UnderstandingJenkinsResults

Differences between revisions 1 and 3 (spanning 2 versions)
⇤ ← Revision 1 as of 2011-11-29 09:51:19 →
Size: 231
Editor: 94-192-45-141
Comment:
← Revision 3 as of 2011-11-30 22:19:20 → ⇥
Size: 2229
Editor: hggdh2
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe QATeam/AutomatedTesting/UnderstandingJenkinsResults here. /!\ if this is the first time you are looking at Jenkins, you might want to read an high-level [[QATeam/AutomatedTesting/UnderstandingJenkins|view]] of it.
Line 3: Line 3:
We should explain how to read jenkins results so that people can understand what is going on and have a look at the results more in depth than just the clouds. We use Jenkins for many of our automated QA processes and tests. The public instance is located [[https://jenkins.qa.ubuntu.com/|here]]; this is a read-only, no-login-required, mirror of our internal Jenkins instance. There you will find all current results for the tests, and a history of previous tests.

Usually you will want to look at a specific set of ''jobs''; each job may have one single test, a sequence of tests, or a collection of other jobs. Each set is show under a tab on the Jenkins main page, and aggregates all tests related (in whatever way we decided they are related).

The tabs currently are:

 * '''All''' -- all jobs defined on Jenkins. You should expect it to be quite a large list, and growing as time goes by
 * '''Precise''' -- all jobs relating to the Ubuntu [[https://wiki.ubuntu.com/PrecisePangolin|Precise Pangolin]] LTS development
 * '''Precise Boot Speed''' -- all jobs relating to the boot speed tests
 * '''Precise Daily ISOs''' -- all jobs relating to the daily ISO tests; these will also include the milestone testing
 * '''Precise Unity Merger''' -- all jobs relating to the Unity uploads (fixes, new versions, etc)

Other tabs will be added as needed.

The code for the tests reside on a bazaar [[https://code.launchpad.net/~ubuntu-server-iso-testing-dev/ubuntu-server-iso-testing/trunk|branch]]; you might want to get it, if you expect to contribute to the testing effort.

Currently, you can be notified of Jenkins results in either one, or both, of the following ways:
 * subscribing to the Jenkins [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-testing-notifications| mailing list]]
 * subscribing to a specific job's RSS feed (either for all, or just failed results)

Subscription to the mailing list will result in a email for each status change of a job (from successful to unstable to failed to unstable to successful); no emails are sent if there is no change in status from the previous run. Except for major, generic problems, we expect the ML's volume to be a few messages per day (or week).

Warning /!\ if this is the first time you are looking at Jenkins, you might want to read an high-level view of it.

We use Jenkins for many of our automated QA processes and tests. The public instance is located here; this is a read-only, no-login-required, mirror of our internal Jenkins instance. There you will find all current results for the tests, and a history of previous tests.

Usually you will want to look at a specific set of jobs; each job may have one single test, a sequence of tests, or a collection of other jobs. Each set is show under a tab on the Jenkins main page, and aggregates all tests related (in whatever way we decided they are related).

The tabs currently are:

  • All -- all jobs defined on Jenkins. You should expect it to be quite a large list, and growing as time goes by

  • Precise -- all jobs relating to the Ubuntu Precise Pangolin LTS development

  • Precise Boot Speed -- all jobs relating to the boot speed tests

  • Precise Daily ISOs -- all jobs relating to the daily ISO tests; these will also include the milestone testing

  • Precise Unity Merger -- all jobs relating to the Unity uploads (fixes, new versions, etc)

Other tabs will be added as needed.

The code for the tests reside on a bazaar branch; you might want to get it, if you expect to contribute to the testing effort.

Currently, you can be notified of Jenkins results in either one, or both, of the following ways:

  • subscribing to the Jenkins mailing list

  • subscribing to a specific job's RSS feed (either for all, or just failed results)

Subscription to the mailing list will result in a email for each status change of a job (from successful to unstable to failed to unstable to successful); no emails are sent if there is no change in status from the previous run. Except for major, generic problems, we expect the ML's volume to be a few messages per day (or week).

QATeam/AutomatedTesting/UnderstandingJenkinsResults (last edited 2011-12-14 14:34:40 by hggdh2)