[xwiki-devs] [Feedback] Evaluation of Travis as a CI tool
Dear devs, It's been a while I'm using Travis-CI.org as a CI tool for my projects. And I thought why not using it with XWiki? So I investigate a bit with xwiki/xwiki-commons [1]. If you don't want to read the details below, here is a resume. I would push to keep Jenkins at this point (much more complete than Travis) but, one killing-feature is missing (in my opinion): integration with Github (display the result of a build in Pull Request is of great value when evaluating a PR). The following list is not exhaustive and is mainly about the most important features I've noticed. ### Travis # Benefit * We don't maintain a server * It's well-integrated with Github * It builds Pull Requests * It builds Branches * UI is pretty nice (at least better than Jenkins, hey!) # Drawbacks * You cannot choose which branches you want to build (all or none) * The UI is crashing often on Firefox (blocks the browser for few seconds before Firefox propose to kill the script) * You only have a raw log (meaning Travis cannot present information of the log with a organised structure) ### Jenkins # Benefits * We already have it and it works * It's specifically adapted for Java project (much much more details to parse the result of the build logs) * It can build branches * It can build Pull Requests # Drawbacks * Consumes a lot of resources on our servers * UI is not easy to browse (note that it show much more than Travis so of course, it's more difficult to do an UI with more information!) [1] https://travis-ci.org/woshilapin/xwiki-commons/ -- Jean Simard [email protected] Research engineer at XWiki SAS http://www.xwiki.com Committer on the XWiki.org project http://www.xwiki.org
Hello Jean and thanks for this analysis. It's interesting to look at others CI, especially Travis-CI which is very popular nowadays. To me, "You only have a raw log (meaning Travis cannot present information of the log with a organised structure)" is a no-go. Same for "You cannot choose which branches you want to build (all or none)". An other benefit of Jenkins is that we do not depend on an external company that can close their service whenever they want. Thanks, Guillaume 2015-12-03 14:23 GMT+01:00 Jean SIMARD <[email protected]>:
Dear devs,
It's been a while I'm using Travis-CI.org as a CI tool for my projects. And I thought why not using it with XWiki? So I investigate a bit with xwiki/xwiki-commons [1].
If you don't want to read the details below, here is a resume. I would push to keep Jenkins at this point (much more complete than Travis) but, one killing-feature is missing (in my opinion): integration with Github (display the result of a build in Pull Request is of great value when evaluating a PR).
The following list is not exhaustive and is mainly about the most important features I've noticed.
### Travis # Benefit
* We don't maintain a server * It's well-integrated with Github * It builds Pull Requests * It builds Branches * UI is pretty nice (at least better than Jenkins, hey!)
# Drawbacks
* You cannot choose which branches you want to build (all or none) * The UI is crashing often on Firefox (blocks the browser for few seconds before Firefox propose to kill the script) * You only have a raw log (meaning Travis cannot present information of the log with a organised structure)
### Jenkins # Benefits
* We already have it and it works * It's specifically adapted for Java project (much much more details to parse the result of the build logs) * It can build branches * It can build Pull Requests
# Drawbacks
* Consumes a lot of resources on our servers * UI is not easy to browse (note that it show much more than Travis so of course, it's more difficult to do an UI with more information!)
[1] https://travis-ci.org/woshilapin/xwiki-commons/ -- Jean Simard [email protected] Research engineer at XWiki SAS http://www.xwiki.com Committer on the XWiki.org project http://www.xwiki.org _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
For the record, I have played a bit with Travis CI too (I was curious), and I managed to execute integration tests with it, with the following .travis.yml file: https://raw.githubusercontent.com/xwiki-contrib/application-tour/fb00372365d... Where maven-settings.xml describes the nexus repositories of xwiki.org: https://github.com/xwiki-contrib/application-tour/blob/fb00372365d9d0b43cd2b... Thanks, 2015-12-14 13:02 GMT+01:00 Guillaume "Louis-Marie" Delhumeau < [email protected]>:
Hello Jean and thanks for this analysis. It's interesting to look at others CI, especially Travis-CI which is very popular nowadays.
To me, "You only have a raw log (meaning Travis cannot present information of the log with a organised structure)" is a no-go. Same for "You cannot choose which branches you want to build (all or none)".
An other benefit of Jenkins is that we do not depend on an external company that can close their service whenever they want.
Thanks, Guillaume
2015-12-03 14:23 GMT+01:00 Jean SIMARD <[email protected]>:
Dear devs,
It's been a while I'm using Travis-CI.org as a CI tool for my projects. And I thought why not using it with XWiki? So I investigate a bit with xwiki/xwiki-commons [1].
If you don't want to read the details below, here is a resume. I would push to keep Jenkins at this point (much more complete than Travis) but, one killing-feature is missing (in my opinion): integration with Github (display the result of a build in Pull Request is of great value when evaluating a PR).
The following list is not exhaustive and is mainly about the most important features I've noticed.
### Travis # Benefit
* We don't maintain a server * It's well-integrated with Github * It builds Pull Requests * It builds Branches * UI is pretty nice (at least better than Jenkins, hey!)
# Drawbacks
* You cannot choose which branches you want to build (all or none) * The UI is crashing often on Firefox (blocks the browser for few seconds before Firefox propose to kill the script) * You only have a raw log (meaning Travis cannot present information of the log with a organised structure)
### Jenkins # Benefits
* We already have it and it works * It's specifically adapted for Java project (much much more details to parse the result of the build logs) * It can build branches * It can build Pull Requests
# Drawbacks
* Consumes a lot of resources on our servers * UI is not easy to browse (note that it show much more than Travis so of course, it's more difficult to do an UI with more information!)
[1] https://travis-ci.org/woshilapin/xwiki-commons/ -- Jean Simard [email protected] Research engineer at XWiki SAS http://www.xwiki.com Committer on the XWiki.org project http://www.xwiki.org _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
participants (3)
-
Guillaume "Louis-Marie" Delhumeau -
Guillaume Delhumeau
-
Jean SIMARD