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

programmatically set build number

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • None
    • Platform: All, OS: All

    Description

      in my case, it would be interesting to have a build number not incremental.
      for example, it could be set to the repository revision number, or a number
      computed based on the date.

      Attachments

        Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-507 Allow for configurable build numbers

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-684 New post-build action to execute aribtrary shell commands

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            dgreen dgreen added a comment -

            watch this issue

            dgreen dgreen added a comment - watch this issue
            huybrechts huybrechts added a comment -

            I've just committed some functionality to the description-setter plugin that may
            help. You can use the description-setter to set the description of a build.
            Later you can retrieve a build by using this url:
            /job/<jobName>/by-description/<description>. In your case the description would
            be the SVN revision.

            huybrechts huybrechts added a comment - I've just committed some functionality to the description-setter plugin that may help. You can use the description-setter to set the description of a build. Later you can retrieve a build by using this url: /job/<jobName>/by-description/<description>. In your case the description would be the SVN revision.
            dgreen dgreen added a comment -

            great! I can't wait to try it out.

            dgreen dgreen added a comment - great! I can't wait to try it out.
            jlongman jlongman added a comment -

            I'd like to be able to share the build number between jobs.

            With a universal increasing build number we can stop including internal build
            details to customers and make it simple, but still track whether something comes
            from an developer, an incremental, a nightly, or an official.

            This still maintains the properties that koshuke used to justify removing the
            programmatic settings.

            jlongman jlongman added a comment - I'd like to be able to share the build number between jobs. With a universal increasing build number we can stop including internal build details to customers and make it simple, but still track whether something comes from an developer, an incremental, a nightly, or an official. This still maintains the properties that koshuke used to justify removing the programmatic settings.
            kohsuke Kohsuke Kawaguchi added a comment -

            In 1.390, the display name of a build is modifiable.
            Committed in ad27bab4e74178aa86a973acb20d6c0747aad894

            kohsuke Kohsuke Kawaguchi added a comment - In 1.390, the display name of a build is modifiable. Committed in ad27bab4e74178aa86a973acb20d6c0747aad894

            People

              al_xipe al_xipe
              al_xipe al_xipe
              Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: