The job is already there, but not yet enabled: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-docvalues-branch/
I just want to know: - When to run - Send emails to which address It uses the trunk test script from svn/nightly. It just checks out another branch to workspace/checkout. Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Simon Willnauer [mailto:[email protected]] > Sent: Sunday, October 17, 2010 8:53 PM > To: [email protected] > Subject: Re: Continuous Integration builds for branches > > On Sun, Oct 17, 2010 at 8:46 PM, Robert Muir <[email protected]> wrote: > > On Sun, Oct 17, 2010 at 1:41 PM, Simon Willnauer > > <[email protected]> wrote: > > > >> True, but that still helps to find those little things that come out > >> if you run on trunk which can be fixed earlier. I don't think that > >> shooting those build mails to the dev list makes any sense. it should > >> go to individuals working on that branch. > > > > I don't think it should send private emails. > > > >> We have the infrastructure why not running such a build a on commit > >> and once or twice a day... I don't see any reason why we shouldn't > >> > > > > one or twice a day, this is different than 24/7. Then again, building > > on commit for a branch with one guy working on it (especially since i > > don't see a particularly large amount of commits going to any > > branches) seems overkill: that person could just run ant test > > themselves. > > I don't think hitting "copy job" and change the url is near any overkill but > I can > simply start my hudson boxes again to run the branch tests. > > > > And at the moment, I have trouble understanding how this would be > > really helpful since trunk/branch-3x itself are not even yet stable > > with regards to tests... > > as helpful as it is for branch-3x IMO but I don't have too strong feelings > about it > though. > > simon > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For > > additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
