• Type: New Feature
• Resolution: Won't Fix
• Priority: Minor
• Component/s: multi-branch-project-plugin (not Pipeline)
• Labels:

  None

[JENKINS-32243] Parameterization of "Restrict where this project can be run"

Matthew DeTullio created issue - 2015-12-30 23:38

Matthew DeTullio made changes - 2015-12-30 23:46

Issue Type

Original: Bug [ 1 ]

New: Improvement [ 4 ]

Matthew DeTullio made changes - 2015-12-30 23:46

Issue Type

Original: Improvement [ 4 ]

New: New Feature [ 2 ]

Matthew DeTullio made changes - 2015-12-31 00:13

Description

Original: We have some jobs than can be merged into one "multi branch" job. The only reason is that they need to run on another slave if it is branch "A" or branch "B". As this cannot be evaluated if the job started it needs to be "hardcoded" to the job configuration. Idea: Write in "global" job in "Restrict where this project can be run" field for example "Windows7_\$SUBJOB_BRANCH" and it will be "Windows7_stable" and "Windows7_master" in the sub projects.

New: Original reporter [~misery] We have some jobs than can be merged into one "multi branch" job. The only reason is that they need to run on another slave if it is branch "A" or branch "B". As this cannot be evaluated if the job started it needs to be "hardcoded" to the job configuration. Idea: Write in "global" job in "Restrict where this project can be run" field for example "Windows7_\$SUBJOB_BRANCH" and it will be "Windows7_stable" and "Windows7_master" in the sub projects.

Matthew DeTullio made changes - 2016-07-01 21:24

Link

New: This issue is related to JENKINS-12998 [ JENKINS-12998 ]

Matthew DeTullio made changes - 2016-07-01 21:24

Resolution		New: Won't Fix [ 2 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:57

Workflow

Original: JNJira [ 167828 ]

New: JNJira + In-Review [ 198286 ]