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

Regression breakage in version number after upgrade

    XMLWordPrintable

Details

    Description

      Hi – Upgrading to the versionnumber plugin version 1.7 seems to have broken the next build number. Reverting to 1.6 fixes the issue.

      I'm using job dsl to configure by jobs. Here is the relevant configuration:

      wrappers {
      versionNumberBuilder {
      environmentVariableName('VERSION')
      environmentPrefixVariable('')
      versionNumberString(cfg.semverPrefix + '.${BUILDS_ALL_TIME}')
      skipFailedBuilds(true)
      useAsBuildDisplayName(true)
      projectStartDate('1969-12-31 05:00:00.0 UTC')
      buildsToday('')
      buildsThisWeek('')
      buildsThisMonth('')
      buildsThisYear('')
      buildsAllTime('')
      }
      }

      The issue is that the build number is not incrementing after successful builds. What is strange is that running a manual build will bump the version. In my case, builds are typically triggered by a push from our Bitbucket. When triggered by the push, the version number does not increment. When triggered from a manual build via the Jenkins UI, the number does increment.

      I'm not sure what other information I can provide, but I'm happy to help out if there are questions.

      Thanks,
      Tim

      Attachments

        Issue Links

          Activity

            People

              bahadir Deniz Bahadir
              timdowney Tim Downey
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: