On 08/25/14 at 02:51pm, Thomas Graf wrote: > This enables the use of travis-ci via github. Linking any ovs > github repo to travis-ci [0] will automatically lead to a build > and testsuite run being triggered for each new commit or pull > requests against the repo.
Given the above, we can consider further integration of CI builds into the devel process: 1. Use of travis-ci on private branches. Everyone can do that by logging into travis-ci.org with your github id and by adding your ovs fork repo to travis-ci. Anytime you push to a branch on your fork, the CI build is triggered. 2. Enable travis-ci for the main repo to catch build regressions at commit time. 3. As (2) is in fact too late, the ideal integration is within patchwork. travis-ci offers both a REST API and CLI tools to allow for this but it will require to extend patchwork. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
