Liking cljdoc? Tell your friends :D

automaton-build.tasks.deploy


clean-state?clj

(clean-state? app-dir)

cli-optsclj


compile*clj

(compile* app-dir
          app-name
          paths
          shadow-deploy-alias
          css-files
          compiled-css-path
          compile-jar
          compile-uber-jar
          jar-entrypoint
          java-opts
          env)

compile-appclj

(compile-app dir
             app-name
             paths
             shadow-deploy-alias
             css-files
             compiled-css-path
             compile-jar
             compile-uber-jar
             jar-entrypoint
             java-opts
             env
             current-branch
             repo
             target-branch)

Deploys app in isolation to ensure no cache which requires that your state should be clean and current branch is not a base branch

The process of deployment is:

  1. Compile jar
  2. Push changes to app target branch for that environment
  3. Deploy app

It's done currently not as a workflow, only because workflow can't be used in another workflow and we have a logic we want to preserve here

Deploys app in isolation to ensure no cache which requires that your state should be clean and current branch is not a base branch

 The process of deployment is:
 1. Compile jar
 2. Push changes to app target branch for that environment
 3. Deploy app

It's done currently not as a workflow, only because workflow can't be used in another workflow and we have a logic we want to preserve here
raw docstring

compile-monorepoclj

(compile-monorepo {:keys [app-name app-dir] :as app}
                  target-branch-env
                  clever-uri-env
                  env
                  current-branch
                  verbose?)

current-branch-name-invalid?clj

(current-branch-name-invalid? subapps current-branch)

ensure-no-cacheclj

(ensure-no-cache new-changes-branch repo)

publish-appclj

(publish-app {:keys [app-name app-dir repo target-branch status publish-clojars?
                     publish-cc? jar env cc-uri paths as-lib pom-xml-license]
              :as app}
             verbose?)

publish-clever-cloudclj

(publish-clever-cloud clever-uri app-dir env)

push-base-branchclj

(push-base-branch app-name app-dir repo base-branch message verbose?)

Pushes app to base-branch

Pushes app to `base-branch`
raw docstring

push-current-branchclj

(push-current-branch app-dir
                     app-name
                     repo
                     main-branch
                     current-branch
                     message
                     verbose?)

Pushes app current changes to it's repository. The changes are pushed to the current branch of user running the function. It is forbidden to push to base-branch of application.

Pushes `app` current changes to it's repository. The changes are pushed to the current branch of user running the function. It is forbidden to push to base-branch of application.
raw docstring

push-local-dir-to-repoclj

(push-local-dir-to-repo source-dir
                        repo-address
                        target-branch
                        commit-msg
                        verbose?)

Commit and push target-branch with files from source-dir. Params:

  • source-dir local directory where the sources are stored, before being pushed to the remote repo
  • repo-address the address of the repo
  • commit-msg message that will end in pushed commit
  • version string with tag version
  • tag (optional) map containg id with tag and optional msg with corresponding message
  • force? (optional default false) if true, will force the changes to be pushed as top commit
  • target-branch (optional default current-branch) where to push
Commit and push `target-branch` with files from `source-dir`.
Params:
* `source-dir` local directory where the sources are stored, before being pushed to the remote repo
* `repo-address` the address of the repo
* `commit-msg` message that will end in pushed commit
* `version` string with tag version
* `tag` (optional) map containg `id` with tag and optional `msg` with corresponding message
* `force?` (optional default false) if true, will force the changes to be pushed as top commit
* `target-branch` (optional default current-branch) where to push
raw docstring

run-monorepoclj

(run-monorepo)

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close