[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here

2014-02-15 Thread de...@ikedam.jp (JIRA)















































ikedam
 closed  JENKINS-19693 as Fixed


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
















Fixed in Copyartifact 1.30.





Change By:


ikedam
(16/Feb/14 4:01 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here

2014-02-02 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-19693


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















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





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here

2014-02-02 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 resolved  JENKINS-19693 as Fixed


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
















Change By:


SCM/JIRA link daemon
(02/Feb/14 12:50 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here

2014-01-13 Thread alexis.more...@gmail.com (JIRA)














































Alexis Morelle
 commented on  JENKINS-19693


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















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.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here

2014-01-13 Thread isan...@gmail.com (JIRA)














































Igor Kostenko
 commented on  JENKINS-19693


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















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.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here

2014-01-13 Thread alexis.more...@gmail.com (JIRA)














































Alexis Morelle
 commented on  JENKINS-19693


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















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)?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here

2014-01-13 Thread isan...@gmail.com (JIRA)














































Igor Kostenko
 commented on  JENKINS-19693


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















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.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.