> > that would be an option, but during our work, Mike and me only > activated the "start new build" button in the GUI, everything else was > and had to be done in the shell: > > - Updating lucene's private SVN tools for the new lucene rev-based > backwards branch (sparse checkout) > > - Upgrading hudson's clover version for our new coverage reports > (that work correct with backwards branch) > > - Killing stuck builds (to get a stack trace you have to send a > SIGHUP to the stuck JVM first) > > > > We can certainly get you access to the Lucene Zone as that is up to the > Lucene PMC, as that is where Hudson always runs Lucene jobs. So, that > plus Hudson UI access would likely solve most issues right?
Yes.
