(clean-state? app-dir)
(current-branch-name-invalid? subapps current-branch)
(deploy app 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:
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
(deploy* app-dir app-name project-config deps-edn env)
(ensure-no-cache new-changes-branch repo)
(publish-apps {:keys [app-name app-dir repo target-branch general
publish-clojars? publish-cc? jar env cc-uri]})
(publish-clever-cloud clever-uri app-dir env)
(push-base-branch app-name app-dir repo base-branch message)
Pushes app to base-branch
Pushes app to `base-branch`
(push-current-branch app-dir app-name repo main-branch current-branch message)
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.
(push-local-dir-to-repo source-dir repo-address target-branch commit-msg)
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 reporepo-address
the address of the repocommit-msg
message that will end in pushed commitversion
string with tag versiontag
(optional) map containg id
with tag and optional msg
with corresponding messageforce?
(optional default false) if true, will force the changes to be pushed as top committarget-branch
(optional default current-branch) where to pushCommit 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)
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close