Re: [isabelle-dev] Jenkins maintenance window

Hi Lars, > However, turns out that the actual problem was that somebody pushed > something completely unrelated (maybe a different repository?) into > testboard. This also generated a gargantuan changelog in Jenkins. I > don't blame that person, it could happen to anyone. But we need to fix >

Re: [isabelle-dev] Jenkins maintenance window

> Was it me? I think I saw a warning to that effect, but with "-f" > (which is necessary since we're creating new heads) it's too late > once the warning is shown. I can easily change the trusty old script > I use to push to testboard to make sure I do it from my Isabelle > repository. If it

Re: [isabelle-dev] Jenkins maintenance window

Hi Lars, I am unsure if an Isabelle tool is the right level of abstraction for an operation, only members of the isabelle (UNIX) group at TUM can/should execute. Also, wouldn’t a push to a fresh repository take quite long. (OK, negligible compared to the actual build, but still.) And one still

Re: [isabelle-dev] Jenkins maintenance window

On Tue, 16 Feb 2016, Dmitriy Traytel wrote: I am unsure if an Isabelle tool is the right level of abstraction for an operation, only members of the isabelle (UNIX) group at TUM can/should execute. BTW, the Isabelle tool name space is not hardwired. Any "component" can add new tool

Re: [isabelle-dev] Jenkins maintenance window

> On 16 Feb 2016, at 11:30, Makarius wrote: > > On Tue, 16 Feb 2016, Dmitriy Traytel wrote: > >> I am unsure if an Isabelle tool is the right level of abstraction for an >> operation, only members of the isabelle (UNIX) group at TUM can/should >> execute. > > BTW, the