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

Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs

    XMLWordPrintable

Details

    • Improvement
    • Status: Reopened (View Workflow)
    • Minor
    • Resolution: Unresolved
    • Jenkins ver. 1.644
      Workflow/Pipeline Plugins: 1.12
      Next Build Number Plugin: 1.3

    Description

      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.

      Attachments

        Issue Links

          Activity

            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.

            evilbeaver Andrei Ovsiankin added a comment - 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.
            derrikammons Derrik Ammons added a comment -

            Oops, sorry Alexander, I edited my original post that may explain my issue further.  I will look at 43867.

            derrikammons Derrik Ammons added a comment - Oops, sorry Alexander, I edited my original post that may explain my issue further.  I will look at 43867.

            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 JENKINS-43867  for a detailed discussion.

            akom Alexander Komarov added a comment - 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 JENKINS-43867   for a detailed discussion.
            derrikammons Derrik Ammons added a comment - - edited

            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 5.1.0.1.  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 Derrik Ammons added a comment - - edited 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 5.1.0.1.  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.

            Reopening since multibranch pipeline is not supported. Patches welcome, not sure when I'll get to this.

            akom Alexander Komarov added a comment - Reopening since multibranch pipeline is not supported. Patches welcome, not sure when I'll get to this.

            People

              akom Alexander Komarov
              potatopankakes Jeff Burke
              Votes:
              8 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated: