Under CircleCI 1.0 we would send a
SKIP_TEST=true environment in the API call to launch a deploy-only job, but to make this efficient, we needed to run each of our commands in a wrapper that skipped them, so only the deploy ran. It would be much easier to do this in CircleCI 2.0 if in addition to a branch-name filter, we could filter jobs (and/or workflows) based on an environment variable.
My current plan without this feature is to set the
shell for each
run to a shell that does nothing when
true, but it means all commands need this