[isabelle-dev] Jenkins SPAM reduction

Makarius makarius at sketis.net
Sat Jul 16 16:37:33 CEST 2016

Jenkins sends lots of mails, and I find it hard to pay attention to them
at all. Even when I do look, the long message body makes it hard to find
the key points: What failed? Why did it fail?

Moreover, Isabelle + AFP get naturally out of sync, because pushes on
AFP are often done later, but Jenkins assumes them to be very close.

How about this:

  * Tests are run less often, e.g. 2-3h after a push and including all
later pushes in that time interval. This reduces test runs and increases
chances that Isabelle + AFP correspond correctly when Jenkins makes a

  * Mails are sent only once per day, as a summary of broken sessions at
the end of the day, not every intermediate state.

If Jenkins were more like a queue management system, it could probably
also provide immediate feedback to the person who pushed something
broken to it.


More information about the isabelle-dev mailing list