Re: [isabelle-dev] Jenkins reconfiguration

2018-07-02 Thread Makarius
On 29/06/18 19:31, Lars Hupel wrote: >> Does it mean that the great new hardware is now locked up and >> exclusively available for Jenkins? > > That assessment is accurate. That is bad. It means that the development process will continue to decline, as we have seen in the past few years -- it

Re: [isabelle-dev] Jenkins reconfiguration

2018-06-29 Thread Lars Hupel
Does it mean that the great new hardware is now locked up and exclusively available for Jenkins? That assessment is accurate. ___ isabelle-dev mailing list isabelle-...@in.tum.de

Re: [isabelle-dev] Jenkins reconfiguration

2018-06-29 Thread Makarius
On 28/06/18 11:41, Lars Hupel wrote: > Dear Isabelle developers, > > you may have already noticed that some Jenkins jobs got reconfigured. > > The following changes are relevant for developers: > > - The new job "isabelle-all" runs Isabelle+AFP together, incrementally. > This should improve

Re: [isabelle-dev] Jenkins reconfiguration

2018-06-29 Thread Lars Hupel
> - The "testboard" job will also be replaced to run Isabelle+AFP > together. Historic builds will be deleted, as they are not relevant for > the official history. I have implemented this now. I'm currently monitoring the situation, but so far, it seems like this sped up the process overall.

[isabelle-dev] Jenkins reconfiguration

2018-06-28 Thread Lars Hupel
Dear Isabelle developers, you may have already noticed that some Jenkins jobs got reconfigured. The following changes are relevant for developers: - The new job "isabelle-all" runs Isabelle+AFP together, incrementally. This should improve overall performance and avoid double builds. There is,