Ubuntu Continuous Integration Engineering
Dual concerns of CI
The CI Engine needs to be careful to not slow development velocity. Developers should be able to continue working as their code is evaluated for quality and inclusion in Ubuntu. If we cannot move fast, we'll fail to effectively compete.
The CI Engine needs to increase debugging velocity. Changes are tested in fundamental pieces like branches for their inclusiveness in:
- The trunk of a project.
- A package build.
- A released stable image with just the changed packages.
- The released development image.
- The image to be produced.
- It ensures that problems are well isolated and provides a very small window to bisect through, ensuring that problems are flagged quickly, found quickly, and fixed quickly.
Adding a new test to run under CI
CI/ProposedMigration - How to reproduce results from proposed migration testing.
Executing CI Testing Locally
Ubuntu Touch Image (Smoke) Testing: http://ubuntu-test-cases-touch.readthedocs.org/en/latest/