# Next Pipeline Number **URL:** \ **Category:** Released\ **Created:** [January 25, 2023, 4:51pm UTC](https://discuss.bitrise.io/t/next-pipeline-number/22103 "2023-01-25T16:51:32Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![joshuaongps](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@joshuaongps](https://discuss.bitrise.io/u/joshuaongps)\ **Post date:** [January 25, 2023, 4:51pm UTC](https://discuss.bitrise.io/t/next-pipeline-number/22103/1 "2023-01-25T16:51:32Z")
Workflows currently allow us to set build numbers via `App Settings > Build > Next Build Number`. A common scenario to use the build number is as the `versionCode` for an Android APK. When migrating from one CI system to Bitrise, we set this value to start from the last build number on the old CI system, as `versionCode` must increment higher. Pipelines does not have this feature for `BITRISEIO_PIPELINE_ID`. Thus when migrating from Workflows to Pipelines, the first `versionCode` would be `1`. Why don’t we want to use `BITRISE_BUILD_NUMBER `? If we have parallelised building `debug` and `release` APKs, they ideally should have the same `versionCode`. `BITRISE_BUILD_NUMBER` is unique per workflow so we wouldn’t achieve that. The more parallelisation, the more `BITRISE_BUILD_NUMBER` increases quicker than `BITRISEIO_PIPELINE_ID`. We don’t want the `versionCode` to increase dramatically because there’s a finite range for `versionCode`s. Pipelines should have the same option as workflows currently do, so we can go to `App Settings.> Build` and configure e.g. `Next Pipeline Number`. ---
**Author:** ![pilvikala](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/pilvikala/32/4522_2.png) [@pilvikala](https://discuss.bitrise.io/u/pilvikala)\ **Post date:** [February 8, 2023, 1:26pm UTC](https://discuss.bitrise.io/t/next-pipeline-number/22103/2 "2023-02-08T13:26:21Z")
@joshuaongps We are planning to put standalone builds and pipeline builds on the same numbering sequence. Workflows running from pipelines will all have the same `BITRISE_BUILD_NUMBER`. When this is released, you will be able to use the current “Next Build Number” to affect your pipeline builds as well. ---
**Author:** ![pilvikala](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/pilvikala/32/4522_2.png) [@pilvikala](https://discuss.bitrise.io/u/pilvikala)\ **Post date:** [April 14, 2023, 8:09am UTC](https://discuss.bitrise.io/t/next-pipeline-number/22103/3 "2023-04-14T08:09:29Z")
Hey @joshuaongps , this has been released some time ago, apologies for the late notice. ---
**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\ **Post date:** [May 19, 2023, 1:51pm UTC](https://discuss.bitrise.io/t/next-pipeline-number/22103/4 "2023-05-19T13:51:17Z")