-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.512
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.