[isabelle-dev] Jenkins maintenance

[Lars Hupel]

> This reminds me of a still open question: Why is there this "continuous
> integration" on every push anyway?

This question is not open; it has been answered quite often in the past.

For the repositories, it serves as a reminder to not push "broken"
changes. (Or at least repair problems when they appear, with a clear
picture of what exactly happened.) This may happen to all of us, and in
fact, happens to all of us.

For the testboards, the answer is even simpler: developers would like to
get immediate feedback for testing bigger changes without a manual hg
push/ssh/isabelle build cycle. This is hardly a new concept – it's not
just industry standard, but even best practice (the term "Continuous
integration" itself traces back to 1991). There is no point in going
back to an outdated development model.

Cheers
Lars