![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
promoted-builds |
|
Created:
|
11/Jan/14 11:07 PM
|
|
Description:
|
With multiple promotion options that differ only by one token, which is the same as the promotion name itself, it would be great to be able to create one promotion block that is optionally executed for a range of promotions.
IOW, Say I have a promotion names P1. It does things with files/P1/...
Then I need to create other promotions, P2, P3, etc, that need to do the exact same thing relative to the promotion name, files/P2/... and files/P3/... .
A better option would be to define the promotion block once, then define the promotion names for which it could be executed.
Currently I have to replicate the entire promotion block, which is very non-DRY when testflight is involved as there's a lot of boilerplate that goes into every promotion block.
|
|
Environment:
|
Linux 64
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Bruce Edge
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
