automaton-build.tasks.deploy — org.clojars.hephaistox/automaton-build 3.2.0-39-la

clean-state? clj

(clean-state? app-dir)

cli-opts clj

compile* clj

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

compile-app clj

(compile-app dir
             app-name
             deps-edn
             excluded-aliases
             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

compile-monorepo clj

(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-cache clj

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

publish-app clj

(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-cloud clj

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

push-base-branch clj

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

Pushes app to base-branch

push-current-branch clj

(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.

push-local-dir-to-repo clj

(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

run-monorepo clj

(run-monorepo)