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

Added plugin mechanism for extending a build's display name

    • Icon: Patch Patch
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      This patch allows plugins to supply additional text to be appended to a Run's
      display name. Intended to be used by SCM plugins to display a branch name or
      revision number as part of the display name. This is achieved via a new
      interface DisplayNameAction for Run actions.

          [JENKINS-4884] Added plugin mechanism for extending a build's display name

          pcc added a comment -

          Created an attachment (id=1021)
          [PATCH 1/2] Added plugin mechanism for extending a build's display name

          pcc added a comment - Created an attachment (id=1021) [PATCH 1/2] Added plugin mechanism for extending a build's display name

          pcc added a comment -

          Created an attachment (id=1022)
          [PATCH 2/2] Changed all known Run.getNumber() references to Run.get

          {,Full}

          DisplayName() where appropriate

          pcc added a comment - Created an attachment (id=1022) [PATCH 2/2] Changed all known Run.getNumber() references to Run.get {,Full} DisplayName() where appropriate

          Thank you for the patch.

          I'm not sure if the revision number from SCM is important enough that it should
          be displayed everywhere a build is referred to — I mean, normally isn't it a
          pretty cryptic meaningless token for most people anyway?

          I think a better change is to allow people to set the display name as text
          during a build, which should allow variable expansions like SCM revision numbers
          and other things. This is often referred to as "ability to set arbitrary build
          number", but what it really means is that people just want to control what
          Hudson shows as an ID of the build, and that doesn't have to be the same with
          what Hudson internally uses to refer to a build.

          Another lesson from that RFE is that people don't like random/meaningless
          numbers used as a build identifier, and to me this would only make it worse.

          So I feel we need to work on this a bit more before integrating this change.

          Kohsuke Kawaguchi added a comment - Thank you for the patch. I'm not sure if the revision number from SCM is important enough that it should be displayed everywhere a build is referred to — I mean, normally isn't it a pretty cryptic meaningless token for most people anyway? I think a better change is to allow people to set the display name as text during a build, which should allow variable expansions like SCM revision numbers and other things. This is often referred to as "ability to set arbitrary build number", but what it really means is that people just want to control what Hudson shows as an ID of the build, and that doesn't have to be the same with what Hudson internally uses to refer to a build. Another lesson from that RFE is that people don't like random/meaningless numbers used as a build identifier, and to me this would only make it worse. So I feel we need to work on this a bit more before integrating this change.

          Issue #53 appears to cover the ability to set a build number.

          Kohsuke Kawaguchi added a comment - Issue #53 appears to cover the ability to set a build number.

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

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

            Unassigned Unassigned
            pcc pcc
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: