You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2013/09/19 01:48:52 UTC
[jira] [Commented] (INFRA-6394) Jenkins tabs for each {A..Z}
[ https://issues.apache.org/jira/browse/INFRA-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771409#comment-13771409 ]
Christopher Tubbs commented on INFRA-6394:
------------------------------------------
Sure, but the grouped views that are there already exist per project, and can be linked to from project documentation, without tying them to a specific user. I suppose the per-user views are a workaround... but there's merit in having links in documentation persist and not tied to a specific user (eg. maintainable by any project developer).
> Jenkins tabs for each {A..Z}
> ----------------------------
>
> Key: INFRA-6394
> URL: https://issues.apache.org/jira/browse/INFRA-6394
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Jenkins
> Reporter: Christopher Tubbs
> Assignee: Jake Farrell
> Priority: Minor
>
> Not long ago, the tabs on the Jenkins web interface (https://builds.apache.org/) changed, resulting in a lot of broken links to project builds. For example, https://builds.apache.org/view/A-F/ changed to https://builds.apache.org/view/A-D/ .
> Is there any way that these can be split into one tab per letter in {A..Z}, so web links directly to project builds can be more robust to future such changes?
--
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