Unfortunately there is no way to configure travis not to send build
notifications for forked repositories.
But the Jenkins builds have mysteriously started to work again (however
I had to disable two tests).
We might want to switch back, but as long as nobody is able to configure
the Jenkins builds, I'd rather leave it this way.
Am 03.12.2015 um 21:26 schrieb Travis CI:
Build Update for kidaa13/tapestry-5
-------------------------------------
Build: #1
Status: Passed
Duration: 31 minutes and 31 seconds
Commit: 5759d41 (master)
Author: Kida Kadeshia
Message: Modifications
View the changeset:
https://github.com/kidaa13/tapestry-5/compare/2f81c8735419...5759d413fcc1
View the full build log and details:
https://travis-ci.org/kidaa13/tapestry-5/builds/94716990
--
You can configure recipients for build notifications in your .travis.yml file.
See https://docs.travis-ci.com/user/notifications
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
