Continuous Integration
The Continuous Integration is very important to keep Crosswalk's high quality.
From overall perspective, a patch’s life cycle could be:
Style bot is for coding style checking. It can be combined with trybot.
Try bot mainly focuses whether coming patch set will break any build, might run some essential test cases as well. The purpose is to provide reviewer some additional information beyond code.
Build bot will run plenty of test cases including functional tests(unit tests/ui tests/etc.) and performance tests(memory/binary size/start up time/etc.). Therefore, we can detect regression at the very beginning.
Build bot will notify Reviewer and Contributor when it fails.
Code for build infrastructure is hosted at https://github.com/otcshare/build-infrastructure/tree/1469_work.
An initial build master is setup at here.
As the first step, Windows/Linux slaves are added to track crosswalk's downstream chromium. They will automatically detect the change and do compiling/testing upon it.
For now, it's building content shell and running webkit layout tests.
Setup build bot for Crosswalk after the first buildable code base is ready.
Integrate with Crosswalk's test framework.
An initial prototype is hosted at here.
It supports trying a patch based on the previous content shell based prototype.
Integrate try bot with github's pull request.
Setup try bot for content shell build, to try chromium/blink patches.
Add style check step before trying to build and test.