How about pushing feature branches instead? Cheers, Gerwin
> On 16 Feb 2016, at 09:25, Lars Hupel <hu...@in.tum.de> wrote: > >> tonight between 20:00 UTC and 22:00 UTC there will be a maintenance >> window for the Jenkins instance. > > Maintenance period is over now. All builds are running again. > > Mails are not yet sent to the mailing list, neither is there a benchmark > job. The reason follows. > > > There was some weirdness wrt to the testboard. New jobs would suddenly > complain about 'bin/isabelle not found' or similar. My suspicion was > that either Jenkins, Mercurial or both got confused about the meaning of > the "default" branch (possibly an ancient revision which reappeared?), > so I nuked and re-create all testboard jobs, resulting in the loss of > old builds (those weren't of much value anyway). > > 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 > this workflow of force-pushing into some "dumping ground" repository. > Any ideas? > > Cheers > Lars > _______________________________________________ > isabelle-dev mailing list > isabelle-...@in.tum.de > https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments. _______________________________________________ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
