On 05/23/2011 05:48 PM, Gavin McDonald wrote: > Hi Guys, > >> -----Original Message----- >> From: Thorsten Scherler [mailto:[email protected]] >> Sent: Monday, 23 May 2011 7:46 PM >> To: [email protected] >> Cc: [email protected] >> Subject: Re: buildbot exception in ASF Buildbot on droids-trunk >> >> On Thu, 2011-05-19 at 17:04 -0500, Richard Frovarp wrote: >>> On 05/19/2011 04:55 PM, [email protected] wrote: >>>> The Buildbot has detected a new failure on builder droids-trunk while >> building ASF Buildbot. >>>> Full details are available at: >>>> http://ci.apache.org/builders/droids-trunk/builds/74 >>>> >>>> Buildbot URL: http://ci.apache.org/ >>>> >>>> Buildslave for this Build: isis_ubuntu >>>> >>>> Build Reason: scheduler >>>> Build Source Stamp: [branch incubator/droids/trunk] 1125136 >>>> Blamelist: rfrovarp >>>> >>>> BUILD FAILED: exception upload >>>> >>>> sincerely, >>>> -The Buildbot >>>> >>> >>> So Buildbot still used ant / ivy. > > nope > >>> >>> Running "mvn test" and everything works just fine. >>> >>> Looking at the documentation for Buildbot, I don't see anyway for us >>> to login and configure. I think a ticket needs to be opened up with infra. >>> Anyone work with this before? >> >> Gavin was so kind to setup build bot for us. >> >> I cc him (hope that is ok with you Gav) he may share some insights with us. >> >> TIA for any feedback Gav! > > Sure , no problem, > > First off, a more direct link to your builder: > > http://ci.apache.org/builders/droids-trunk > > click on any to see details of the build, ie, > > http://ci.apache.org/builders/droids-trunk/builds/80 > > this shows that steps 1 and 2 and 3 passed ok, which were > > step 1 - clean checkout > step2 - mvn clean install > step 3 - mvn deploy > > step 4 failed with > > No such file or directory: '/home/buildslave2/slave2/droids-trunk/build/docs' > > step 4 is supposed to upload the 'docs' directory, so something has changed > since I created > the build. > > The configuration files for projects using buildbot are available in svn and > committers have > read/write access to those files, yours is at: > > https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/droids.conf > > I'll assume your build has changed and that you no longer generate Forrest > docs there. > > Your site although outdated at incubator.apache.org/droids/ still uses > forrest but part of your pom.xml suggests > you might like to build the site using maven, yet I also see Forrest sources > still present. > > According to the build date at > > http://ci.apache.org/projects/droids/ > > this started failing May 13th. > > Anyway, rather than me dig too much more, please let me know (via cc) what > has changed and how you want things to happen > on the Buildbot now. > > Or, feel free to edit your config file directly, it will take affect within 5 > minutes, at which point you need only commit something > to trigger a rebuild. > > HTH > > Gav... >
Fantastic. Thanks once again for your help. The docs directory has been moved out of trunk. So that part isn't effective at this point. I commented those sections out. Committing a file triggered a build that did succeed. The one problem I found is that RAT is running over the docs files and a few others that no longer exist in our source. What cleans out the build directory? If you look here: http://ci.apache.org/projects/droids/rat-output.html doap.rdf, testng.properties, docs, and tools no longer exist in trunk. The stuff under src isn't going to exist anymore either.
