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

"Build Number" field expect positive number, so it is impossible to use named builds here

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      "Build Number" field (when "Which Build" = "Specific build") expect positive number, so it is not possible to use named builds here (like "RC1").

      It is much more convenient to use build name here (you could rename any build). But because of this check it is not possible to copy artifacts from renamed builds.

        Attachments

          Activity

          Hide
          almorelle Alexis Morelle added a comment -

          What you are referencing is only the display name, in background, Jenkins still reference the build by its number. There's a method in the core to retrieve a build by its number but not by its display name, finding a match may be less efficient then.

          Show
          almorelle Alexis Morelle added a comment - What you are referencing is only the display name, in background, Jenkins still reference the build by its number. There's a method in the core to retrieve a build by its number but not by its display name, finding a match may be less efficient then.
          Hide
          igorkostenko Igor Kostenko added a comment -

          Yes, I understand that build number still could be used. Idea was to make life easier - when you have many different jobs with different build numbers it is easy to make a mistake when you getting specific artifacts from there, using the same name everywhere is more convenient.

          Show
          igorkostenko Igor Kostenko added a comment - Yes, I understand that build number still could be used. Idea was to make life easier - when you have many different jobs with different build numbers it is easy to make a mistake when you getting specific artifacts from there, using the same name everywhere is more convenient.
          Hide
          almorelle Alexis Morelle added a comment -

          It's just that you could give the same display name to two existing builds and also name one with a number while there's already a build with that number.
          Do you think it's fair enough to give priority to numbers (i.e. it's a number so we look for it not as a display name) than look for named builds (and then permalinks)?

          Show
          almorelle Alexis Morelle added a comment - It's just that you could give the same display name to two existing builds and also name one with a number while there's already a build with that number. Do you think it's fair enough to give priority to numbers (i.e. it's a number so we look for it not as a display name) than look for named builds (and then permalinks)?
          Hide
          igorkostenko Igor Kostenko added a comment -

          Yes, it is fair and it is consistent with jeninks url behavior, if you specifying number in http://<jenkins>/job/<job>/<build>/ you will get build by number (and will get an error if you used a number for display name and there is no job with such number). I guess it would be better if just number in display name will be prohibited to avoid confusion and inconsistent behavior.

          Show
          igorkostenko Igor Kostenko added a comment - Yes, it is fair and it is consistent with jeninks url behavior, if you specifying number in http://<jenkins>/job/<job>/<build>/ you will get build by number (and will get an error if you used a number for display name and there is no job with such number). I guess it would be better if just number in display name will be prohibited to avoid confusion and inconsistent behavior.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Alexis Morelle
          Path:
          src/main/java/hudson/plugins/copyartifact/SpecificBuildSelector.java
          src/main/resources/hudson/plugins/copyartifact/SpecificBuildSelector/config.jelly
          src/main/webapp/help-specificBuild.html
          src/test/java/hudson/plugins/copyartifact/SpecificBuildSelectorTest.java
          http://jenkins-ci.org/commit/copyartifact-plugin/f0a01c82472879e9bd9b72022b6bd16363b603b6
          Log:
          [FIXED JENKINS-19693]

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Alexis Morelle Path: src/main/java/hudson/plugins/copyartifact/SpecificBuildSelector.java src/main/resources/hudson/plugins/copyartifact/SpecificBuildSelector/config.jelly src/main/webapp/help-specificBuild.html src/test/java/hudson/plugins/copyartifact/SpecificBuildSelectorTest.java http://jenkins-ci.org/commit/copyartifact-plugin/f0a01c82472879e9bd9b72022b6bd16363b603b6 Log: [FIXED JENKINS-19693]
          Hide
          ikedam ikedam added a comment -

          Fixed in Copyartifact 1.30.

          Show
          ikedam ikedam added a comment - Fixed in Copyartifact 1.30.

            People

            • Assignee:
              Unassigned
              Reporter:
              igorkostenko Igor Kostenko
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: