Travis is set up for testing pull requests and potentially other free GitHub-integrated services like coveralls, though if we looked into it, I bet we could do all those things strictly with Jenkins somehow.
On 26 May 2017 at 06:27, Mikael Ståldal <[email protected]> wrote: > Link to Travis CI build: > > https://travis-ci.org/apache/logging-log4j2/builds/236303848 > ?utm_source=github_status&utm_medium=notification > > > > On 2017-05-26 13:20, Mikael Ståldal wrote: > >> Now the Travis CI build almost works, but fails with: >> ----- >> The log length has exceeded the limit of 4 MB (this usually means that >> the test suite is raising the same exception over and over). >> >> The job has been terminated >> ----- >> >> After 49 minutes. >> >> Why do we even use Travis CI when we have Jenkins? Jenkins works and is >> almost twice as fast (29 minutes). >> >> Can't we connect Jenkins to GitHub instead? I know that's possible. >> >> > -- Matt Sicker <[email protected]>
