[JIRA] (JENKINS-14656) Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.

2012-08-04 Thread mindl...@java.net (JIRA)














































Alan Harder
 commented on  JENKINS-14656


Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.















If you trigger the build manually then there is no upstream build, so this is expected.
Check the Use "Last successful build" as fallback checkbox to use the last successful build instead of no artifact.



























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






[JIRA] (JENKINS-14656) Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.

2012-08-04 Thread mindl...@java.net (JIRA)















































Alan Harder
 resolved  JENKINS-14656 as Not A Defect


Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.
















Change By:


Alan Harder
(04/Aug/12 3:44 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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






[JIRA] (JENKINS-14656) Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.

2012-08-04 Thread ranki...@yahoo.com (JIRA)












































 
Chris Rankin
 edited a comment on  JENKINS-14656


Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.
















The problem with the Use "Last successful build" as fallback checkbox is that someone might have created a new upstream build (or two) in the interim. We would like Jenkins to push a particular build though the pipeline instead, even if some of the steps need to be triggered manually.



























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






[JIRA] (JENKINS-14656) Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.

2012-08-04 Thread ranki...@yahoo.com (JIRA)












































 
Chris Rankin
 edited a comment on  JENKINS-14656


Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.
















The problem with the Use "Last successful build" as fallback checkbox is that someone might have created a new upstream build (or two) in the interim. We would like Jenkins to push a particular build though the pipeline instead, even if some of the step need to be triggered manually.



























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






[JIRA] (JENKINS-14656) Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.

2012-08-04 Thread ranki...@yahoo.com (JIRA)














































Chris Rankin
 commented on  JENKINS-14656


Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.















Perhaps this issue should be renamed: "Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually".



























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






[JIRA] (JENKINS-14656) Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.

2012-08-03 Thread ranki...@yahoo.com (JIRA)














































Chris Rankin
 created  JENKINS-14656


Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.















Issue Type:


Bug



Affects Versions:


current



Assignee:


Alan Harder



Components:


build-pipeline, copyartifact



Created:


01/Aug/12 2:31 PM



Description:


Configure a build pipeline of two jobs, where the second job is triggered manually. The Copy Artifacts plugin cannot select the artifacts from the first job because TriggeredBuildSelector only checks for "hudson.model.Cause$UpstreamCause", and not for "au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView$MyUserIdCause".




Environment:


Windows 7




Project:


Jenkins



Priority:


Major



Reporter:


Chris Rankin

























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






[JIRA] (JENKINS-14656) Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.

2012-08-03 Thread ranki...@yahoo.com (JIRA)














































Chris Rankin
 updated  JENKINS-14656


Copy Artifacts plugin cannot copy from upstream build pipeline if build is triggered manually.
















Change By:


Chris Rankin
(01/Aug/12 4:13 PM)




Description:


Configureabuildpipelineoftwojobs,wherethesecondjobistriggeredmanually.TheCopyArtifactsplugin
inthesecondjob
cannotselecttheartifactsfromthefirstjobbecauseTriggeredBuildSelectoronlychecksforhudson.model.Cause$UpstreamCause,andnotforau.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView$MyUserIdCause.



























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