Re: no code analysis showing up with my builds

[Ulli Hafner]

Ok, then the registration is done correctly. 

Seems that the plug-ins don't detect that the corresponding maven goal is 
started. How do you invoke findbugs in maven? When started with 
findbugs:findbugs then everything should work out of the box…

Ulli


Am 04.10.2012 um 02:37 schrieb Rob Withers :

> One last thing I see.  I deleted the config.xml inside the modules 
> subdirectory and copied the config.xml from the modules\murmur-events 
> direcotory to the modules subdirectory.  Then I reran the build.  THe result 
> did NOT have the analysis done and the config.xml in the modules 
> subdirectory, after running the build, did NOT have the reporters section 
> with the analysis tools.
> 
> Tchuss,
> Rob
> 
> -Original Message- From: Rob Withers
> Sent: Wednesday, October 03, 2012 7:46 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis showing up with my builds
> 
> Oops, I just saw that I have 2 config.xml files in my project.
> 
> One is here: C:\software\Jenkins\jobs\murmur-events
> 
> The other is here:
> C:\software\Jenkins\jobs\murmur-events\modules\murmur-events$murmur-events
> 
> The one inside the modules directory does not have the analysis reporters
> section.
> 
> Rob
> 
> -Original Message- From: Ulli Hafner
> Sent: Wednesday, October 03, 2012 5:51 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis showing up with my builds
> 
> Is there a Findbugs action in your job's config.xml file?
> 
> Ulli
> Am 03.10.2012 um 19:00 schrieb Rob Withers :
> 
>> There are no logs for analysis tools in the console log.
>> 
>> Rob
>> 
>> -Original Message- From: Ulli Hafner
>> Sent: Wednesday, October 03, 2012 12:47 PM
>> To: jenkinsci-users@googlegroups.com
>> Subject: Re: no code analysis showing up with my builds
>> 
>> The analysis plug-ins log their results in the console log. Is there 
>> something printed out?
>> E.g. [FINDBUGS] Parsing...
>> 
>> Does your build produce the artifacts (e.g. FindBugs results XML file) that 
>> are read as input by the plugins?
>> 
>> Ulli
>> 
>> Am 03.10.2012 um 17:05 schrieb Rob Withers :
>> 
>>> I have the following plugins loaded:
>>> 1) JUnit Attachments Plugin
>>> 2) Static Analysis Utilities
>>> 3) Static Analysis Collector Plug-in
>>> 4) Checkstyle Plug-in
>>> 5) PMD Plug-in
>>> 6) FindBugs
>>> 7) DRY
>>> 
>>> My issue is no results are showing up when I do a build.  I have enabled 
>>> the project to get these results.  What gives?
>>> 
>>> thanks,
>>> Rob
>> 
> 

Re: no code analysis showing up with my builds

[Ulli Hafner]

Ok, then the registration is done correctly. 

Seems that the plug-ins don't detect that the corresponding maven goal is 
started. How do you invoke findbugs in maven? When started with 
findbugs:findbugs then everything should work out of the box…

Ulli


Am 04.10.2012 um 02:37 schrieb Rob Withers :

> One last thing I see.  I deleted the config.xml inside the modules 
> subdirectory and copied the config.xml from the modules\murmur-events 
> direcotory to the modules subdirectory.  Then I reran the build.  THe result 
> did NOT have the analysis done and the config.xml in the modules 
> subdirectory, after running the build, did NOT have the reporters section 
> with the analysis tools.
> 
> Tchuss,
> Rob
> 
> -Original Message- From: Rob Withers
> Sent: Wednesday, October 03, 2012 7:46 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis showing up with my builds
> 
> Oops, I just saw that I have 2 config.xml files in my project.
> 
> One is here: C:\software\Jenkins\jobs\murmur-events
> 
> The other is here:
> C:\software\Jenkins\jobs\murmur-events\modules\murmur-events$murmur-events
> 
> The one inside the modules directory does not have the analysis reporters
> section.
> 
> Rob
> 
> -Original Message- From: Ulli Hafner
> Sent: Wednesday, October 03, 2012 5:51 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis showing up with my builds
> 
> Is there a Findbugs action in your job's config.xml file?
> 
> Ulli
> Am 03.10.2012 um 19:00 schrieb Rob Withers :
> 
>> There are no logs for analysis tools in the console log.
>> 
>> Rob
>> 
>> -Original Message- From: Ulli Hafner
>> Sent: Wednesday, October 03, 2012 12:47 PM
>> To: jenkinsci-users@googlegroups.com
>> Subject: Re: no code analysis showing up with my builds
>> 
>> The analysis plug-ins log their results in the console log. Is there 
>> something printed out?
>> E.g. [FINDBUGS] Parsing...
>> 
>> Does your build produce the artifacts (e.g. FindBugs results XML file) that 
>> are read as input by the plugins?
>> 
>> Ulli
>> 
>> Am 03.10.2012 um 17:05 schrieb Rob Withers :
>> 
>>> I have the following plugins loaded:
>>> 1) JUnit Attachments Plugin
>>> 2) Static Analysis Utilities
>>> 3) Static Analysis Collector Plug-in
>>> 4) Checkstyle Plug-in
>>> 5) PMD Plug-in
>>> 6) FindBugs
>>> 7) DRY
>>> 
>>> My issue is no results are showing up when I do a build.  I have enabled 
>>> the project to get these results.  What gives?
>>> 
>>> thanks,
>>> Rob
>> 
> 

Re: no code analysis showing up with my builds

[Rob Withers]

One last thing I see.  I deleted the config.xml inside the modules 
subdirectory and copied the config.xml from the modules\murmur-events 
direcotory to the modules subdirectory.  Then I reran the build.  THe result 
did NOT have the analysis done and the config.xml in the modules 
subdirectory, after running the build, did NOT have the reporters section 
with the analysis tools.


Tchuss,
Rob

-Original Message- 
From: Rob Withers

Sent: Wednesday, October 03, 2012 7:46 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

Oops, I just saw that I have 2 config.xml files in my project.

One is here: C:\software\Jenkins\jobs\murmur-events

The other is here:
C:\software\Jenkins\jobs\murmur-events\modules\murmur-events$murmur-events

The one inside the modules directory does not have the analysis reporters
section.

Rob

-Original Message- 
From: Ulli Hafner

Sent: Wednesday, October 03, 2012 5:51 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

Is there a Findbugs action in your job's config.xml file?

Ulli
Am 03.10.2012 um 19:00 schrieb Rob Withers :


There are no logs for analysis tools in the console log.

Rob

-Original Message- From: Ulli Hafner
Sent: Wednesday, October 03, 2012 12:47 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

The analysis plug-ins log their results in the console log. Is there 
something printed out?

E.g. [FINDBUGS] Parsing...

Does your build produce the artifacts (e.g. FindBugs results XML file) 
that are read as input by the plugins?


Ulli

Am 03.10.2012 um 17:05 schrieb Rob Withers :


I have the following plugins loaded:
1) JUnit Attachments Plugin
2) Static Analysis Utilities
3) Static Analysis Collector Plug-in
4) Checkstyle Plug-in
5) PMD Plug-in
6) FindBugs
7) DRY

My issue is no results are showing up when I do a build.  I have enabled 
the project to get these results.  What gives?


thanks,
Rob

Re: no code analysis showing up with my builds

[Rob Withers]

Oops, I just saw that I have 2 config.xml files in my project.

One is here: C:\software\Jenkins\jobs\murmur-events

The other is here: 
C:\software\Jenkins\jobs\murmur-events\modules\murmur-events$murmur-events


The one inside the modules directory does not have the analysis reporters 
section.


Rob

-Original Message- 
From: Ulli Hafner

Sent: Wednesday, October 03, 2012 5:51 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

Is there a Findbugs action in your job's config.xml file?

Ulli
Am 03.10.2012 um 19:00 schrieb Rob Withers :


There are no logs for analysis tools in the console log.

Rob

-Original Message- From: Ulli Hafner
Sent: Wednesday, October 03, 2012 12:47 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

The analysis plug-ins log their results in the console log. Is there 
something printed out?

E.g. [FINDBUGS] Parsing...

Does your build produce the artifacts (e.g. FindBugs results XML file) 
that are read as input by the plugins?


Ulli

Am 03.10.2012 um 17:05 schrieb Rob Withers :


I have the following plugins loaded:
1) JUnit Attachments Plugin
2) Static Analysis Utilities
3) Static Analysis Collector Plug-in
4) Checkstyle Plug-in
5) PMD Plug-in
6) FindBugs
7) DRY

My issue is no results are showing up when I do a build.  I have enabled 
the project to get these results.  What gives?


thanks,
Rob

Re: no code analysis showing up with my builds

[Rob Withers]

Tchuss Ulli,

I have reporters, but no "actions", if those are a separate section of the 
xml.  This is coming from the config.xml inside the jobs directory, and then 
inside my project directory.


Here is the reporters section...

Danke,
Rob


 
   
   
   [CHECKSTYLE] 
   low
   false
   false
   
 
 
 
 
 
 
 
 
   
   true
 
 
   
   
   [FINDBUGS] 
   low
   false
   false
   
 
 
 
 
 
 
 
 
   
   true
   false
 
 
   
   
   [PMD] 
   low
   false
   false
   
 
 
 
 
 
 
 
 
   
   true
 
 
   
   
   [DRY] 
   low
   false
   false
   
 
 
 
 
 
 
 
 
   
   true
   50
   25
 
 
   reefed...@gmail.com
   false
   false
   true
 



-Original Message- 
From: Ulli Hafner

Sent: Wednesday, October 03, 2012 5:51 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

Is there a Findbugs action in your job's config.xml file?

Ulli
Am 03.10.2012 um 19:00 schrieb Rob Withers :


There are no logs for analysis tools in the console log.

Rob

-Original Message- From: Ulli Hafner
Sent: Wednesday, October 03, 2012 12:47 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

The analysis plug-ins log their results in the console log. Is there 
something printed out?

E.g. [FINDBUGS] Parsing...

Does your build produce the artifacts (e.g. FindBugs results XML file) 
that are read as input by the plugins?


Ulli

Am 03.10.2012 um 17:05 schrieb Rob Withers :


I have the following plugins loaded:
1) JUnit Attachments Plugin
2) Static Analysis Utilities
3) Static Analysis Collector Plug-in
4) Checkstyle Plug-in
5) PMD Plug-in
6) FindBugs
7) DRY

My issue is no results are showing up when I do a build.  I have enabled 
the project to get these results.  What gives?


thanks,
Rob

Re: force a a job run on every node

[phil swenson]

Just got it going.  I switched from using labels in the Configuration
Matrix to Individual Nodes and it works.

Not sure why, but I'm happy

On Wed, Oct 3, 2012 at 3:46 PM, Richard Lavoie  wrote:
> Matrix build should let you run a job multiple times and iirc there is 
> aplugin to add a node label axis (might be node label plugin)
>
>
>
> On 2012-10-03, at 17:26, phil swenson  wrote:
>
>> well, it's not running on every node.  I kick off a job and it only
>> goes to one node.
>>
>> so still stuck….
>>
>> On Wed, Oct 3, 2012 at 3:21 PM, phil swenson  wrote:
>>> trying a multi-configuration build now.  think this will give me what i want
>>>
>>> On Wed, Oct 3, 2012 at 2:54 PM, phil swenson  wrote:
 I'm using gradle and periodically I need to run a specific task on
 every node to clean out the cache.

 Is there a way I can force a job to run on all nodes?

 thanks

Re: no code analysis showing up with my builds

[Ulli Hafner]

Is there a Findbugs action in your job's config.xml file?

Ulli
Am 03.10.2012 um 19:00 schrieb Rob Withers :

> There are no logs for analysis tools in the console log.
> 
> Rob
> 
> -Original Message- From: Ulli Hafner
> Sent: Wednesday, October 03, 2012 12:47 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis showing up with my builds
> 
> The analysis plug-ins log their results in the console log. Is there 
> something printed out?
> E.g. [FINDBUGS] Parsing...
> 
> Does your build produce the artifacts (e.g. FindBugs results XML file) that 
> are read as input by the plugins?
> 
> Ulli
> 
> Am 03.10.2012 um 17:05 schrieb Rob Withers :
> 
>> I have the following plugins loaded:
>> 1) JUnit Attachments Plugin
>> 2) Static Analysis Utilities
>> 3) Static Analysis Collector Plug-in
>> 4) Checkstyle Plug-in
>> 5) PMD Plug-in
>> 6) FindBugs
>> 7) DRY
>> 
>> My issue is no results are showing up when I do a build.  I have enabled the 
>> project to get these results.  What gives?
>> 
>> thanks,
>> Rob
> 

Re: force a a job run on every node

[Richard Lavoie]

Matrix build should let you run a job multiple times and iirc there is aplugin 
to add a node label axis (might be node label plugin)



On 2012-10-03, at 17:26, phil swenson  wrote:

> well, it's not running on every node.  I kick off a job and it only
> goes to one node.
> 
> so still stuck….
> 
> On Wed, Oct 3, 2012 at 3:21 PM, phil swenson  wrote:
>> trying a multi-configuration build now.  think this will give me what i want
>> 
>> On Wed, Oct 3, 2012 at 2:54 PM, phil swenson  wrote:
>>> I'm using gradle and periodically I need to run a specific task on
>>> every node to clean out the cache.
>>> 
>>> Is there a way I can force a job to run on all nodes?
>>> 
>>> thanks

Re: force a a job run on every node

[phil swenson]

well, it's not running on every node.  I kick off a job and it only
goes to one node.

so still stuck….

On Wed, Oct 3, 2012 at 3:21 PM, phil swenson  wrote:
> trying a multi-configuration build now.  think this will give me what i want
>
> On Wed, Oct 3, 2012 at 2:54 PM, phil swenson  wrote:
>> I'm using gradle and periodically I need to run a specific task on
>> every node to clean out the cache.
>>
>> Is there a way I can force a job to run on all nodes?
>>
>> thanks

Re: force a a job run on every node

[Slide]

You may want the node-label plugin.

On Wed, Oct 3, 2012 at 2:21 PM, phil swenson  wrote:

> trying a multi-configuration build now.  think this will give me what i
> want
>
> On Wed, Oct 3, 2012 at 2:54 PM, phil swenson 
> wrote:
> > I'm using gradle and periodically I need to run a specific task on
> > every node to clean out the cache.
> >
> > Is there a way I can force a job to run on all nodes?
> >
> > thanks
>



-- 
Website: http://earl-of-code.com

Re: force a a job run on every node

[phil swenson]

trying a multi-configuration build now.  think this will give me what i want

On Wed, Oct 3, 2012 at 2:54 PM, phil swenson  wrote:
> I'm using gradle and periodically I need to run a specific task on
> every node to clean out the cache.
>
> Is there a way I can force a job to run on all nodes?
>
> thanks

force a a job run on every node

[phil swenson]

I'm using gradle and periodically I need to run a specific task on
every node to clean out the cache.

Is there a way I can force a job to run on all nodes?

thanks

Re: Jenkins using massive amount of ram

[Ben Erridge]

Excellent I will look for that!

On Wednesday, October 3, 2012 3:10:05 PM UTC-4, Baptiste MATHUS wrote:
>
> By the way, you don't want to keep that behaviour in mind too long (I 
> mean, loading everything in memory). 
>
> Thanks to Kohsuke, Jenkins is actually now gonna lazy-load build results: 
> see 
> https://groups.google.com/forum/#!msg/jenkinsci-dev/ri5E9LW2kDo/G3NMc65rWpcJ
> .
>
> It's already in the trunk, so it should be out in a release version in 
> some weeks.
>
> Cheers
>
> 2012/10/3 Ben Erridge >
>
>> Rob Thanks discarding old builds seems to have done it. 
>>
>>
>> On Wednesday, October 3, 2012 12:51:23 PM UTC-4, Mandeville, Rob wrote:
>>
>>>  How many runs of these builds do you have hanging around?  I had this 
>>> problem before, and it appeared that the results of every build (except for 
>>> the log files and the artifacts) are held in memory.  In my case, I stored 
>>> the environment of every build I ran and our environments get really big 
>>> (as in, classpaths get truncated for exceeding Linux’s max size for 
>>> environment variable values).  Trimming down to (say) the last week of 
>>> builds helped out a lot.
>>>
>>>  
>>>
>>> Also, you may want to explicitly set your max heap space, but that’s 
>>> more a Java 7 thing than a Jenkins thing. 
>>>
>>>  
>>>
>>> --Rob
>>>
>>>  
>>>
>>> *From:* jenkins...@googlegroups.**com [mailto:jenkins...@**
>>> googlegroups.com] *On Behalf Of *Ben Erridge
>>>
>>> *Sent:* Wednesday, October 03, 2012 11:34 AM
>>> *To:* jenkins...@googlegroups.**com
>>>
>>> *Subject:* Jenkins using massive amount of ram
>>>
>>>  
>>>
>>> I have installed jenkins on a fedora core 17 linux server. When I start 
>>> jenkins it seems to take a ton of ram (12GB+). I start jenkins with the 
>>> command.
>>>  
>>>  
>>>  
>>> I am using open jdk 1.7
>>>  
>>>  
>>>  
>>> start command is
>>>  
>>> /usr/bin/java -Djava.awt.headless=true -DXmx4g -XX:MaxPermSize=128m 
>>>  -DJENKINS_HOME=/var/lib/**jenkins -jar /usr/lib/jenkins/jenkins.war 
>>> --logfile=/var/log/jenkins/**jenkins.log --webroot=/var/cache/jenkins/**war 
>>> --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 
>>> --handlerCountMaxIdle=20
>>>   
>>>  
>>>  
>>> It doesn't seem reasonable to me. Maybe I am doing something wrong? I 
>>> only have 5 builds setup...
>>>  
>>>  
>>>  
>>>
>>> 
>>>
>>>  
>>>   The information in this message is for the intended recipient(s) only 
>>> and may be the proprietary and/or confidential property of Litle & Co., 
>>> LLC, and thus protected from disclosure. If you are not the intended 
>>> recipient(s), or an employee or agent responsible for delivering this 
>>> message to the intended recipient, you are hereby notified that any use, 
>>> dissemination, distribution or copying of this communication is prohibited. 
>>> If you have received this communication in error, please notify Litle & Co. 
>>> immediately by replying to this message and then promptly deleting it and 
>>> your reply permanently from your computer.
>>>  
>>
>
>
> -- 
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>  

Re: Jenkins using massive amount of ram

[Baptiste MATHUS]

By the way, you don't want to keep that behaviour in mind too long (I mean,
loading everything in memory).

Thanks to Kohsuke, Jenkins is actually now gonna lazy-load build results:
see
https://groups.google.com/forum/#!msg/jenkinsci-dev/ri5E9LW2kDo/G3NMc65rWpcJ
.

It's already in the trunk, so it should be out in a release version in some
weeks.

Cheers

2012/10/3 Ben Erridge 

> Rob Thanks discarding old builds seems to have done it.
>
>
> On Wednesday, October 3, 2012 12:51:23 PM UTC-4, Mandeville, Rob wrote:
>
>>  How many runs of these builds do you have hanging around?  I had this
>> problem before, and it appeared that the results of every build (except for
>> the log files and the artifacts) are held in memory.  In my case, I stored
>> the environment of every build I ran and our environments get really big
>> (as in, classpaths get truncated for exceeding Linux’s max size for
>> environment variable values).  Trimming down to (say) the last week of
>> builds helped out a lot.
>>
>>
>>
>> Also, you may want to explicitly set your max heap space, but that’s more
>> a Java 7 thing than a Jenkins thing.
>>
>>
>>
>> --Rob
>>
>>
>>
>> *From:* jenkins...@googlegroups.**com [mailto:jenkins...@**
>> googlegroups.com] *On Behalf Of *Ben Erridge
>>
>> *Sent:* Wednesday, October 03, 2012 11:34 AM
>> *To:* jenkins...@googlegroups.**com
>>
>> *Subject:* Jenkins using massive amount of ram
>>
>>
>>
>> I have installed jenkins on a fedora core 17 linux server. When I start
>> jenkins it seems to take a ton of ram (12GB+). I start jenkins with the
>> command.
>>
>>
>>
>> I am using open jdk 1.7
>>
>>
>>
>> start command is
>>
>> /usr/bin/java -Djava.awt.headless=true -DXmx4g -XX:MaxPermSize=128m
>>  -DJENKINS_HOME=/var/lib/**jenkins -jar /usr/lib/jenkins/jenkins.war
>> --logfile=/var/log/jenkins/**jenkins.log --webroot=/var/cache/jenkins/**war
>> --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100
>> --handlerCountMaxIdle=20
>>
>>
>>
>> It doesn't seem reasonable to me. Maybe I am doing something wrong? I
>> only have 5 builds setup...
>>
>>
>>
>>
>> 
>>
>>
>>   The information in this message is for the intended recipient(s) only
>> and may be the proprietary and/or confidential property of Litle & Co.,
>> LLC, and thus protected from disclosure. If you are not the intended
>> recipient(s), or an employee or agent responsible for delivering this
>> message to the intended recipient, you are hereby notified that any use,
>> dissemination, distribution or copying of this communication is prohibited.
>> If you have received this communication in error, please notify Litle & Co.
>> immediately by replying to this message and then promptly deleting it and
>> your reply permanently from your computer.
>>
>


-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

[Les Mikesell]

On Tue, Oct 2, 2012 at 12:25 PM, zperry  wrote:
> Hi Les,
>
> Finally, the first sentence in "Distributed builds" wiki and the list from
> Kohsuke Kawaguchi started making sense to me.  Thank you once more for
> sharing your experience.
>
> Regarding the list (shown below, and somewhat shortened and edited by me,
> e.g. s#/var/jenkins#/var/lib/jenkins#), could you please comment on
>
> #1 (the bold faced part). Is it really necessary?  For example, the uid/gid
> usage in Fedora differ quite much from that of Ubuntu.  I doubt even NIS
> would make it simpler.  My approach is to review the /etc/passwd and
> /etc/group of all target platforms, pick a pair of uid/gid that are not used
> by all, and assign the pair for Jenkins' use (on both the master and
> slaves).  The packages provided on Jenkins pkg site (e.g
> http://pkg.jenkins-ci.org/redhat/) don't make this task transparent, so the
> above step seems to be necessary.
> #7.  Do you think it's a nearly optimal way to do as part of setting up a
> slave?
> #8. IMHO this is optional. What would you recommend?
>
> 1.  Each computer has an user called jenkins and a group called jenkins. All
> computers use the same UID and GID. (If you have access to NIS, this can be
> done more easily.) This is not a Jenkins requirement, but it makes the slave
> management easier.

The main (maybe only) reason this would matter is if you have common
NFS mounts across the slaves where uid matters.  I have a read-only
export of common libs/tools shared via nfs and samba but it is all
public.   For things I want back from the build, I let jenkins archive
the build artifacts specified for the job.

> 2. On each computer, /var/lib/jenkins directory is set as the home directory 
> of
> user jenkins. Again, this is not a hard requirement, but having the same
> directory layout makes things easier to maintain.

Doesn't really matter, especially if you don't install the jenkins
package and create the user yourself.  You do need to pay attention in
partition layout to have space for jenkin's workspace.

> 3 . All machines run sshd. Windows slaves run cygwin sshd.

Yes, for linux - and probably OK for windows.   My windows slaves are
VM's cloned after installing a bunch of tools including setting up the
jenkins slave as service.  In that scenario you just have to edit the
slave's own name in the jenkins-slave.xml file to match the
newly-added node in jenkins to come up working.

> 4. All machines have ntpdate client installed, and synchronize clock regularly
> with the same NTP server.

Yes, this is pretty much essential unless you are running VMs with a
good sync with their host clock.

> 5. Master's /var/lib/jenkins have all the build tools beneath it.

I don't build anything on the master.   I do export the NFS/samba
share to the slaves from the jenkins server but that's just a matter
of convenience.

> 6. Master's /var/lib/jenkins/.ssh has private/public key and authorized_keys 
> so
> that a master can execute programs on slaves through ssh, by using public
> key authentication.

Yes, but normally the only thing it needs to do directly is copy over
the slave.jar and execute it.  The rest is done internally with java
remoting magic.

> 7. On master, I have a little shell script that uses rsync to synchronize
> master's /var/lib/jenkins to slaves (except /var/lib/jenkins/workspace) I
> use this to replicate tools on all slaves.

I avoid that with the common nfs/samba export.  Copying just gives a
different tradeoff for setup time/disk usage/speed.

> 8. (optional) /var/lib/jenkins/bin/launch-slave is a shell script that Jenkins
> uses to execute jobs remotely.

Jenkins should take care of that by itself with the 'Jenkins SSH slaves plugin'.

> 9. Finally all computers have other standard build tools like svn and cvs
> installed and available in PATH.

Yes, it is painful to try to fight with the rpm/deb package managers
in that respect.  In cases where you want to build with non-standard
versions of libs or tools, you can supply paths in the jenkins job,
but you might end up needing either a chroot environment or a whole
different slave to avoid conflicts.  For example, on windows it is
easy enough to have multiple versions of the boost libs available  and
specify which you want in your job, but I haven't come up with a good
way to do that on linux where there is an expected/packaged version
and changing it conflicts with other packages.

-- 
   Les Mikesell
 lesmikes...@gmail.com

Re: MVN multi-module dependencies build - by a SVN hook

[joantune]

Any ideas/opinions?

On Thursday, September 27, 2012 6:06:21 PM UTC+1, joantune wrote:
>
> Hi community!
>
> First of all, thanks for having developed (those of you that can relate) 
> and given support to this awesome tool that is Jenkins.
>
> So, we have been using jenkins for a bit here at work. We have a big 
> modular project, that used to use ant to compile the several modules that 
> we had (the project is kinda old and by then Maven wasn't popular, i guess 
> that's why it wasn't born using maven to manage the dependencies).
>
> In order to introduce the least level of changes to the developers 
> workflow, I have implemented a hook in the SCM *SVN for now* that detects 
> the modules and creates a jenkin job for each of it based on some groovy 
> magic and a template job.
>
> The behaviour that we want, is the following:
>
>
> We make a commit with changes to project A and B; 
> A is depended by C, and Z depends on C (A<- C<-Z), and B is depended by Y 
> (B<-Y).
>
> So, I have implemented a hook, that does the following:
>
> Checks if A and B are maven modules, and if they are and don't exist, it 
> creates a jenkins job for them.
>
> Second, it launches the jobs for A and B, with a parameter of deploy=true 
> so that it will make a mvn deploy at the end, but only for A and B
>
> Plus, seen that all of the jobs have set the option of *'Build whenever a 
> SNAPSHOT dependency is built'*, and the deploy parameter by default is 
> set to false, B will trigger a build on Y; and A will trigger a build in C, 
> and C will trigger a build in Z, but none of these other builds, will 
> deploy anything to the repository (as intended).
>
> Also, because we have the option of '*Block build when upstream project 
> is building'*. If we make changes to A and Z, the building of A, blocks 
> Z, so that A will build first, and then Z, who will see the changes in A.
>
> This approach however, has two problems which are the reason why I'm 
> writing you this somehow lengthy email (thanks for sticking around until 
> here). They are:
>
> *Problem 1:* If changes are made now to B and Z, and Z is introduced with 
> a dependency on B (B<-Y,Z), because jenkins does not know yet that Z 
> depends now on B, they will be built at the same time, which can cause 
> errors, if Z depends on methods that were introduced in this commit to B.
>
> *Problem 2:* A,C, and Z are committed, A has a method that C and Z now 
> use. A's job fails, C and Z jobs also fail, because of the dependency on A, 
> thus we receive by default 3 emails, and then eventually 3 other emails 
> when A is corrected.
>
> So, Problem 1 is easy to solve with an extra 'round' on the build. I'm 
> thinking on doing something like have a cleanOnly parameter for the jobs, 
> which makes them simply check out the updates from the SCM, parse the new 
> pom, and make a mvn clean. Afterwards, Jenkins should realize that now both 
> Y and Z depend on B, thus B will be built first and block Z's build, when 
> the second normal round of builds (with cleanOnly to false) is done.
>
> Problem 2 however, is harder to solve. We don't want that many emails to 
> be sent. And in case of a fail, we want only one email (the example I gave 
> are 3 emails, which isn't that much added load to your inbox, but seen that 
> we have ~60 modules, and lots of dependencies, this becomes a problem). I'm 
> thinking on using the *'Editable email notification'* along with some 
> groovy magic to solve it. The idea is for instance, have a file written to 
> a temporary location when a fail email is sent. Afterwards, you check if 
> that file is there or not, if it is, you don't send anymore emails... 
> voodoo like that.. not sure exactly what kind of voodoo yet though.
>
> But I'm wondering if this is the way to go. I read about the *Incremental 
> Builds* option and just having the *'Send e-mail for each failed module'* 
> unchecked 
> and put everything under the control of an aggregator pom. (And we have a 
> problem to solve before being able to use the aggregator pom, because we 
> use a custom Mojo that just breaks that simple aggregator pom. But my 
> estimation of the effort that needs to be put into solving that is less 
> than my estimation of solving problem 2 with groovy magic)
>
> Any ideas or opinions if the aggregator pom is the way to go or not? 
> should I just stick with solving problem 2 with groovy magic, any idea 
> which trick of magic should I use?
>
> Thanks in advance.
>  - João Antunes
>

RSS feed for build results doesn't show In-progress builds

[suresh palaniandy]

Hi,

I'm trying to obtain the RSS feed for the Jenkins build results.

It shows the stable, failed and aborted builds. But, it doesn't show the
currently In-Progress build.

I just want to know whether my job has currently got any In-Progress builds.

My build time takes around 3 mins.

Any help is very much appreciated.

Thanks...
Suresh

Re: Approach to build a cluster of Jenkins CI servers hands-off and tie them together?

[Les Mikesell]

On Tue, Oct 2, 2012 at 11:16 AM, zperry  wrote:
>>
>> I don't really see how that practice relates to a web service intended
>> for both remote and local use from multiple users. The remote api does
>> the same things as the regular http interface.It could work, of
>> course, but it's not what people expect from a network service.   If
>> you are going to only run commands locally from the jenkins master you
>> might as well use the cli or groovy instead of the remote api.
>
>
> Lets say the master CI provides Web access (UI and RESTful) only to the
> localhost of the node.  At the first look, this is extremely inconvenient.
> But, in almost all cases, the node runs sshd anyways, thus it can be
> accessed via ssh.
>
> With ssh, you can use port forwarding ssh -L
> local_port:remote_ip:remote_port remote_hostname to forward a desired local
> port, e.g. 8080 to the "localhost" of the master.

I understand the concept and use it for ad-hoc things myself, but
don't normally give all the people who would use jenkins a system
login to the server.

> No more insecure Basic Authentication to worry.  If you have setup PKI, the
> access is transparent and secure.

Our lab is firewalled and remote access already secured, but if I were
concerned about this, I'd probably use https - unless there were
already a central authentication setup that would generate restricted
ssh logins on access.

-- 
   Les Mikesell
lesmikes...@gmail.com

Re: Jenkins using massive amount of ram

[Ben Erridge]

Rob Thanks discarding old builds seems to have done it. 


On Wednesday, October 3, 2012 12:51:23 PM UTC-4, Mandeville, Rob wrote:
>
>  How many runs of these builds do you have hanging around?  I had this 
> problem before, and it appeared that the results of every build (except for 
> the log files and the artifacts) are held in memory.  In my case, I stored 
> the environment of every build I ran and our environments get really big 
> (as in, classpaths get truncated for exceeding Linux’s max size for 
> environment variable values).  Trimming down to (say) the last week of 
> builds helped out a lot.
>
>  
>
> Also, you may want to explicitly set your max heap space, but that’s more 
> a Java 7 thing than a Jenkins thing. 
>
>  
>
> --Rob
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Ben Erridge
> *Sent:* Wednesday, October 03, 2012 11:34 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Jenkins using massive amount of ram
>
>  
>
> I have installed jenkins on a fedora core 17 linux server. When I start 
> jenkins it seems to take a ton of ram (12GB+). I start jenkins with the 
> command.
>  
>  
>  
> I am using open jdk 1.7
>  
>  
>  
> start command is
>  
> /usr/bin/java -Djava.awt.headless=true -DXmx4g -XX:MaxPermSize=128m 
>  -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war 
> --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war 
> --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 
> --handlerCountMaxIdle=20
>   
>  
>  
> It doesn't seem reasonable to me. Maybe I am doing something wrong? I only 
> have 5 builds setup...
>  
>  
>  
>
> 
>
>  
>   The information in this message is for the intended recipient(s) only 
> and may be the proprietary and/or confidential property of Litle & Co., 
> LLC, and thus protected from disclosure. If you are not the intended 
> recipient(s), or an employee or agent responsible for delivering this 
> message to the intended recipient, you are hereby notified that any use, 
> dissemination, distribution or copying of this communication is prohibited. 
> If you have received this communication in error, please notify Litle & Co. 
> immediately by replying to this message and then promptly deleting it and 
> your reply permanently from your computer.
>  

Re: no code analysis showing up with my builds

[Rob Withers]

There are no logs for analysis tools in the console log.

Rob

-Original Message- 
From: Ulli Hafner

Sent: Wednesday, October 03, 2012 12:47 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: no code analysis showing up with my builds

The analysis plug-ins log their results in the console log. Is there 
something printed out?

E.g. [FINDBUGS] Parsing...

Does your build produce the artifacts (e.g. FindBugs results XML file) that 
are read as input by the plugins?


Ulli

Am 03.10.2012 um 17:05 schrieb Rob Withers :


I have the following plugins loaded:
1) JUnit Attachments Plugin
2) Static Analysis Utilities
3) Static Analysis Collector Plug-in
4) Checkstyle Plug-in
5) PMD Plug-in
6) FindBugs
7) DRY

My issue is no results are showing up when I do a build.  I have enabled 
the project to get these results.  What gives?


thanks,
Rob

Perforce plugin and P4TICKET variable

[Richard J]

Our Perforce server is set at security level 3 and the build scripts need 
to use the P4TICKET variable to perform a checkin.
 
It seems that the P4TICKET variable is only available when the plugin tries 
to communicate with Perforce, fails and then does a login.
So, in order to guarantee that the variable is defined for the job, I need 
to start each Jenkins jobs with a pre-SCM script that performs a Perforce 
Logoff.
This is working for me, but it's ugly. 
 
Is there a better way?
 
Richard
 
 

RE: Jenkins using massive amount of ram

[Mandeville, Rob]

How many runs of these builds do you have hanging around?  I had this problem 
before, and it appeared that the results of every build (except for the log 
files and the artifacts) are held in memory.  In my case, I stored the 
environment of every build I ran and our environments get really big (as in, 
classpaths get truncated for exceeding Linux’s max size for environment 
variable values).  Trimming down to (say) the last week of builds helped out a 
lot.

Also, you may want to explicitly set your max heap space, but that’s more a 
Java 7 thing than a Jenkins thing.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ben Erridge
Sent: Wednesday, October 03, 2012 11:34 AM
To: jenkinsci-users@googlegroups.com
Subject: Jenkins using massive amount of ram

I have installed jenkins on a fedora core 17 linux server. When I start jenkins 
it seems to take a ton of ram (12GB+). I start jenkins with the command.

I am using open jdk 1.7

start command is
/usr/bin/java -Djava.awt.headless=true -DXmx4g -XX:MaxPermSize=128m  
-DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war 
--logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war 
--httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 
--handlerCountMaxIdle=20

It doesn't seem reasonable to me. Maybe I am doing something wrong? I only have 
5 builds setup...


[https://lh5.googleusercontent.com/-Ofheh_L4EgY/UGxasgpqtcI/A2Q/V38CC-q1Jvo/s400/jenkinsTop.png]



The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

Re: no code analysis showing up with my builds

[Ulli Hafner]

The analysis plug-ins log their results in the console log. Is there something 
printed out?
E.g. [FINDBUGS] Parsing...

Does your build produce the artifacts (e.g. FindBugs results XML file) that are 
read as input by the plugins?

Ulli
 
Am 03.10.2012 um 17:05 schrieb Rob Withers :

> I have the following plugins loaded:
> 1) JUnit Attachments Plugin
> 2) Static Analysis Utilities
> 3) Static Analysis Collector Plug-in
> 4) Checkstyle Plug-in
> 5) PMD Plug-in
> 6) FindBugs
> 7) DRY
>  
> My issue is no results are showing up when I do a build.  I have enabled the 
> project to get these results.  What gives?
>  
> thanks,
> Rob

maven jdk

[JohnZerbe]

quick question. 
Is there a way to tell Jenkins to invoke maven itself via one jdk version
but have maven build a java project with a different jdk? 

Example: The current version of Maven will not run on jdk 1.4.2, but we have
a project for IBM WebSphere 5.1 that requires jdk 1.4.2. I want Maven to run
on jdk 1.7, but the build to compile and create WARS and EARS via 1.4.2.




--
View this message in context: 
http://jenkins.361315.n4.nabble.com/maven-jdk-tp4642118.html
Sent from the Jenkins users mailing list archive at Nabble.com.

Jenkins using massive amount of ram

[Ben Erridge]

I have installed jenkins on a fedora core 17 linux server. When I start 
jenkins it seems to take a ton of ram (12GB+). I start jenkins with the 
command.

I am using open jdk 1.7

start command is
/usr/bin/java -Djava.awt.headless=true -DXmx4g -XX:MaxPermSize=128m 
 -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war 
--logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war 
--httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 
--handlerCountMaxIdle=20

It doesn't seem reasonable to me. Maybe I am doing something wrong? I only 
have 5 builds setup...

no code analysis showing up with my builds

[Rob Withers]

I have the following plugins loaded:
1) JUnit Attachments Plugin
2) Static Analysis Utilities
3) Static Analysis Collector Plug-in
4) Checkstyle Plug-in
5) PMD Plug-in
6) FindBugs
7) DRY

My issue is no results are showing up when I do a build.  I have enabled the 
project to get these results.  What gives?

thanks,
Rob 

getting maven2 to use the default pom

[Rob Withers]

I am using 1.484  I set my workspace to my eclipse workspace.  There is no 
pom file there.  I have no global MAVEN_OPTS and the local Maven repository 
is local to the workspace.

When I add a project, I cannot simply use pom.xml as my Root POM – I have to 
specify the subdirectory it is in “murmur-events/pom.xml”.  It seems that 
each project does not exist in its own subdirectory specified by the project 
name?

thanks,
Rob

Re: Build Flow plugin saves empty DSL

[nicolas de loof]

I will try to reproduce your issue, but being at JavaOne can't do it before
next week

2012/10/3 dhyix 

> Editing a Build Flow always saves an empty DSL. I configure it, enter in:
> build("job"). Then after saving, if I reconfigure it or look at the config
> file in the filesystem the dsl is always empty. Is there something I'm
> missing?
>
> I have a new install of Jenkins version 1.484 and I've added the Build
> Flow plugin version 0.5 to it. That's it.
>
> Thanks!
>

Build Flow plugin saves empty DSL

[dhyix]

Editing a Build Flow always saves an empty DSL. I configure it, enter in: 
build("job"). Then after saving, if I reconfigure it or look at the config 
file in the filesystem the dsl is always empty. Is there something I'm 
missing?

I have a new install of Jenkins version 1.484 and I've added the Build Flow 
plugin version 0.5 to it. That's it. 

Thanks!

setting up git SCM...

[Rob Withers]

I stopped using git and went back to what was working before, which was 
setting up a maven2 project.  Now I develop in eclipse and I can launch a 
build manually, whenever I want to build the jar and run the tests.  To get 
it working, I set the global workspace to my eclipse workspace and then 
specify the project pom, like: "murmur-events/pom.xml".


So, sticking to Git, how should I setup a project to use the git SCM?  Which 
plugin should I use and how should I configure it?
1) I would like to run a build, automatically, whenever the local repository 
gets a commit.

2) Just to know, I would also like to run a build whenever I push to github.

thanks!
Rob

-Original Message- 
From: Dirk Weigenand

Sent: Wednesday, October 03, 2012 7:48 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: multiple problems setting up Jenkins and Git and Maven, as well 
as code analysis tools - start with git...


Hi,

i guess this problem is related to files still opened by Jenkins or
another process.

I experience this problem only on Windows when cleaning the workspace.

You should use the equivalent of 'lsof' to find out what file is still
in use by which process.

regards

Dirk

On 03.10.2012 03:51, Rob Withers wrote:

Here is the error I am getting:  Thanks!


Started
by user Robert
Withers 
Building in workspace c:\rob\comp\workspace
Checkout:workspace / c:\rob\comp\workspace -
hudson.remoting.LocalChannel@4d4834
Using strategy: Default
Cloning the remote Git repository
Cloning repository http://github.com/reefedjib/murmur-events/
git --version
git version 1.7.11.msysgit.1
ERROR: Failed to clean the workspace
java.io.IOException 
: 
Unable to

delete c:\rob\comp\workspace\.metadata\.lock
at hudson.Util.deleteFile(Util.java:243) 

at hudson.Util.deleteRecursive(Util.java:293) 

at hudson.Util.deleteContentsRecursive(Util.java:204) 

at hudson.Util.deleteRecursive(Util.java:284) 

at hudson.Util.deleteContentsRecursive(Util.java:204) 

at hudson.Util.deleteRecursive(Util.java:284) 

at hudson.FilePath$11.invoke(FilePath.java:982) 

at hudson.FilePath$11.invoke(FilePath.java:980) 

at hudson.FilePath.act(FilePath.java:851) 

at hudson.FilePath.act(FilePath.java:824) 

at hudson.FilePath.deleteRecursive(FilePath.java:980) 

at hudson.plugins.git.GitAPI.clone(GitAPI.java:239) 

at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1040) 

at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:982) 

at hudson.FilePath.act(FilePath.java:851) 

at hudson.FilePath.act(FilePath.java:824) 

at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:982) 

at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1138) 

at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) 

at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 

at 
hudson.model.Abst

Re: Re : Re: Login Failed with svn+ssh

[Oscar Martins]

Can you provide the code you have added in the file bashrc?

Segunda-feira, 6 de Junho de 2011 10:06:44 UTC+1, sebboon escreveu:
>
> Thank you teilo, you show the right way !
>
> I gave a password to the jenkins user with a ssh private key.
> I added ssh-agent with ssh-add to the bashrc file to preload this key and 
> allow authentication to svn throught SSH during maven release process
>
> And now the my release commit are done by jenkins user which is not so bad 
> :D
>

Issues installing plugins on XP

[Iain Walsh]

HI,
   I've successfully got Jenkins running on my Windows 7 machine. However 
I'm having an issue with Hudson not finding a Kernel32 class on the XP 
machine.
I'm remotely logged on to the XP machine with Administrator permissions. 
However it looks like it could be a permission problem, could I get 
confirmation before
bringing this to our system administrator?

Whenever I try to install a plugin I get this exception:
Failure - 

java.lang.NoClassDefFoundError: Could not initialize class 
hudson.util.jna.Kernel32
at 
hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:62)
at hudson.Util.isSymlink(Util.java:322)
at hudson.Util.deleteRecursive(Util.java:283)
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:403)
at 
hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:117)
at hudson.PluginManager.dynamicLoad(PluginManager.java:388)
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1223)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1037)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)


Regards,

Iain

Re: multiple problems setting up Jenkins and Git and Maven, as well as code analysis tools - start with git...

[Dirk Weigenand]

Hi,

i guess this problem is related to files still opened by Jenkins or
another process.

I experience this problem only on Windows when cleaning the workspace.

You should use the equivalent of 'lsof' to find out what file is still
in use by which process.

regards

Dirk

On 03.10.2012 03:51, Rob Withers wrote:
> Here is the error I am getting:  Thanks!
>  
> 
> Started 
> by user Robert 
> Withers 
> Building in workspace c:\rob\comp\workspace
> Checkout:workspace / c:\rob\comp\workspace - 
> hudson.remoting.LocalChannel@4d4834
> Using strategy: Default
> Cloning the remote Git repository
> Cloning repository http://github.com/reefedjib/murmur-events/
> git --version
> git version 1.7.11.msysgit.1
> ERROR: Failed to clean the workspace
> java.io.IOException 
> : Unable 
> to 
> delete c:\rob\comp\workspace\.metadata\.lock
>   at hudson.Util.deleteFile(Util.java:243) 
> 
>   at hudson.Util.deleteRecursive(Util.java:293) 
> 
>   at hudson.Util.deleteContentsRecursive(Util.java:204) 
> 
>   at hudson.Util.deleteRecursive(Util.java:284) 
> 
>   at hudson.Util.deleteContentsRecursive(Util.java:204) 
> 
>   at hudson.Util.deleteRecursive(Util.java:284) 
> 
>   at hudson.FilePath$11.invoke(FilePath.java:982) 
> 
>   at hudson.FilePath$11.invoke(FilePath.java:980) 
> 
>   at hudson.FilePath.act(FilePath.java:851) 
> 
>   at hudson.FilePath.act(FilePath.java:824) 
> 
>   at hudson.FilePath.deleteRecursive(FilePath.java:980) 
> 
>   at hudson.plugins.git.GitAPI.clone(GitAPI.java:239) 
> 
>   at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1040) 
> 
>   at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:982) 
> 
>   at hudson.FilePath.act(FilePath.java:851) 
> 
>   at hudson.FilePath.act(FilePath.java:824) 
> 
>   at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:982) 
> 
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1138) 
> 
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
>  
> 
>   at 
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) 
> 
>   at hudson.model.Run.execute(Run.java:1502) 
> 
>   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:88) 
> 

Maven Post Action Deploy?

[David Doughty]

I've got some users who are trying as a post build action to deploy artefacts 
to Nexus

Using the maven goal deploy the build picks up the settings.xml from the maven 
install on the build box.

Using the plugin, it appears to be trying to access the user settings.xml 
(jenkins user in .m2/repository/settings.xml, which doesn't exist).

I've not used the post build action deploy previously, can anyone tell me if 
this is working as expected, or did I miss a config step to get it to pickup 
the installation settings.xml?

Currently we're running 1.482 Jenkins on this linux box

Thanks

dD