Status: Reopened (View Workflow)
Jenkins ver. 1.644
Workflow/Pipeline Plugins: 1.12
Next Build Number Plugin: 1.3
The Set Next Build Number menu link does not show up for Workflow or Multi-branch Workflow/Pipeline projects. See attached images of link present on a freestyle project, but missing on the workflow project, and on the multibranch workflow child/branch projects.
- is blocked by
JENKINS-44757 Provide a way to reset build number to 1 within Jenkinsfile for a Multibranch Pipeline
I too need to be able to update our Release branch for both our iOS and Android apps. I would like to reset the build back to 1 when a release is incremented in the plist for iOS or gradle file for Android. There may be several builds in the previous release and after development merges their feature branches into the master branch along with an incremented release number, I want the build number to start from 1 again. For example, if the previous release was 5.0.5 (24), and the source code has 5.1.0, the build starts back at 1 allowing the iOS app be 5.1.0 (1) and the Android app be 184.108.40.206. I suppose that the 24 builds of the previous release will be removed.
I will close my enhancement request that I filed, yesterday: https://issues.jenkins-ci.org/browse/JENKINS-44757 and watch this issue.
Alexander, if this is not the same type of request, please let me know, and I can reopen my original request.
derrikammons: With regard to "resetting the build back to 1", what behavior are you expecting? Jenkins does not permit setting build numbers lower than the highest existing build number (you can delete the old builds, however). See
for a detailed discussion. JENKINS-43867
Oops, sorry Alexander, I edited my original post that may explain my issue further. I will look at 43867.
I also interested in this.
Use case: simple git-flow development cycle.
There are stable branches: dev and master. When DEV is merged to master, master number will be lower than last night-build number. Customers are finding it strange.
Reopening since multibranch pipeline is not supported. Patches welcome, not sure when I'll get to this.