Re: Maven Builds - Slow Build Times on Jenkins Slaves

2014-03-22 Thread Kai
Sorry for the late reply. Actually, it runs pretty quick when I run my 
maven command manually on the slave - takes about ~8 mins.

However, when I run through Jenkins, it takes between ~18-19mins for the 
job to complete.
Here are a few snippets from the console logs. Most of the areas where it 
tends to be slow is when it says "deleting .../target" directory, then says 
"archiving disabled" and stays there for like 2 mins usually, then moves 
on. And it does this for each maven module that's part of the project, so 
it adds up.
Also, takes some time, after "archiving steps", then says "archiving 
disabled", usually like up to 2 min delay before moving on.

*Snippets from Console Log*


*19:56:10 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
test-project-parent ---19:56:10 [INFO] Deleting 
/var/lib/jenkins/workspace/test-project/target19:56:13 [JENKINS] Archiving 
disabled19:58:33 [INFO]20:03:32 [JENKINS] Archiving site from 
/var/lib/jenkins/workspace/test-project-main/test-project/target/site to 
/var/lib/jenkins/jobs/test-project-main/site/test-project20:03:32 [JENKINS] 
Archiving disabled20:05:51 [INFO]   *





On Tuesday, March 18, 2014 11:15:49 PM UTC-7, Baptiste Mathus wrote:
>
> Outside Jenkins, I mean.
> Le 19 mars 2014 07:15, "Baptiste Mathus" > 
> a écrit :
>
>> Is it also slow if you run the maven build manually on that slave?
>> Le 16 mars 2014 22:57, "Kai" > a écrit :
>>
>>> Hi,
>>>
>>> We are currently on Jenkins 1.551 and are experiencing significant maven 
>>> build slowness on our jenkins slaves.
>>>
>>> It seems deleting the target directory takes forever.
>>> Also, during the site phase, a step: "Archiving site from ..." comes and 
>>> takes a while (even though archiving is disabled), then it says "archiving 
>>> disabled" and moves on.
>>>
>>> However, when the build runs on the master, I don't experience this 
>>> slowness and deleting the target directory is really quick.
>>>
>>> Has anyone else experienced this issue or know what could be causing the 
>>> slowness when building on Jenkin slaves?
>>>
>>> Thank you so much!
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-use...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Cannot write file to disk using the build Flow plugin

2014-03-22 Thread teilo
Hi Les,

Firstly a workspace will never give you true stateless in Jenkins à workspace 
availability is best effort (slave may be unavailable, workspace may be deleted 
to reclaim slave disk space...)

Depending on what state you want to store you should look at writing either an 
extension to the build flow, or a new plugin or a combination of both.

/James

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.