Closed jdeanwallace closed 1 year ago
Resolves https://github.com/tiny-pilot/tinypilot/issues/1548
This PR moves the comments that explains how to trigger a code-based bundle build from .circleci/config.yml to .circleci/continue_config.yml and updates the contributing docs to reference the correct CircleCI config file.
.circleci/config.yml
.circleci/continue_config.yml
So the correct ways to manually trigger a bundle build is either the:
In the CircleCI configuration, change the bundle_build_branch parameter’s default value from master to << pipeline.git.branch >>. Push your changes as branch to GitHub. CircleCI will now automatically build bundles for all subsequent commits of that branch. Before eventually merging your feature branch, remember to revert the bundle_build_branch parameter to the original value (i.e., master)
bundle_build_branch
default
master
<< pipeline.git.branch >>
On CircleCI’s overview page for the respective branch, click the “Trigger Pipeline” button. In the dialog, enter bundle_build_branch as parameter name, and the (exact) name of the branch as parameter value. Click the “Trigger Pipeline” button in the dialog. CircleCI will now build a bundle for the latest commit of that branch.
Resolves https://github.com/tiny-pilot/tinypilot/issues/1548
This PR moves the comments that explains how to trigger a code-based bundle build from
.circleci/config.yml
to.circleci/continue_config.yml
and updates the contributing docs to reference the correct CircleCI config file.So the correct ways to manually trigger a bundle build is either the: