Jenkins and Us, or Living With a Majordomo

Registered by C de-Avillez on 2011-04-22

We started using Jenkins (er, Hudson) during the Maverick cycle. Since then we have:

- expanded from server ISO tests to dekstop and alternate ISO tests
- added a few Automated Kernel Tests [1] to the mix
- added EC2 automated testing

In other words, we are growing more dependent on Jenkins (as has been known for quite a long time and, recently, by a fortunate few, life is *much* easier if one has a good majordomo. Even when said majordomo forks in new personalities). So, it would help if we decide and organise a series of points _before_ Jenkins usage turns into a (perhaps hopeless) spaghetti of tests, conflicting requests and, last but not least, a new sauna in my office (amazing how much heat is dissipated by a few computers in a 4x5 meters room).

Points to consider:

* location of Jenkins Server (currently on AWS)
* amount of Jenkins slaves (machines available for actually running the tests)
* distribution of said slaves -- both geographical and logical
* additional functionality:
  * email-on-test-error (Daviey): send an email to a person/group when a specific test fails (or category? or tag? or group?)
  * integration with TestLink: TestLink seems to be good on documenting tests, Jenkins seems to be good on executing them (patrickmw, hggdh)
  * integration with iso.qa.ubuntu.com
  * add yours

[1] http://autotest.kernel.org/

Blueprint information

Status:
Not started
Approver:
Pete Graner
Priority:
Undefined
Drafter:
C de-Avillez
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.