![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Oliver Gondža
|
|
Components:
|
build-alias-setter |
|
Created:
|
11/Sep/14 6:49 PM
|
|
Description:
|
The idea would be to select a build via the standard Jenkins UI, and assign an arbitrary (subject to input validation) alias to it, i.e. the build page is now available thru a url utilizing the new alias (as you would expect from an alias that has been automatically assigned during the actual build).
Fancy: detect if this alias is already used (by another build), offer to move it to the present build. (btw, it would be nice to be able to "revoke" an existing alias, whether previously assigned manually or automatically).
This feature would be useful for manual processes around build promotion or build marking.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Patrice Matignon
|
|
|
|
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/d/optout.
