I have a problem where a build runs on one Jenkins machine, and then I do a manual promotion. The manual promotion runs on a different machine than the build that I am promoting, so of course the directories and files constructed by the build do not exist on the second machine. The promotion fails immediately as a result.
How can I get the promotion to respect the host to run on? If I set the "Restrict where this promotion process can be run" checkbox, then the comment states that "If not set, the label of the promoted build will be used", which is extremely poor wording that I interpret as it should stay on the same host as the build that I'm promoting. Unfortunately, it will not stick unless I enter a hostname, so it too is useless. If I enter the matching hostname to the box that the build was run on, then it works, but realistically prevents me from using any slave machines. Is this multipole bugs in the Jenkins 1.612 promotion mechanism, or am I missing something? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/958ce4c66ec24b61b34e30ab328f9024%40mbx01cmb01p.esentire.local. For more options, visit https://groups.google.com/d/optout.
