Agreed. It shouldn't take hours :) ; will take a closer look at the archiving process (I think it's due to the size of our distributions- close to 1GB). I think the archive is primarily used in case you want to take a look at what was built by the CI; it's currently set to save the last 3 builds. We can probably skip this step.. --Pei
> -----Original Message----- > From: Steven Bethard [mailto:[email protected]] > Sent: Tuesday, October 23, 2012 5:50 PM > To: [email protected] > Subject: Jenkins builds take hours? > > So it seems like, while Maven clean/compile/test takes at most a few > minutes, each of our builds on Jenkins takes many hours: > > Build #18 Took 9 hr 24 min > Build #19 has been executing for 4 hr 13 min > > It seems like they're getting hung up on some "archiving" step. For example, > consider: > > https://builds.apache.org/job/cTAKES-trunk/19/console > > I see: > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 13:32.809s > [INFO] Finished at: Tue Oct 23 17:42:21 UTC 2012 [INFO] Final Memory: > 25M/345M [INFO] > ----------------------------------------------------------------------- > - > > So I know the whole `mvn install` takes less than 15 minutes. The rest of the > time seems to be waiting on things like: > > [JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/cTAKES- > trunk/ctakes-distribution/target/apache-ctakes-3.0.0-incubating-SNAPSHOT- > src.zip to /home/hudson/hudson/jobs/cTAKES- > trunk/modules/org.apache.ctakes$ctakes-distribution/builds/2012-10- > 23_17-28-31/archive/org.apache.ctakes/ctakes-distribution/3.0.0-incubating- > SNAPSHOT/ctakes-distribution-3.0.0-incubating-SNAPSHOT-src.zip > > What are these? And how important are they? > > I personally would have expected Jenkins to report build errors within 15-30 > minutes. Definitely not 9 hours later... > > Steve
