Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44757

Provide a way to reset build number to 1 within Jenkinsfile for a Multibranch Pipeline

XMLWordPrintable

      Currently I am using the incremented build number provided by Jenkins for the release version of our iOS and Android app. Product/dev drive the release numbers. Once the feature branch is merged into master, a build is automatically kicked off and if the release number is incremented, I want to reset the build number back to 1. For example if 5.0.1 (5) is the current market release and dev merges a feature branch into master with a greater release number, like 5.0.2, I want to reset the build number back to 1 so that the app version is now 5.0.2 (1). My Jenkins is on a Linux server that uses a Mac OS X agent for building our iOS app. How do I reset the build number back to 1 after the build has automatically kicked off, checked out the source code, and checked to see if the build should be reset?

        1. System Information [Jenkins].pdf
          121 kB

          [JENKINS-44757] Provide a way to reset build number to 1 within Jenkinsfile for a Multibranch Pipeline

          Derrik Ammons created issue -

          Derrik Ammons added a comment -

          It appears that this may be related to https://issues.jenkins-ci.org/browse/JENKINS-33046

          Derrik Ammons added a comment - It appears that this may be related to  https://issues.jenkins-ci.org/browse/JENKINS-33046
          Derrik Ammons made changes -
          Component/s New: next-build-number-plugin [ 15651 ]
          Derrik Ammons made changes -
          Labels Original: BuildNumber New: core plugin

          Derrik Ammons added a comment -

          Since this appears to be a duplicate, I will close this.  I am happy to see that others have ran into the same issue.

          Derrik Ammons added a comment - Since this appears to be a duplicate, I will close this.  I am happy to see that others have ran into the same issue.
          Derrik Ammons made changes -
          Link New: This issue blocks JENKINS-33046 [ JENKINS-33046 ]
          Derrik Ammons made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

          victor borrull added a comment - - edited

          Hi derrikammons,

          In my opinion this is not a duplicated of JENKINS-33046

          I have a very similar request as you do. In my case the main issue is with Android release in Google Play. Our current version is 2.2.21 and build number is 331, the versionCode becomes 202213312 (20221 is the version, 331 is the build number, 2 is the architecture) but the maximum value allowed in Google Play is 2100000000, which means that we are either limited to 3 digits build number if we reach version 10.x.x or to 4 digits if we assume we will stick to single digit major version.

          Thus, as you do, we need to be able to reset the build number back to 1 when the major or minor version increases. Ideally, as you pointed out, this should be done from the JenkinsFile. I am not a Jenkins expert but I don't think that this is possible at the moment.

          victor borrull added a comment - - edited Hi derrikammons , In my opinion this is not a duplicated of JENKINS-33046 I have a very similar request as you do. In my case the main issue is with Android release in Google Play. Our current version is 2.2.21 and build number is 331, the versionCode becomes 202213312 (20221 is the version, 331 is the build number, 2 is the architecture) but the maximum value allowed in Google Play is 2100000000, which means that we are either limited to 3 digits build number if we reach version 10.x.x or to 4 digits if we assume we will stick to single digit major version. Thus, as you do, we need to be able to reset the build number back to 1 when the major or minor version increases. Ideally, as you pointed out, this should be done from the JenkinsFile. I am not a Jenkins expert but I don't think that this is possible at the moment.

          Mark Waite added a comment -

          What are the barriers that prevent you from encoding the release number in your source files and incrementing that build number when you release software? The Jenkins BUILD_ID really isn't connected to your release numbering technique, while your source code is strongly connected to your release numbering technique.

          Ant based builds can have the build.number file. Maven based builds encode the release in the pom file. I believe other build systems likewise have a way of giving the build software (ant, maven, cmake, make, ...) control of the release numbering scheme.

          Mark Waite added a comment - What are the barriers that prevent you from encoding the release number in your source files and incrementing that build number when you release software? The Jenkins BUILD_ID really isn't connected to your release numbering technique, while your source code is strongly connected to your release numbering technique. Ant based builds can have the build.number file. Maven based builds encode the release in the pom file. I believe other build systems likewise have a way of giving the build software (ant, maven, cmake, make, ...) control of the release numbering scheme.

          victor borrull added a comment -

          Hi markewaite, I believe that we actually have no barriers to do that. Actually it is probably better since it seems that resetting the Jenkins build number actually means deleting the builds using those numbers previously, thus losing the build history.

          We will implement some kind of auto increasing and resettable build number as part of the build process.

          Thanks

          victor borrull added a comment - Hi markewaite , I believe that we actually have no barriers to do that. Actually it is probably better since it seems that resetting the Jenkins build number actually means deleting the builds using those numbers previously, thus losing the build history. We will implement some kind of auto increasing and resettable build number as part of the build process. Thanks

            Unassigned Unassigned
            derrikammons Derrik Ammons
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: