Hi folks:
As a result of my extra development activities, I took time to learn
more about using Travis CI as an auxiliary tool of our development team.
As a result, I've fixed the long standing bugs in the CI jobs of
autotest, and also took the time to set up a similar job for virt-test.
A bunch of bugs in our unittests were fixed as part of the process, and
I can say the overall result is nice.
The difference with virt-test is that it already runs 'inspekt lint'
after unittest, meaning we will also catch syntax mistakes in peoples
pull requests in an automated way, and conveniently integrated with the
github pull request view. Example:
https://github.com/autotest/virt-test/pull/1602
If you check the last commit in there, you'll see a green arrow, meaning
that the CI job passed for that PR, and the arrow also has a link to the
job links:
https://travis-ci.org/autotest/virt-test/builds/23094894
It is worth noting that PEP8 checks were not enabled yet, as they'll
take a bit more work and will be difficult to get right across everybody
developing virt-test.
As always, there's still a ton of other work to do:
1) Job for tp-qemu
2) Job for tp-libvirt
3) Job for autotest-client-tests
4) Job for autotest-server-tests
5) Add pylint and PEP8 to the autotest job
And a lot of other stuff I'm probably forgetting. I'll leave them for
another opportunity.
Meanwhile, let me know of any comments, suggestions and criticisms.
Cheers,
Lucas
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
