Merge lp:~jml/canonical-identity-provider/tarmac-tests into lp:canonical-identity-provider/release
Proposed by
Jonathan Lange
| Status: | Merged |
|---|---|
| Approved by: | Ricardo Kirkner |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 550 |
| Proposed branch: | lp:~jml/canonical-identity-provider/tarmac-tests |
| Merge into: | lp:canonical-identity-provider/release |
| Diff against target: |
14 lines (+10/-0) 1 file modified
tarmac_tests.sh (+10/-0) |
| To merge this branch: | bzr merge lp:~jml/canonical-identity-provider/tarmac-tests |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Ricardo Kirkner (community) | Approve | ||
| Vincent Ladeuil (community) | Approve | ||
|
Review via email:
|
|||
Commit message
Add tarmac_tests.sh, so CI tests are controlled from the branch
Description of the change
One thing that's worked well for us is having a script in the branch
that is solely dedicated to running the pre-merge tests. Jenkins is
configured to tell tarmac to run this script.
That way, once pre-merge testing is set up, the way that tests are run
can itself be changed with a guarantee that it will only get through to
trunk if it continues to work.
It also provides handy version control for this key part of the
configuration.
cheers,
jml
To post a comment you must log in.
Revision history for this message
| Jonathan Lange (jml) wrote | # |
Revision history for this message
| Jonathan Lange (jml) wrote | # |
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
+1 on the idea, the more we control the tests we run (and *how* to run them and why we change that) the better.