![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
03/May/13 9:22 AM
|
|
Description:
|
According to "The Jenkins Book" it is a good idea to separate different jobs, e. g. to have IT tests running only once a day, but have Unit Tests running after SCM change, etc. In fact this is a good idea, but it results in lots of jobs in the roster.
My proposal for improvement would be to make a hierarchic roster which can collapse projects:
[+] MyProject1
[+] MyProject2
[-] MyProject3
MyJob1
MyJob2
MyJob3
The default should be "all collapsed", so only project overall status is visiable, and to show up the single jobs of each project only when expanding the tree.
|
|
Environment:
|
Jenkins 1.512
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Markus KARG
|
|
|
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
