|
||||||||
|
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.
Yes, but the list of alias will become long and unsightly on the UI. And selecting the desired alias from that list of duplicates does not resolve to the latest, because they are direct hyperlinks to the numbered builds (so each duplicate of the alias points to a different build thru its canonical url).
I would like the UI to be fixed to treat the 'pseudo-permalinks' (like lastStableBuild, lastSuccessfulBuild, and the custom last[Status][Moniker]) differently form the other aliases: be listed with the moniker url, and resolved only when the build is requested. While the other aliases can stay as is, I think it would be better to also delay resolution of the alias. However, it could affect the rendering performance of the Project page since it needs to 'curates' the pseudo permalinks.