[JIRA] [promoted-builds-plugin] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (24/Nov/14 4:15 PM) Description: Mybuildsareforwindowsprojects,butthisissuewouldbethecasewithanyprojectIassume.Ihaveabuildthatisusingalabel,win,whichbothwinbuilda01andwinbuilda02arelabelledwith.Sometimes,thebuildhappensonwinbuilda01:StartedbyuserCharlesMathisBuildingremotelyonwinbuilda01inworkspaced:\jenkins-slave\workspace\DeployerUsingremoteperforceclient:jenkins_deployer--667683261[...successfullybuilds...]NotifyingupstreamprojectsofjobcompletionFinished:SUCCESSButthepromotionhappensonwinbuilda02:StartedbyuserchmathisBuildingremotelyonwinbuilda02inworkspaceD:\jenkins-slave\workspace\DeployerPromotingDeployer#173[Deployer]$cmd/ccallC:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfullypromotes...]NotifyingupstreamprojectsofjobcompletionFinished:FAILUREIwouldexpectoneoftwothings:1)Ittorunthepromotiononwinbuilda01sinceitbuiltitonwinbuilda01or2)Copydownthebuildartifactstowinbuilda02sothatitcanrunthepromotionthereNeitherseemtohappen.AmImissingsomething?Oristhisabug?-Theobviousworkaroundistosetthebuildtospecificboxinsteadofalabelsothatthebuildandpromotionsjobsdonotroam,butthatdefeatsthepurposeofusingslaves.:( -11/24/2014Edit:IhavealotmoreexperiencewithJenkinsnow,soIrealizethatIshouldnotrelyonworkspacefileswhenpromoting,butratherarchivemyartifacts,andcopyartifactsfromapreviousbuildusingtheCopyArtifactsplugin.Thatway,nomatterwheremypromotionruns,itllalwayscopydowntheartifactstotheboxitrunson.Whilethatistheappropriatethingtodo,forlessexperiencedusersofJenkins,itsnotobvious,soIwouldsuggestthatthisissueisstillrelevant,butunderstandwhyitisalowerpriority.Thanks! 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/d/optout.
[JIRA] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis created JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 29/Nov/12 3:28 PM Description: My builds are for windows projects, but this issue would be the case with any project I assume. I have a build that is using a label, "win", which both winbuila01 and winbuilda02 are labelled with. Sometimes, the build happens on winbuila01: Started by user Charles Mathis Building remotely on winbuila01 in workspace d:\jenkins-slave\workspace\Deployer Using remote perforce client: jenkins_deployer--667683261 ...successfully builds... Notifying upstream projects of job completion Finished: SUCCESS But the promotion happens on winbuilda02: Started by user chmathis Building remotely on winbuilda02 in workspace D:\jenkins-slave\workspace\Deployer Promoting Deployer #173 Deployer $ cmd /c call C:\Windows\TEMP\hudson791959618011257982.bat ...unsuccessfully promotes... Notifying upstream projects of job completion Finished: FAILURE I would expect one of two things: 1) It to run the promotion on winbuila01 since it built it on winbuilda01 or 2) Copy down the build artifacts to winbuilda02 so that it can run the promotion there Neither seem to happen. Am I missing something? Or is this a bug? - The obvious workaround is to set the build to specific box instead of a label so that the build and promotions jobs do not roam, but that defeats the purpose of using slaves. Environment: Master: Linux Slave [webdeva03] Windows Server 2008 Slave [winbuilda01] Windows Server 2008 Project: Jenkins Labels: plugin promoted-builds artifact Priority: Minor Reporter: Charles Mathis 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-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:29 PM) Description: Mybuildsareforwindowsprojects,butthisissuewouldbethecasewithanyprojectIassume.Ihaveabuildthatisusingalabel,win,whichbothwinbuila01andwinbuilda02arelabelledwith.Sometimes,thebuildhappensonwinbuila01: StartedbyuserCharlesMathisBuildingremotelyonwinbuila01inworkspaced:\jenkins-slave\workspace\DeployerUsingremoteperforceclient:jenkins_deployer--667683261[...successfullybuilds...]NotifyingupstreamprojectsofjobcompletionFinished:SUCCESSButthepromotionhappensonwinbuilda02:StartedbyuserchmathisBuildingremotelyonwinbuilda02inworkspaceD:\jenkins-slave\workspace\DeployerPromotingDeployer#173[Deployer]$cmd/ccallC:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfullypromotes...]NotifyingupstreamprojectsofjobcompletionFinished:FAILUREIwouldexpectoneoftwothings:1)Ittorunthepromotiononwinbuila01sinceitbuiltitonwinbuilda01or2)Copydownthebuildartifactstowinbuilda02sothatitcanrunthepromotionthereNeitherseemtohappen.AmImissingsomething?Oristhisabug?-Theobviousworkaroundistosetthebuildtospecificboxinsteadofalabelsothatthebuildandpromotionsjobsdonotroam,butthatdefeatsthepurposeofusingslaves.:( 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-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:30 PM) Environment: Master:LinuxSlave[ webdeva03 winbuilda01 ]WindowsServer2008Slave[ winbuilda01 winbuilda02 ]WindowsServer2008 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-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:36 PM) Description: Mybuildsareforwindowsprojects,butthisissuewouldbethecasewithanyprojectIassume.Ihaveabuildthatisusingalabel,win,whichboth winbuila01 winbuilda01 andwinbuilda02arelabelledwith.Sometimes,thebuildhappenson winbuila01 winbuilda01 :StartedbyuserCharlesMathisBuildingremotelyon winbuila01 winbuilda01 inworkspaced:\jenkins-slave\workspace\DeployerUsingremoteperforceclient:jenkins_deployer--667683261[...successfullybuilds...]NotifyingupstreamprojectsofjobcompletionFinished:SUCCESSButthepromotionhappensonwinbuilda02:StartedbyuserchmathisBuildingremotelyonwinbuilda02inworkspaceD:\jenkins-slave\workspace\DeployerPromotingDeployer#173[Deployer]$cmd/ccallC:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfullypromotes...]NotifyingupstreamprojectsofjobcompletionFinished:FAILUREIwouldexpectoneoftwothings:1)Ittorunthepromotionon winbuila01 winbuilda01 sinceitbuiltitonwinbuilda01or2)Copydownthebuildartifactstowinbuilda02sothatitcanrunthepromotionthereNeitherseemtohappen.AmImissingsomething?Oristhisabug?-Theobviousworkaroundistosetthebuildtospecificboxinsteadofalabelsothatthebuildandpromotionsjobsdonotroam,butthatdefeatsthepurposeofusingslaves.:( 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-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 6:34 PM) Labels: artifactpluginpromoted-builds slave 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
