My request: Don't unset the `CIRCLECI_BUILD_NUM` in a local CircleCI build, please.
The local CircleCI build unset's it:
====>> Spin up Environment
Build-agent version 0.0.5763-f6bc418 (2018-05-22T19:06:47+0000)
Starting container [...]
using image [...]
Using build environment variables:
That means you can't reset it with
circleci build --env CIRCLE_BUILD_NUM=manual-1
See also: https://discuss.circleci.com/t/setting-circle-build-num-in-local-builds/16743
We tag our Docker image builds with the `CIRCLECI_BUILD_NUM`. It would be nice that we can test the CircleCI build locally again. It was possible in an older CLI version.