[JIRA] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Scott Armit commented on JENKINS-15980 Promotion job doesn't execute on the same machine that the build job executed on. +1 for fixing this. A simple example for why the promote plugin should have the ability to tie to the same node where the build was executed is the Git publisher plugin which is an option in the list of tasks available to the promote plugin. If you want to treat merging/publishing a Git branch or tag created by your build up to the server (which is the point of the Git publisher plugin), then you need access to the workspace of the build. Another example is running a script as part of a promotion, and that script is in the workspace/git repository. Sure, you treat the script as a build artifact, then grab it, etc. etc., but it makes a lot more sense to be able to tie a promotion to the same system. Thanks for considering. 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] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesn't execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 6:34 PM) Labels: artifact plugin promoted-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
[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 doesn't execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:36 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 winbuilda01 and winbuilda02 are labelled with.Sometimes, the build happens on winbuila01 winbuilda01 :Started by user Charles MathisBuilding remotely on winbuila01 winbuilda01 in workspace d:\jenkins-slave\workspace\DeployerUsing remote perforce client: jenkins_deployer--667683261[...successfully builds...]Notifying upstream projects of job completionFinished: SUCCESSBut the promotion happens on winbuilda02:Started by user chmathisBuilding remotely on winbuilda02 in workspace D:\jenkins-slave\workspace\DeployerPromoting Deployer #173[Deployer] $ cmd /c call C:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfully promotes...]Notifying upstream projects of job completionFinished: FAILUREI would expect one of two things:1) It to run the promotion on winbuila01 winbuilda01 since it built it on winbuilda01or2) Copy down the build artifacts to winbuilda02 so that it can run the promotion thereNeither 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. :( 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 doesn't 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 ]Windows Server 2008Slave [ winbuilda01 winbuilda02 ]Windows Server 2008 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 doesn't execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:29 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 MathisBuilding remotely on winbuila01 in workspace d:\jenkins-slave\workspace\DeployerUsing remote perforce client: jenkins_deployer--667683261[...successfully builds...]Notifying upstream projects of job completionFinished: SUCCESSBut the promotion happens on winbuilda02:Started by user chmathisBuilding remotely on winbuilda02 in workspace D:\jenkins-slave\workspace\DeployerPromoting Deployer #173[Deployer] $ cmd /c call C:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfully promotes...]Notifying upstream projects of job completionFinished: FAILUREI would expect one of two things:1) It to run the promotion on winbuila01 since it built it on winbuilda01or2) Copy down the build artifacts to winbuilda02 so that it can run the promotion thereNeither 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. :( 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 created JENKINS-15980 Promotion job doesn't 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
