incubator-ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen, Pei" <Pei.C...@childrens.harvard.edu>
Subject RE: Jenkins builds take hours?
Date Wed, 24 Oct 2012 01:33:38 GMT
FYI:
Thanks Steve and Britt.  These are great suggestions.
The below have been created now:

https://builds.apache.org/job/cTAKES-trunk-compiletest/
will check for svn for changes and will run compile test
(auto archiving disabled now)

https://builds.apache.org/job/cTAKES-trunk-package/
runs @daily

Let's see how that works out.  Keep in mind that Jenkins distributes it's load across shared
hardware so if it's a new machine, it may take longer for a fresh checkout.

FYI: if you need admin access to create/edit jobs, any one of the chairs should be able to
run the command to grant you access to Jenkins (if not, open an infra jira):
modify_appgroups.pl hudson-jobadmin --add=<Apache username>

________________________________________
From: Steven Bethard [steven.bethard@Colorado.EDU]
Sent: Tuesday, October 23, 2012 8:22 PM
To: ctakes-dev@incubator.apache.org
Subject: Re: Jenkins builds take hours?

On Oct 23, 2012, at 5:41 PM, Britt Fitch <britt.fitch@gmail.com> wrote:
> In the past I have seen Hudson set up to have different build goals. Should we consider
doing a package only once per day and regular compile/test on every commit?

Note that `mvn package` isn't the problem - the entire `mvn install` only takes 15 minutes
on our Jenkins. The delay comes from Jenkins archiving stuff after the build.

But I agree that it makes a lot of sense to just run `mvn test` on every commit, and `mvn
package` only once a day. And if we're going to let Jenkins archive anything, we could restrict
it to the results of that once-daily `mvn package`.

Steve

>
> Sent from my iPhone
>
> On Oct 23, 2012, at 6:27 PM, "Chen, Pei" <Pei.Chen@childrens.harvard.edu> wrote:
>
>> 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:steven.bethard@Colorado.EDU]
>>> Sent: Tuesday, October 23, 2012 5:50 PM
>>> To: ctakes-dev@incubator.apache.org
>>> 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


Mime
View raw message