We have updated the behavior of the BITRISE_BUILD_NUMBER environment variable on Pipelines to avoid build numbering conflicts and to make it easier for you to work with Pipelines and standalone builds in the future.
What changed
Pipelines are now on the same numbering sequence as standalone builds. For example, if your last standalone Workflow Build had build number 100, your next pipeline build will be 101 no matter what the previous pipeline build number was.
The BITRISE_BUILD_NUMBER variable is now the same for all Workflows within the pipeline. This makes finding the builds by their build number easier in the App page.
What do you need to do?
If you use the BITRISE_BUILD_NUMBER environment variable in your pipelines for app versioning or similar purposes, note that the number may have jumped in the sequence.
If you need a unique identifier for your Workflows running within pipelines, you can use BITRISE_BUILD_SLUG instead. For the full overview of environment variables available during Builds, see our documentation.
When you are setting up new pipelines:
- Start using the Pipeline Build as the main build (similar to a Standalone Build)
- Do not use build numbers to version your apps, instead, use the Pipeline build number available in the
BITRISE_BUILD_NUMBERenvironment variable. - When searching for builds in the build list, use the build number to find the pipeline, and drill down to find the included builds.