Tech:Continuous integration: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
(+) |
(+dns travis checks) |
||
| Line 8: | Line 8: | ||
* If the change has already been merged then it should be reverted and then fixed! |
* If the change has already been merged then it should be reverted and then fixed! |
||
* If you merge pull request before Travis CI job starts, Travis CI will be failed! |
* If you merge pull request before Travis CI job starts, Travis CI will be failed! |
||
; DNS |
|||
Travis CI also runs against our DNS repo. The basic rule of thumb for this should be to '''never''' merge a change without having Travis run a test on it (unless a fairly no-op commit). If Travis fails - '''never''' merge the commit regardless. Travis runs the same checks GDNSD runs - if Travis fails, the service will fail in production, rendering our DNS servers offline. |
|||
Revision as of 21:08, 11 October 2014
Travis CI is a continuous integration service used by Orain (see .travis.yml for details).
On every new pull request or commit, Travis CI will run a series of checks on the repo.
See https://travis-ci.org/Orain/ansible-playbook
- If Travis CI fails for a valid reason for any commit that commit should not be merged!
- If the change has already been merged then it should be reverted and then fixed!
- If you merge pull request before Travis CI job starts, Travis CI will be failed!
- DNS
Travis CI also runs against our DNS repo. The basic rule of thumb for this should be to never merge a change without having Travis run a test on it (unless a fairly no-op commit). If Travis fails - never merge the commit regardless. Travis runs the same checks GDNSD runs - if Travis fails, the service will fail in production, rendering our DNS servers offline.