On Thu, Aug 9, 2012 at 9:13 AM, Matthias Friedrich <[email protected]> wrote: > Hey guys, > > I have re-enabled the build jobs and email notifications. The builds > worked again after I forced them to a different build slave (thanks, > Rahul!). I also had git clean the workspace before running the build; > this would have prevented the build failure caused by CRUNCH-32 > (left-over files that the license check didn't like). Notifications > are now only sent once when a build breaks, subsequent failures don't > send emails to keep spam down. > > From work I know that Jenkins installations with several hundreds of > jobs typically cause some trouble. I hope this rocky start doesn't > discourage anyone from using CI, smaller setups usually work fine. > > @Josh: Is there any reason why we're using the github mirror and for > this particular polling strategy?
Nope, I think when I was setting it up, it was the first one that, like, worked. :) > > Regards, > Matthias > > > On Thursday, 2012-08-09, Rahul wrote: >> The current issue that we are facing has also been reported on few >> other Apache projects like : >> http://lucene.472066.n3.nabble.com/Build-failed-in-Jenkins-nutch-trunk-maven-325-td3991061.html >> http://comments.gmane.org/gmane.comp.java.hadoop.hbase.devel/28552 >> http://mail-archives.apache.org/mod_mbox/www-builds/201203.mbox/%[email protected]%3E >> >> Looking at the mailing archives timestamps it looks like the job >> would fail when we have the job ending on the same slave(on which it >> failed initially). >> The same issue is reported in Jenkins Jira at >> https://issues.jenkins-ci.org/browse/JENKINS-6604. The solution that >> people have resorted to is restarting the server. >> I think the build could be successful again when it finds a new slave. >> >> regards, >> Rahul >> >> On 09-08-2012 11:35, Matthias Friedrich wrote: >> >Hi, >> > >> >right now, things seem to be really broken in Jenkins itself. I don't >> >think it's a problem with our configuration, a new job I created had >> >the same problem. No surprise there, Jenkins is an extremely buggy piece >> >of software. >> > >> >I have disabled the job for now until I've got time to take a closer look. >> > >> >Regards, >> > Matthias >> > >> >On Wednesday, 2012-08-08, Josh Wills wrote: >> >>Updated it-- thanks Rahul. >> >> >> >>On Wed, Aug 8, 2012 at 8:58 PM, Rahul <[email protected]> wrote: >> >>>Hi >> >>> >> >>>Do we require internal tagging ? I think we can turn down the same. Both >> >>>our >> >>>builds failed due to the same reason. >> >>>Here is the link how to skip it : >> >>>http://fijiaaron.wordpress.com/2012/03/08/skip-internal-tag-jenkins-git/ >> >>> >> >>>regards, >> >>>Rahul >> >>> >> >>>On 09-08-2012 07:44, Apache Jenkins Server wrote: >> >>>>See <https://builds.apache.org/job/Crunch-master-integration/3/> >> >>>> >> >>>>------------------------------------------ >> >>>>Started by timer >> >>>>Building remotely on ubuntu4 in workspace >> >>>><https://builds.apache.org/job/Crunch-master-integration/ws/> >> >>>>Checkout:Crunch-master-integration / >> >>>><https://builds.apache.org/job/Crunch-master-integration/ws/> - >> >>>>hudson.remoting.Channel@155094e7:ubuntu4 >> >>>>Using strategy: Default >> >>>>Last Built Revision: Revision a92a523fb72a3d3180d43115762442e4ccf881f3 >> >>>>(origin/master) >> >>>>Cloning the remote Git repository >> >>>>Cloning repository origin >> >>>>Fetching upstream changes from http://github.com/apache/incubator-crunch >> >>>>Commencing build of Revision c12ef81090bbc142ed865592bb1a497699376c24 >> >>>>(origin/master) >> >>>>Checking out Revision c12ef81090bbc142ed865592bb1a497699376c24 >> >>>>(origin/master) >> >>>>FATAL: Could not apply tag jenkins-Crunch-master-integration-3 >> >>>>hudson.plugins.git.GitException: Could not apply tag >> >>>>jenkins-Crunch-master-integration-3 >> >>>> at hudson.plugins.git.GitAPI.tag(GitAPI.java:751) >> >>>> at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1321) >> >>>> at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1269) >> >>>> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196) >> >>>> at hudson.remoting.UserRequest.perform(UserRequest.java:118) >> >>>> at hudson.remoting.UserRequest.perform(UserRequest.java:48) >> >>>> at hudson.remoting.Request$2.run(Request.java:326) >> >>>> at >> >>>>hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) >> >>>> at >> >>>>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >> >>>> at java.util.concurrent.FutureTask.run(FutureTask.java:166) >> >>>> at >> >>>>java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) >> >>>> at >> >>>>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) >> >>>> at java.lang.Thread.run(Thread.java:679) >> >>>>Caused by: hudson.plugins.git.GitException: Command "git tag -a -f -m >> >>>>Jenkins Build #3 jenkins-Crunch-master-integration-3" returned status >> >>>>code >> >>>>128: >> >>>>stdout: >> >>>>stderr: >> >>>>*** Please tell me who you are. >> >>>> >> >>>>Run >> >>>> >> >>>> git config --global user.email "[email protected]" >> >>>> git config --global user.name "Your Name" >> >>>> >> >>>>to set your account's default identity. >> >>>>Omit --global to set the identity only in this repository. >> >>>> >> >>>>fatal: empty ident <[email protected] >> >>>>>not allowed >> >>>> at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:818) >> >>>> at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:780) >> >>>> at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:790) >> >>>> at hudson.plugins.git.GitAPI.tag(GitAPI.java:749) >> >>>> ... 12 more >> >>> >> >> >> >> >> >>-- >> >>Director of Data Science >> >>Cloudera >> >>Twitter: @josh_wills >> -- Director of Data Science Cloudera Twitter: @josh_wills
