Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
Jenkins 1.404
Jenkins promoted builds plugin 2.0
Description
Promote build plugin has the ability to run some scripts. But it doesn't provide the ability to choose which slave the script will be running on.
Sometimes there comes the case that the script can be only running on some of the slaves rather than all of them.
Attachments
Activity
created pull request https://github.com/jenkinsci/promoted-builds-plugin/pull/5
Code changed in jenkins
User: Seiji Sogabe
Path:
src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java
src/main/java/hudson/plugins/promoted_builds/PromotionProcess.java
src/main/resources/hudson/plugins/promoted_builds/JobPropertyImpl/config.jelly
src/main/resources/hudson/plugins/promoted_builds/JobPropertyImpl/help-labelString.html
src/main/resources/hudson/plugins/promoted_builds/Messages.properties
http://jenkins-ci.org/commit/promoted-builds-plugin/2abeca2ff733b3a29227fddc433912570ef691e4
Log:
Merge pull request #5 from ssogabe/JENKINS-9260.
Jenkins 9260 promote plugin should provide ability to select slave node to run
Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/47e71b8...2abeca2
I am eagerly to see this bug can be fixed as soon as possible.
As in our case, we have different type of slaves (windows/mac/linux), and many projects, some projects and their promotion scripts target to run on a specific type of slaves.
Promote plugin randomly chooses the slave causes the annoying failure, we can't do anything even though we known where is the problem.