How do you keep a build from running ahead of a test?

Describe jobs and their order in the project’s .circleci/config.yml file. Use a workflow dependency to make the build wait for a passing test. A workflow is the group of jobs and their order.

Use the app’s existing test and keep the result next to the run. An uploaded artifact can hold the test report so someone else can see what failed.

Who can approve a CircleCI hold?

A workflow can wait at an approval job. Jobs after the hold must explicitly require it. CircleCI documents that someone with repository push access can approve the ordinary hold.

When a production release should be limited to fewer people, check repository access and the permissions of the downstream job. Treat the approval and permission to run the next job as separate checks.

What do 30,000 Free credits buy?

CircleCI documents 30,000 monthly Free credits for non-open-source usage. The minutes you get depend on the machine type and size. Storage and network usage beyond the included amounts can also consume credits.

When the balance is exhausted, Free non-open-source builds stop until credits refill. Keep the config with the project and save needed artifacts outside expiring run storage. Changing providers means recreating the workflow settings and credentials there.

How can you rehearse approval without releasing?

Sketch a fictional booking change on paper. Use no connected repository, hosted runner, credential or release action.

Draw the dependencies
Put a passing test before an approval and the publish job after it.
Try the no-approval case
Cover the approval with a piece of paper. The publish job should have no path to run.