Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Simplify CircleCI build, less configuration, remove macOS build (#2051)
* Simplify CircleCI build, less configuration, remove macOS build * Automatically build release when tag is pushed * Build image tarballs when not prerelease * Try to do less homebrew and make all commands quieter * Add the org_global restricted context to release buld * Update docs and remove trigger_release.sh
- Loading branch information
Showing
8 changed files
with
156 additions
and
333 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,5 @@ | ||
# CircleCI Script Usage | ||
|
||
## Tags build automatically | ||
## Tags/Releases build automatically | ||
|
||
If you just push a tag, circleci will build that tag and make its artifacts available both on CircleCI and by creating a GitHub release draft containing the artifacts. This is a result of the tag_build *workflow*, which calls the job. | ||
|
||
## Push a release with trigger_release.sh | ||
|
||
`.circleci/trigger_release.sh --release-tag=v1.7.1 --circleci-token=circleToken900908b3443ea58316baf928b --github-token=githubPersonalToken853ae6f72c40525cd21036f742904a --windows-signing-password=windowscodepassword | jq -r 'del(.circle_yml)' | jq -r 'del(.circle_yml)'` | ||
|
||
## trigger_job.sh options | ||
|
||
trigger_job.sh can be used to trigger *jobs* but not workflows. As our Circleci strategy is mostly built around workflows, this is less useful than it used to be. | ||
|
||
.circleci/trigger_job.sh <circle_token> tag_build drud/ddev <optional_branch> <github_personal_access_token> <release_tag> | jq -r | ||
|
||
trigger_job.sh can trigger a nightly or a normal build. It triggers *jobs* not workflows. | ||
|
||
It always requires a circle token for the second argument, and by default will run the main build workflow: | ||
|
||
* trigger normal build: | ||
`.circleci/trigger_job.sh 0123456773884887377aabvb ` | ||
|
||
* trigger nightly build in drud/ddev (default): | ||
`.circleci/trigger_job.sh 0123456773884887377aabvb nightly_build` | ||
|
||
* trigger nightly using rfay/ddev master branch (testing must be enabled on rfay/ddev): | ||
`.circleci/trigger_job.sh 0123456773884887377aabvb nightly_build rfay/ddev` | ||
|
||
* trigger nightly on rfay/ddev on branch 20170803_workflows_contexts: | ||
`.circleci/trigger_job.sh 0123456773884887377aabvb nightly_build rfay/ddev 20170803_workflows_contexts` |
Oops, something went wrong.