RE: Jenkins svn ssh / host key verification problems

[Nord, James]

Yes – the slave needs the servers host key in the known_hosts (or you can 
configure ssh to not use strict host checking[1] – depending on your level of 
security paranioa )

[1] 
http://linuxcommando.blogspot.co.uk/2008/10/how-to-disable-ssh-host-key-checking.html

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bjørn Water
Sent: 07 January 2013 09:43
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins svn ssh / host key verification problems

So i have checked and the slave where i run my build process on does not 
contain a host key.
So i suspect this slave also needs one?

On Friday, January 4, 2013 3:19:31 PM UTC+1, Bjørn Water wrote:
So i am trying to use the M2-release plugin to release my project and push it 
to my nexus.
I can do svn checkout and i can even tag my build and see it in my repo
but when i try to do mvn release:prepare after a succesfull build i get an error


[ERROR] BUILD FAILURE

[INFO] 

[INFO] Unable to commit files

Provider message:

The svn command failed.

Command output:

Host key verification failed.

svn: Commit failed (details follow):

svn: To better debug SSH connection problems, remove the -q option from 'ssh' 
in the [tunnels] section of your Subversion configuration file.

svn: Network connection closed unexpectedly



[INFO] 

[INFO] Trace

org.apache.maven.BuildFailureException: Unable to commit files

Provider message:

The svn command failed.

Command output:

Host key verification failed.

svn: Commit failed (details follow):

svn: To better debug SSH connection problems, remove the -q option from 'ssh' 
in the [tunnels] section of your Subversion configuration file.

svn: Network connection closed unexpectedly



 at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)

 at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)

 at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)

 at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)

 at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)

 at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)

 at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)

 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)

 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)

 at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

 at java.lang.reflect.Method.invoke(Method.java:597)

 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

 at hudson.maven.agent.Main.launch(Main.java:185)

 at hudson.maven.MavenBuilder.call(MavenBuilder.java:153)

 at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)

 at hudson.maven.Maven2Builder.call(Maven2Builder.java:55)

 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:303)

 at java.util.concurrent.FutureTask.run(FutureTask.java:138)

 at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

 at java.lang.Thread.run(Thread.java:662)

Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files

Provider message:

The svn command failed.

Command output:

Host key verification failed.

svn: Commit failed (details follow):

svn: To better debug SSH connection problems, remove the -q option from 'ssh' 
in the [tunnels] section of your Subversion configuration file.

svn: Network connection closed unexpectedly



 at 
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:287)

 at 
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:237)

 at 
org.

RE: Master + slave + job JVM memory tuning...

[Nord, James]

Have enough RAM on the slave that you can run your jobs plus Jenkins + some for 
overhead.
(e.g. 1GB of Jenkins slave, + #executors * ( 2GB for Maven +2GB for unit tests 
in forked VM) + OS overhead)
 Although this amount is mostly an overkill setting it too close to the 
threshold will slow your jobs down due to paging at best, or mean you get 
intermittent failures due to OOM at worst – (memory is generally cheaper that 
human time taken to investigate issues!)  (our maven jobs can be very memory 
hungry so your figures will vary)  (Note I recommend a single executor per 
slave)

The master depends more on how many jobs / reports per jobs / job history you 
have etc – we use 10GB (but not tomcat).

If you’re in the UK and there is any spaces left I will cover some things like 
this next week at the Jenkins User Event.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jeff
Sent: 04 January 2013 21:56
To: jenkinsci-users@googlegroups.com
Subject: Master + slave + job JVM memory tuning...

I'm trying to optimize how much memory I allocate to the master application 
(aka - tomcat), slave processes, maven tasks, etc. and going crazy.

I've been unsuccessful in finding a guideline to determine how much memory I 
ought to allocate or if I should just let the defaults work.

All machines are single processor, dual core with 4 GB ram.

I've typically set tomcat to use 2048MB + 512MB permgen space and set my maven 
process to use 384MB max.  Is this reasonable?

My slaves are set to run 4 executors.  Jobs use either svn or git to check out 
code and Maven to build with a SONAR post-build analysis.  We also do Maven 
releases at times.

How much does the core slave process need?  Is there a "rule-of-thumb" based on 
the number of executors?

Any perspective/considerations/resources/links/pointers are much appreciated.

--
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox !!




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: TFS/Maven/Linux Help needed!

[Nord, James]

You may want to change the build users password :-o

Maven will want the “tf” command to be on the path which it appears it’s not[1] 
(Jenkins uses the absolute path that its configured with[2]

I would double check that environment that the user Jenkins is running as has 
/usr/bin/tfs on the path

/James

[1] 16:06:15 [INFO] err - /bin/sh: tf: command not found
[2] 16:02:33 [workspace] $ /usr/bin/tfs/tf workspaces -format:brief 
-server:http://1.2.3.250:8080/tfs/2x 

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Steve Brice
Sent: 03 January 2013 15:55
To: jenkinsci-users@googlegroups.com
Subject: TFS/Maven/Linux Help needed!

We are currently migrating from Windows to Linux build servers. I have 
everything up and running in Linux fine. However, when performing a maven 
release its failing right at the end. I have verified all the permissions, 
environment paths...etc.  I am attaching the console output if someone could 
kindly point me in the right direction.

 Jenkins appears to be connecting to TFS fine but I think there is something 
going on with the maven plugin.




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: m2release 0.10.0 (Not yet released) - duedate

[Nord, James]

Hi Marcus,

There are a couple of outstanding pull requests that I need to pull in before 
the release - one of which is for a defect with the release builds to keep.

-1 as a default doesn't make sense (it is really 0 as you are marking zero 
builds to keep).

If there are any features you would like that are missing the best way is to 
create a pull request and a JIRA issue.

Regards,

/James

From: jenkinsci-...@googlegroups.com [mailto:jenkinsci-...@googlegroups.com] On 
Behalf Of Marcus Vinicius
Sent: 03 January 2013 11:08
To: jenkinsci-users@googlegroups.com; jenkinsci-...@googlegroups.com
Subject: m2release 0.10.0 (Not yet released) - duedate

Hello,

 I'm interessted at release 0.10.0 of  m2reelase plugin. I built from source 
code and tried it. I have the suggestions below about the Fix  "Add ability to 
specify number of release builds to keep":
- As can you see at image there is a error when you click on help image: 
"Failed to load help image: Not found"
- Default number of successful release builds to keep to "-1".

What is the due date to perform 0.10.0 release?

I'm a java developer how could i help this plugin project?


[cid:image001.png@01CDE9AB.ACA227C0]

--

Marcus Vinicius A. Silva
P  ANTES DE IMPRIMIR pense em sua responsabilidade e compromisso com o MEIO 
AMBIENTE.




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**
<>

dynamic popup memus

[Nord, James]

Arrghhh!

Well now that's got your attention/back up[1] I would like to provide some 
feedback as to why I'm saying "Arrghhh" and the uses cases that I find are now 
killed because of it.

I constantly find myself cutting and pasting bits of info from Jenkins to place 
elsewhere and half way through selecting the piece of information I need the 
popup menu appears - and this causes the selection to be deselected - so when 
the mouse is still moving to select some more bits you end up with the first 
bit selected no longer being in the selection :-o
(this gets even worse when using a track pad rather than a mouse as you need to 
re-position your finger - so selection takes even longer than it would with a 
mouse)

The other is I know where the menu is relative to a co-ordinate so I may move 
my mouse without speed to the link I want.
When I do this without looking - (well you touch type so why not touch mouse!) 
you sometimes get a popup whilst the mouse is moving and select an item from 
the popup not the link that is now hidden by the popup.

They do not disappear with the same stimulus method that enabled them to appear 
(that is you can not dismiss them by moving the mouse) (which is what the 
weather ones allow you to do - they disappear as soon as you mouse out of the 
weather icon - or popup).  Even the weather popup can get obtrusive at times 
(think a folder with many jobs under it).

I have also found (but can't recall on which tooltip) that I wanted to get a 
"tooltip" (I think it was estimated time left of a build job) and the tooltip 
was then covered up by the popup menu - rendering the tooltip unreadable.

Note things may have moved on as I am on LTS. Chrome is the brower of choice...

/James

[1] delete as applicable




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

remove "copy job" option

[Nord, James]

Hi all,

Is it possible to remove the "Copy Existing"... option when creating a new job 
(either by writing a plugin, or config - ideally I do not  want to edit the 
jelly files for each Jenkins release).

If so any pointers?

Regards,

/James




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Nullpointer in log rotator

[Nord, James]

Thorough testing only occurs in the LTS branch.

If you don’t want to do some testing of your own before rolling out a Jenkins 
upgrade I would recommend that you switch from the bleeding edge to LTS.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Pawel
Sent: 10 October 2012 13:03
To: jenkinsci-users@googlegroups.com
Subject: Re: Nullpointer in log rotator

Same issue for me. I have first updated to 484, which introduced nasty bug with 
Maven installations being removed, so I installed 485, which makes plenty of my 
builds fail because of NPE. Is anyone testing the releases in some real 
environment before giving them to users?




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Can I use the same job names on many slaves (i.e. in an OO manner)?

[Nord, James]

It sounds like you want a multi-configuration project with the node set as one 
of your axis.

/James



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of zperry
Sent: 05 October 2012 22:22
To: jenkinsci-users@googlegroups.com
Subject: Can I use the same job names on many slaves (i.e. in an OO manner)?

We are POCing a Jenkins build farm that consists of 1 master, 2 slaves.

We use Jenkins mainly to monitor our C++ builds.  Our software targets many 
different Linux and FreeBSD distributions and releases, so we can see that 
Jenkins can help boost our efficiency significantly.

But while testing it out, it seems to me that even for the same build job, I 
have name jobs differently.  I wonder it's because I have misunderstood 
Jenkins' usage or it's a current limitation that I have to live with?

To make it concrete, lets say we have

  *   m0, s0, and s1, where m0 is the master, s0 and s1 are the two slaves.
  *   j0, j1, ... jn as the respective "original" name of our C++ build/test 
jobs (i.e. when these jobs were ran just on the POC master)
Now, to use s0 and s1, it seems that we must rename our jobs to the following:

  *   On m0: m0-j0, m0-j1, ... m0-jn
  *   On s0: s0-j0, s0-j1, ... s0-jn
  *   On s1: s1-j0, s1-j1, ... s1-jn
This seems to be quite cumbersome an requirement.  Can we do it in a more 
Object-Oriented manner - use an attribute somewhere to denote a j0 should be 
run on s0, and another j0 should be run on s1 etc, likewise for other jobs?

Thanks in advance for any hints/tips.

Regards,

-- Zack





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Taking a lot of disk space

[Nord, James]

>From memory it does when the next build of that job runs.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Miguel Almeida
Sent: 21 September 2012 17:05
To: jenkinsci-users@googlegroups.com
Subject: Re: Taking a lot of disk space

Wonderful news James! Would that recursively delete artifacts from old builds 
if you set it on a job with existing (a few hundred) builds?
On Fri, Sep 21, 2012 at 4:28 PM, Nord, James 
mailto:jn...@nds.com>> wrote:
Nah - no need to be that drastic - maven2 project type to the rescue!

Just set a different retention for artifacts vs builds.




Discard Old Builds





Days to keep builds



if not empty, build records are only kept up to this number of days



Max # of builds to keep



if not empty, only up to this number of build records are kept




Days to keep artifacts



if not empty, artifacts from builds older than this number of days will be 
deleted, but the logs, history, reports, etc for the build will be kept



Max # of builds to keep with artifacts



if not empty, only up to this number of builds have their artifacts retained



From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Stephen Connolly
Sent: 21 September 2012 15:56
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: Taking a lot of disk space

Aha! Maven 2 project type strikes again!

It auto-archives every build artifact... I think you can disable this 
setting... but you risk reduced functionality in some use cases
On 21 September 2012 15:49, Miguel Almeida 
mailto:migueldealme...@gmail.com>> wrote:
Hi Marek,
On Fri, Sep 21, 2012 at 3:36 PM, Marek Gimza 
mailto:marekgi...@gmail.com>> wrote:
Miguel,

Is the workspace directory under the 
/usr/share/tomcat6/.jenkins/jobs/ directories?
It is. But the workspace directly below  is only 100 MB large, so 
it's hardly the problem.
Running some "du" commands, I see most space is being occupied by the builds 
directories under each module: 
/usr/share/tomcat6/.jenkins/jobs//moduleA/builds. One of them 
has...15GB of data!

This could be the reason for the disk usage.
The workspace is the directory to which jenkins will sync and perform your 
build-steps.


You could take advantage of the "customWorkspace" field in the job 
configuration or the "Remote FS root" field in the Node's configuration to 
specify a different directory to store the workspace.

We use these fields to specify our workspace for each job to be different than 
the job's meta-data, such as log-files, which is still under the 
${JENKINS_HOME}/jobs/ directories.


Kind Regards,
Marek

On Fri, Sep 21, 2012 at 10:26 AM, Miguel Almeida 
mailto:migueldealme...@gmail.com>> wrote:
Dear all,

I have been using Jenkins for some months now and I am interested in the issue 
of disk usage.

While trying to understand why the 50GB on the server were becoming short, I 
decided to investigate the size of each job directory under 
/usr/share/tomcat6/.jenkins/jobs/. To my surprise, this was larger than 
expected. One maven job with 5 modules and about 700 runs is currently taking 
16 GB of disk space!

I realize  I can "discard old builds" of a job, but then I'll lose interesting 
metrics like code coverage trends or test result trends. My questions are:

1) Is this a normal usage - 23-ish MB per job run?
2) If so, are there other options that allow me to keep a relatively 
interesting history but without taking so much disk space?
3) Is this a usual concern, or do you just splash new TB disks whenever you run 
out of space? I mean, I've been using Jenkins for 10 months and have around 20 
projects now, surely this is not intensive usage.


I appreciate the feedback,

Miguel Almeida







**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com<mailto:postmas...@nds.com> and delete it from your system as 
well as any copies. The content of e-mails as well as traffic data may be 
monitored by NDS for employment and security purposes. To protect the 
environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Taking a lot of disk space

[Nord, James]

Nah - no need to be that drastic - maven2 project type to the rescue!

Just set a different retention for artifacts vs builds.




Discard Old Builds





Days to keep builds



if not empty, build records are only kept up to this number of days



Max # of builds to keep



if not empty, only up to this number of build records are kept




Days to keep artifacts



if not empty, artifacts from builds older than this number of days will be 
deleted, but the logs, history, reports, etc for the build will be kept



Max # of builds to keep with artifacts



if not empty, only up to this number of builds have their artifacts retained



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 21 September 2012 15:56
To: jenkinsci-users@googlegroups.com
Subject: Re: Taking a lot of disk space

Aha! Maven 2 project type strikes again!

It auto-archives every build artifact... I think you can disable this 
setting... but you risk reduced functionality in some use cases
On 21 September 2012 15:49, Miguel Almeida 
mailto:migueldealme...@gmail.com>> wrote:
Hi Marek,
On Fri, Sep 21, 2012 at 3:36 PM, Marek Gimza 
mailto:marekgi...@gmail.com>> wrote:
Miguel,

Is the workspace directory under the 
/usr/share/tomcat6/.jenkins/jobs/ directories?
It is. But the workspace directly below  is only 100 MB large, so 
it's hardly the problem.
Running some "du" commands, I see most space is being occupied by the builds 
directories under each module: 
/usr/share/tomcat6/.jenkins/jobs//moduleA/builds. One of them 
has...15GB of data!

This could be the reason for the disk usage.
The workspace is the directory to which jenkins will sync and perform your 
build-steps.


You could take advantage of the "customWorkspace" field in the job 
configuration or the "Remote FS root" field in the Node's configuration to 
specify a different directory to store the workspace.

We use these fields to specify our workspace for each job to be different than 
the job's meta-data, such as log-files, which is still under the 
${JENKINS_HOME}/jobs/ directories.


Kind Regards,
Marek


On Fri, Sep 21, 2012 at 10:26 AM, Miguel Almeida 
mailto:migueldealme...@gmail.com>> wrote:
Dear all,

I have been using Jenkins for some months now and I am interested in the issue 
of disk usage.

While trying to understand why the 50GB on the server were becoming short, I 
decided to investigate the size of each job directory under 
/usr/share/tomcat6/.jenkins/jobs/. To my surprise, this was larger than 
expected. One maven job with 5 modules and about 700 runs is currently taking 
16 GB of disk space!

I realize  I can "discard old builds" of a job, but then I'll lose interesting 
metrics like code coverage trends or test result trends. My questions are:

1) Is this a normal usage - 23-ish MB per job run?
2) If so, are there other options that allow me to keep a relatively 
interesting history but without taking so much disk space?
3) Is this a usual concern, or do you just splash new TB disks whenever you run 
out of space? I mean, I've been using Jenkins for 10 months and have around 20 
projects now, surely this is not intensive usage.


I appreciate the feedback,

Miguel Almeida







**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Problem with MAVEN_HOME in a build

[Nord, James]

Hi Erik,

Does the slave machine have MAVEN_HOME set in is environment (either in the OS 
or on the Jenkins slave properties)?

Any chance of a log output of a release build with debug logging ( add the "-X" 
flag on the release goals ), and a copy of the maven-release-plugin 
configuration you are using.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of erik petzold
Sent: 19 September 2012 15:02
To: jenkinsci-users@googlegroups.com
Subject: Re: Problem with MAVEN_HOME in a build


Hi,

we have the maven version set in jenkins main config (only maven 2.2.1, nothing 
else).
We only use maven2 jobs in jenkins and it is the m2-release-plugin (I didnt 
even know theres another release plugin).

When we started with jenkins, the maven version on this machine was older, so 
someone installed 2.2.1 (we needed this for a maven plugin, cant remember which 
one). All jobs in jenkins use this version. But the older one is still there, 
so when calling maven in a job we always provide the -gs flag with the correct 
global settings.xml. I did this also in the configuration for the 
release-plugin in the configuration of the job. Maybe it has to do something 
with this?

Erik
Am 19.09.2012 14:40 schrieb "mpapo - Michaël Pailloncy" 
mailto:mpapo@gmail.com>>:
Hi James,

In my case, the problem occurs even if we set a specific version of Maven in 
build and release configuration. We have 2 Maven versions configured in Jenkins 
configuration (Maven 2.2.1 and 3.0.3).
I guess my configuration is very specific : the problem occurs with a Maven 
type jobs with Release Plugin and not the normal M2Release Plugin for this type 
of jobs.

@Erik : do you have the same configuration ?

We have not detected the problem with Freestyle job type and Release Plugin.

Michaël

Le mercredi 19 septembre 2012 14:43:21 UTC+2, teilo a écrit :
Hi Erik,

I personally wouldn't recommend putting MAVEN_HOME in a profile, rather it is 
better to let Jenkins managed this by specifying the version of maven to use.

You can configure this in the Jenkins main config (and then override per slave 
if needs be.)

See 
http://my.safaribooksonline.com/book/software-engineering-and-development/ide/9781449311155/configuring-your-jenkins-server/sect-configuration-build-tools
 for more details.

BTW - is this with the "m2release plugin" on a maven type job or with the 
"release plugin" on a freestyle job?

/James

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com]
 On Behalf Of Erik
Sent: 17 September 2012 08:44
To: jenkins...@googlegroups.com
Subject: Re: Problem with MAVEN_HOME in a build

I get the same exception in Jenkins v. 1.477 and maven 2.2.1

Everything works fine, except for the release. There I get this exception.

[INFO] Exception in thread "main" java.lang.NoClassDefFoundError: 
org/codehaus/classworlds/Launcher

[INFO] Caused by: java.lang.ClassNotFoundException: 
org.codehaus.classworlds.Launcher

Thanks,
Erik


Am Donnerstag, 6. September 2012 19:14:13 UTC+2 schrieb mpapo - Michaël 
Pailloncy:
Hi,

We faced in a problem with Maven during a release build. The job is configured 
with the Release Plugin.
MAVEN_HOME variable is correctly set during the first build (and any 'normals' 
builds), but when we launch a release and the build arrive to the command 'mvn 
.. release:clean release:prepare release:perform' to launch the Maven3 release, 
it seems that the MAVEN_HOME variable is not set correctly and the build crashs 
with this error :

class not found:  org.codehaus.classworlds.Launcher  -  
org.codehaus.classworlds.Launcher

We have also Maven2.2.1 and Maven3.0.3 installed on the master (AIX) which 
build this job.
In .profile file, M2_HOME is by default set to Maven2.2.1.

The problem is appeared since we have updated Jenkins with version 1.478.
The same job worked correctly before the update (last release has been built 
just before our update of Jenkins and the mvn command worked correctly).

Is this a bug ? Does I create a ticket in Jira ?

Thanks in advance from any help !
Michaël




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postm...@nds.com and delete it from your system as 
well as any copies. The content of e-mails as well as traffic data may be 
monitored by NDS for employment and security purposes. To protect the 
environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
*

RE: Problem with MAVEN_HOME in a build

[Nord, James]

Hi Michaël

The maven job type plugin at one point never inserted MAVEN_HOME and didn’t add 
maven to the path and so the m2release plugin did this to work around this 
issue.  It sounds like that functionality may have once again disappeared from 
the Maven jobtype plugin

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of mpapo - Michaël Pailloncy
Sent: 19 September 2012 14:40
To: jenkinsci-users@googlegroups.com
Subject: Re: Problem with MAVEN_HOME in a build

Hi James,

In my case, the problem occurs even if we set a specific version of Maven in 
build and release configuration. We have 2 Maven versions configured in Jenkins 
configuration (Maven 2.2.1 and 3.0.3).
I guess my configuration is very specific : the problem occurs with a Maven 
type jobs with Release Plugin and not the normal M2Release Plugin for this type 
of jobs.

@Erik : do you have the same configuration ?

We have not detected the problem with Freestyle job type and Release Plugin.

Michaël

Le mercredi 19 septembre 2012 14:43:21 UTC+2, teilo a écrit :
Hi Erik,

I personally wouldn’t recommend putting MAVEN_HOME in a profile, rather it is 
better to let Jenkins managed this by specifying the version of maven to use.

You can configure this in the Jenkins main config (and then override per slave 
if needs be.)

See 
http://my.safaribooksonline.com/book/software-engineering-and-development/ide/9781449311155/configuring-your-jenkins-server/sect-configuration-build-tools
 for more details.

BTW – is this with the “m2release plugin” on a maven type job or with the 
“release plugin” on a freestyle job?

/James

From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On 
Behalf Of Erik
Sent: 17 September 2012 08:44
To: jenkins...@googlegroups.com
Subject: Re: Problem with MAVEN_HOME in a build

I get the same exception in Jenkins v. 1.477 and maven 2.2.1

Everything works fine, except for the release. There I get this exception.

[INFO] Exception in thread "main" java.lang.NoClassDefFoundError: 
org/codehaus/classworlds/Launcher

[INFO] Caused by: java.lang.ClassNotFoundException: 
org.codehaus.classworlds.Launcher

Thanks,
Erik


Am Donnerstag, 6. September 2012 19:14:13 UTC+2 schrieb mpapo - Michaël 
Pailloncy:
Hi,

We faced in a problem with Maven during a release build. The job is configured 
with the Release Plugin.
MAVEN_HOME variable is correctly set during the first build (and any 'normals' 
builds), but when we launch a release and the build arrive to the command 'mvn 
.. release:clean release:prepare release:perform' to launch the Maven3 release, 
it seems that the MAVEN_HOME variable is not set correctly and the build crashs 
with this error :

class not found:  org.codehaus.classworlds.Launcher  -  
org.codehaus.classworlds.Launcher

We have also Maven2.2.1 and Maven3.0.3 installed on the master (AIX) which 
build this job.
In .profile file, M2_HOME is by default set to Maven2.2.1.

The problem is appeared since we have updated Jenkins with version 1.478.
The same job worked correctly before the update (last release has been built 
just before our update of Jenkins and the mvn command worked correctly).

Is this a bug ? Does I create a ticket in Jira ?

Thanks in advance from any help !
Michaël




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the postm...@nds.com 
and delete it from your system as well as any copies. The content of e-mails as 
well as traffic data may be monitored by NDS for employment and security 
purposes. To protect the environment please do not print this e-mail unless 
necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Problem with MAVEN_HOME in a build

[Nord, James]

Hi Erik,

I personally wouldn’t recommend putting MAVEN_HOME in a profile, rather it is 
better to let Jenkins managed this by specifying the version of maven to use.

You can configure this in the Jenkins main config (and then override per slave 
if needs be.)

See 
http://my.safaribooksonline.com/book/software-engineering-and-development/ide/9781449311155/configuring-your-jenkins-server/sect-configuration-build-tools
 for more details.

BTW – is this with the “m2release plugin” on a maven type job or with the 
“release plugin” on a freestyle job?

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Erik
Sent: 17 September 2012 08:44
To: jenkinsci-users@googlegroups.com
Subject: Re: Problem with MAVEN_HOME in a build

I get the same exception in Jenkins v. 1.477 and maven 2.2.1

Everything works fine, except for the release. There I get this exception.

[INFO] Exception in thread "main" java.lang.NoClassDefFoundError: 
org/codehaus/classworlds/Launcher

[INFO] Caused by: java.lang.ClassNotFoundException: 
org.codehaus.classworlds.Launcher

Thanks,
Erik


Am Donnerstag, 6. September 2012 19:14:13 UTC+2 schrieb mpapo - Michaël 
Pailloncy:
Hi,

We faced in a problem with Maven during a release build. The job is configured 
with the Release Plugin.
MAVEN_HOME variable is correctly set during the first build (and any 'normals' 
builds), but when we launch a release and the build arrive to the command 'mvn 
.. release:clean release:prepare release:perform' to launch the Maven3 release, 
it seems that the MAVEN_HOME variable is not set correctly and the build crashs 
with this error :

class not found:  org.codehaus.classworlds.Launcher  -  
org.codehaus.classworlds.Launcher

We have also Maven2.2.1 and Maven3.0.3 installed on the master (AIX) which 
build this job.
In .profile file, M2_HOME is by default set to Maven2.2.1.

The problem is appeared since we have updated Jenkins with version 1.478.
The same job worked correctly before the update (last release has been built 
just before our update of Jenkins and the mvn command worked correctly).

Is this a bug ? Does I create a ticket in Jira ?

Thanks in advance from any help !
Michaël




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Cloudbees Enterprise ?? How useful is it ??

[Nord, James]

Hi,

Templates is a major feature.  The VMWare plugin is nice in that it you can 
also allocate VMs to slaves so its not autoscalling as such but you can get a 
pristine environment in which to run integration/acceptance style tests without 
risk of any polluted environment.  (I think the OSS VMWare plugin may now have 
similar functionality but it didn't exist when the cloudbees one was written).

But having said that - support is king!  When you tie Jenkins to the heart of 
you build test release procedure then any issue is likely to stop the business 
- so having the support line is more than a nice to have.

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Tom80112
> Sent: 17 September 2012 22:22
> To: jenkinsci-users@googlegroups.com
> Subject: Cloudbees Enterprise ?? How useful is it ??
>
> I watched a Cloudbees Enterprise webinar today.  This is essentially Jenkins 
> plus
> a bunch of their in-house developed plugins.
>
> The VMware plugin seemed interesting for load-balancing Jenkins jobs
> amongst a group of Jenkins slaves but other than that I didn't see anything
> earth shatteringly new here.  Most of the plugins seem like you could script 
> the
> same functionality within the shell window.
>
> Oh yes,  I will admit the security roles is a new feature but we don't need 
> that
> level of security.
>
> So has anyone used Cloudbees Enterprise ??
> What have you found that it does that base Jenkins cannot do??
>
> Thanks...
>
>
>
> --
> View this message in context: http://jenkins.361315.n4.nabble.com/Cloudbees-
> Enterprise-How-useful-is-it-tp4640478.html
> Sent from the Jenkins users mailing list archive at Nabble.com.




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Forcing 32-bit or 64-bit install of JDKs through Jenkins' auto-install

[Nord, James]

Hi Michael

There is an open JIRA[1] about this. (workaround is to package (which is not 
hard) your own and call it jdk1.7.0_64 jdk1.7.0_32) and the job is then 
explicitly tied to a 32bit or 64bit jdk regardless of the platform that it is 
running on.

/James

[1] https://issues.jenkins-ci.org/browse/JENKINS-3963

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mike Chmielewski
Sent: 13 September 2012 17:08
To: jenkinsci-users@googlegroups.com
Subject: Forcing 32-bit or 64-bit install of JDKs through Jenkins' auto-install

I've done some google searching, and haven't seen anything about this.

Is there a way to tell/force the auto-installer to install the 32-bit vs. 
64-bit version of the SDK? Our product is such that older legacy jobs need to 
use the 32-bit JDK.

Thanks!

--

Michael Chmielewski | Senior Release Engineer

Contact | (w) 617.478.9368

Connect | Twitter | 
LinkedIn



BULLHORN(r) | Follow 
Us



NOTICE: This email and any attachments may contain confidential and proprietary 
information of Bullhorn Inc. and is for the sole use of the intended recipient 
for the stated purpose. Any improper use or distribution is prohibited. If you 
are not the intended recipient, please notify the sender; do not review, copy 
or distribute; and promptly delete or destroy all transmitted information. 
Please note that all communications and information transmitted through this 
email system may be monitored by Bullhorn or its agents and that all incoming 
email is automatically scanned by a third party spam and filtering service.





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Looking for Help with M2 Release Plugin and Hudson

[Nord, James]

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=375565 for the workaround.

I think there may be a bug in the Jenkins hpi plugin that isn't handling 
transitive hpi dependencies correctly

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of sdoca sdoca
Sent: 24 August 2012 22:57
To: jenkinsci-users@googlegroups.com
Subject: Looking for Help with M2 Release Plugin and Hudson

Hi,

I'm using Hudson and am looking for some help with the M2 Release Plugin 
(http://wiki.hudson-ci.org/display/HUDSON/M2+Release+Plugin) which is being 
maintained in the Jenkins space.  If there's a different list/forum that's more 
appropriate to ask questions about this plugin and Hudson, I'd appreciate a 
link.

I recently upgraded to Hudson 2.2.1 and tried to upgrade the M2 Release plugin 
from 0.8.1 to 0.9.1 but I get this error:

[#|2012-08-24T15:12:37.250-0600|SEVERE|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=72;_ThreadName=Thread-1;|WebModule[/hudson]Error
 while serving http://myserver:8080/hudson/pluginManager/install
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)

... [snip] ...

[#|2012-08-24T15:12:37.250-0600|SEVERE|glassfish3.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=72;_ThreadName=Thread-1;|WebModule[/hudson]Error
 while serving http://myserver:8080/hudson/pluginManager/install
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)

... [snip] ...

Is this a Hudson/plugin compatability issue?

Also, when I first installed the 0.8.1 version of the plugin, I was not able to 
use it because access issues to our SCM (Mercurial).  We've now fixed that and 
I'm trying to set up a Maven release job, but the directions on the plugin page 
(https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin) but my job 
configuration page doesn't have a "Build Environment" section, nor do I have a 
"Perform Maven Release" link.  I don't know if these are differences between 
Jenkins and Hudson, the plugin versions or if I never had the plugin installed 
correctly in the first place.

Any guidance is greatly appreciated!




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: What is the name of the 'todo' plugin?

[Nord, James]

I think you are looking for the task scanner plugin

https://wiki.jenkins-ci.org/display/JENKINS/Task+Scanner+Plugin

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kenneth
Sent: 22 August 2012 10:10
To: jenkinsci-users@googlegroups.com
Subject: What is the name of the 'todo' plugin?

That afte compilation runs through source code and can find todo, and other 
comments
that needs to be addressed?

thanks
Kenneth




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: When will Jenkins LTS support Subversion 1.7?

[Nord, James]

Hi David,

It may happen in the next versionof LTS which would be in 3 months time.

You can should be able to run the latest subversion plugin in the just released 
LTS.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: 06 August 2012 15:23
To: jenkinsci-users@googlegroups.com
Subject: When will Jenkins LTS support Subversion 1.7?

Hi

Subversion 1.7 was first supported in version 1.40 of the Jenkins Subversion 
Plugin.

Does anyone know when Jenkins Subversion plugin 1.40 or later will be included 
in a Jenkins LTS release?

Best regards

David





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: What is the latest LTS release?

[Nord, James]

The "latest" symlink is a bit messed up.

You can download 1.466.1 from 
http://mirrors.jenkins-ci.org/war-stable/1.466.1/jenkins.war

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of David Aldrich
> Sent: 06 August 2012 10:07
> To: jenkinsci-users@googlegroups.com
> Subject: RE: What is the latest LTS release?
>
> This is weird. I downloaded what I thought to be 1.466.1 and installed it but
> Jenkins is now indicating 1.447.2.
>
> Also,
>
> http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war
>
> is now offline.
>
> Is it being updated?
>
> David
>
> > -Original Message-
> > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> > us...@googlegroups.com] On Behalf Of Richard Bywater
> > Sent: 06 August 2012 09:41
> > To: jenkinsci-users@googlegroups.com
> > Subject: Re: What is the latest LTS release?
> >
> > 1.466.1 is the latest as far as I'm aware.
> >
> > I've had problems in the past with Manage Jenkins screen showing the
> > correct next version - thought it had been fixed but perhaps there is
> > some process that needs to run on a server somewhere to make it
> > visible to that screen?
> >
> > Cheers
> > Richard.
> >
> > On Mon, Aug 6, 2012 at 8:38 PM, David Aldrich
> >  wrote:
> > > Hi
> > >
> > >
> > >
> > > I am running Jenkins LTS release v.1.447.1.  My 'Manage Jenkins'
> > > page shows that 1.447.2 is available.  But this Jenkins change log:
> > >
> > >
> > >
> > > http://jenkins-ci.org/changelog-stable
> > >
> > >
> > >
> > > shows that 1.466.1 is available.
> > >
> > >
> > >
> > > What is the latest LTS release please?
> > >




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Permalink to last Maven release builds usable in downstream build?

[Nord, James]

Hi Radim/Domi,

It may also be because m2release plugin doesn't work well with Jenkins 
artifacts archival - see https://issues.jenkins-ci.org/browse/JENKINS-7487?

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of domi
> Sent: 30 July 2012 17:32
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Permalink to last Maven release builds usable in downstream
> build?
>
> Hi Radim,
> please fill an issue for this.
> regards Domi
>
> On 30.07.2012, at 13:54, Radim Kubacki wrote:
>
> > Hi,
> >
> > I wanted to create a pipeline with a
> > 1. Maven build that builds project including few of its subprojects
> > and configured settings for Maven release build 2. manually executed
> > downstream build to take deployed artifact(s) from latest Maven
> > release build and push it to our testing enviroment (install RPM or
> > deploy web application).
> >
> > I can do (2.) as a promotion but I do not like it. (I'd like to run
> > some integration tests when the build is is deployed. Also there can
> > be more staging levels so deployment pipeline looks like a better
> > solution than a set of promotions.)
> >
> > I am almost there with the help of Maven Deployment Linker plugin
> > (http://wiki.hudson-ci.org/display/HUDSON/Maven+Deployment+Linker) but
> > I can only choose to select last {|stable|successfull|failed} build as
> > a source of my artifacts in this downstream build. Why isn't release
> > build here when Maven plugin creates a permalink for lastRelease job?
> > Configuring it to lastStable build is not an option: there can be some
> > manual test between build and deployment build and even without the
> > release build initiates new non-release build called from an SCM
> > trigger when version update is pushed as a result of maven release.
> >
> > So is there a way how to access last release build data from some
> > downstream build? If there is not how difficult it would be to add it?
> >
> > -Radim





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: M2 release build and Trigger build

[Nord, James]

No – by trigger I meant a job step that executed curl.

If you have any reported/publishers that effect the build outcome then you 
would need to write your own publisher that then performed the http post (or 
seeing as you are already inside Jenkins called the job with the m2release).

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Eskay
Sent: 23 June 2012 11:13
To: jenkinsci-users@googlegroups.com
Subject: Re: M2 release build and Trigger build

I take it that you are referring to using "Trigger/Call builds on other 
projects". This takes project name as input. I don't see any obvious way to 
include action to kickoff. Am I missing something?

I guess I could use remote trigger instead and put action on the URL. This 
approach seem to have some downside since it is not as tightly integrated as 
Trigger/Call builds.

On Saturday, June 23, 2012 5:01:29 AM UTC-4, teilo wrote:
You can add a trigger on the upstream job to post to the action to kick off a 
build.

However you will need to post the data (developmentURL etc).

/James

> -Original Message-
> From: 
> jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Eskay
> Sent: 23 June 2012 02:53
> To: Jenkins Users
> Subject: M2 release build and Trigger build
>
> I have a Maven job on Jenkins that has both regular build (build-now) and M2
> release build. Is there a way to trigger M2 release build, as opposed to 
> regular
> build, from a master build job?




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: M2 release build and Trigger build

[Nord, James]

You can add a trigger on the upstream job to post to the action to kick off a 
build.

However you will need to post the data (developmentURL etc).

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Eskay
> Sent: 23 June 2012 02:53
> To: Jenkins Users
> Subject: M2 release build and Trigger build
>
> I have a Maven job on Jenkins that has both regular build (build-now) and M2
> release build. Is there a way to trigger M2 release build, as opposed to 
> regular
> build, from a master build job?


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Release the m2release plugin

[Nord, James]

I've not had time to test it yet.

Have you tested it - and which of the new features have you tested.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jay Keshur
Sent: 20 June 2012 12:35
To: jenkinsci-users@googlegroups.com
Subject: Release the m2release plugin

Hi,

Could someone release 0.10.0 of M2 Release plugin please 
(https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin)

Cheers.


Regards,

Jay Keshur



This message contains confidential and proprietary information of the sender, 
and is intended only for the person(s) to whom it is addressed. Any use, 
distribution, copying, disclosure or taking of any action in reliance upon it 
by any other person is strictly prohibited. If you have received this message 
in error, please notify the e-mail sender immediately, and delete the original 
message without making a copy.

The Monitise group comprises: Monitise plc (Reg. No. 6011822), Monitise Group 
Limited (Reg. No. 5590897), Monitise International Limited (Reg. No. 5556711) 
and Monitise Europe Limited (Reg. No. 4831976). These companies are registered 
in England and Wales and their registered office address is: Warnford Court, 29 
Throgmorton Street, London, EC2N 2AT United Kingdom.



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: M2 Release plugin disapper

[Nord, James]

Hi Tim,

The following page should give detailed information about this: 
https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup

Specifically Within the Job”permission group there will be a permission 
called“Release”

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of ??
Sent: 12 June 2012 14:52
To: jenkinsci-users@googlegroups.com
Subject: Re: M2 Release plugin disapper

Upgrade to the latest version whatever for jenkins or m2 release plugin, 
collabet net plugin, problem still happens.

Does anyone know how to auth the M2 release plugin?

Br,
Tim
2012/6/12 吴亭 mailto:wutingb...@gmail.com>>
Does any one met this problem before?

Br,
Tim

2012/6/12 吴亭 mailto:wutingb...@gmail.com>>
Hi Nord,

Thanks for your reply, could you see more detail about this, I search a lot 
from my jenkins config tab and do not find this configuration.

Thanks in advance.

Br,
Tim
2012/6/11 Nord, James mailto:jn...@nds.com>>

There is a separate permission for the m2release that you can configure in the 
Jenkins config.


From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Tim
Sent: 11 June 2012 14:57
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: M2 Release plugin disapper

Hi there,

I am using the M2 Release plugin for us to release the project, and recently, 
for the security issue, we use team forge to auth the project. However, I 
found, only admin can do the maven release, other team member can not see 
"Perform maven release" Button.

Do you have any experience for this?

Br,
Tim



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com<mailto:postmas...@nds.com> and delete it from your system as 
well as any copies. The content of e-mails as well as traffic data may be 
monitored by NDS for employment and security purposes. To protect the 
environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: M2 Release plugin disapper

[Nord, James]

There is a separate permission for the m2release that you can configure in the 
Jenkins config.


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Tim
Sent: 11 June 2012 14:57
To: jenkinsci-users@googlegroups.com
Subject: M2 Release plugin disapper

Hi there,

I am using the M2 Release plugin for us to release the project, and recently, 
for the security issue, we use team forge to auth the project. However, I 
found, only admin can do the maven release, other team member can not see 
"Perform maven release" Button.

Do you have any experience for this?

Br,
Tim



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: M2 Release Plugin not showing

[Nord, James]

What type of project are you using?

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Marcus Thormählen
Sent: 21 May 2012 15:30
To: jenkinsci-users@googlegroups.com
Subject: M2 Release Plugin not showing

I have Jenkins 1.464 and M2 Release Plugin v0.9.1 and i want to configure my 
project for release. The problem is that in the project configuration I cannot 
see any options except "[] Execute shell script on remote host using ssh". I 
expect to see the ones from 
here and also 
see a "Perform Maven Release" button but I don't.

I also see "Maven Release Plug-in" > "Enable Nexus Pro support" in global 
Jenkins configuration, so the plugin IS installed...just missing the project 
configuration.

Any advise, perhaps some dependancies?



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: M2 Release Plugin + SVN

[Nord, James]

Add "-Dusername=releaseuser" to the command line (if different from the user 
that runs Jenkins)

Authenticate against SVN server using the svn command line tools on the slave
(this updates ~jenkinsuser/.subversion/auth/)
Copy that around all your slaves.

Jenkins also has the ability somewhere to store the credentials it uses to 
checkout in the auth cache.

YMMV.

/James


> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of BusyByte
> Sent: 21 May 2012 16:23
> To: Jenkins Users
> Subject: M2 Release Plugin + SVN
>
> How do I pass my credentials for maven to do the SCM plugin stuff for the
> Maven Release.
> I don't want each job to have to enter the process id username/ password.
> I tried to put it in my settings.xml by the base host name for svn server.
> EG https://myhost/mysvnpath I put a server entry with: myshost


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: keeping m2 repository disk space under control

[Nord, James]

You can (in a one of the latest Jenkins) set the private repo to be per 
executor.
You can then schedule a job to run on that executor periodically to rm –fr 
privaterepo.

This has drawbacks as an “mvn install” from one job is visible to all other 
jobs on the same executor, whereas you really only want the results of mvn 
deploy to be visible.

The other alternative is to take a look at 
https://wiki.jenkins-ci.org/display/JENKINS/Maven+Repo+Cleaner+Plugin

Note I have done neither, so YMMV.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jorg Heymans
Sent: 16 May 2012 09:12
To: jenkinsci-users@googlegroups.com
Subject: keeping m2 repository disk space under control

Hi,

For a large (100+ m2 jobs) Jenkins instance, what are my options to control the 
diskspace taken up by the jobs' private m2 repos ? Since maven does not handle 
access to its own local repo transactionally (vote here 
http://jira.codehaus.org/browse/MNG-2802) we need to set a private local repo 
per job.

Has anyone been able to tackle this in some way or another ?

Thanks !
Jorg



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: How to know if a job is enabled with Jenkins REST ?

[Nord, James]

Does http://myserver/job/myjob/api/xml?xpath=*/buildable do what you need?

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of HARDION Vincent
> Sent: 09 May 2012 13:34
> To: jenkinsci-users@googlegroups.com
> Subject: How to know if a job is enabled with Jenkins REST ?
>
> Hi all,
>
> I don't find the way to know the state enable/disable of a job through the
> jenkins REST !
> Some urls exist but only accessible to post action.
>
> Any idea ?
>
> Vincent


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: M2Release plugin: unable to choose Verioning mode

[Nord, James]

Hi Gianluca,

With the current version mode was removed – and you can only have one version 
for all modules.

If you want something different (I’m still to hear from someone with a 
convincing argument) then you will have to use an older version (0.7.1).
There is also an open defect that you may want to watch (JENKINS-11466).

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Gianluca Chiodaroli
Sent: 18 April 2012 15:53
To: jenkinsci-users@googlegroups.com
Subject: M2Release plugin: unable to choose Verioning mode

Hi to all, i have installed Jenkins 1.460 and m2release plugin 0.9.1 as a 
windows service.
When i try to release a maven3 multimodule project i'm unable too choose 
Versioning mode, the plugin set the version of parent pom to all modules.
I miss somethings?

Thanks for your help.

Gianluca



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Change path of .m2 directory if using maven-plugin

[Nord, James]

Jenkins did (does) use the local users repo when it is parsing the POM files 
(before the invocation of maven on the executor)

If you switch to the freestyle job this should work – but you will loose all of 
the goodness that comes with the Maven2 type job.

But – as you’re administrators expect this to be set per web-app in the app 
server why don’t you ask them to configure it for you on the app server?

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Michael Wieland
Sent: 20 March 2012 19:27
To: jenkinsci-users@googlegroups.com
Subject: Re: Change path of .m2 directory if using maven-plugin

Hi,

I already tried that using the MAVEN_OPTS configuration field. But Maven still 
uses the old home directory.


On Tuesday, March 20, 2012 7:20:56 PM UTC+1, domi wrote:
add "-Duser.home=/oath/toNewDir" to the options
/Domi


On 20.03.2012, at 13:53, Michael Wieland wrote:


Hi,

thanks for your reply but that didn't solved the problem. :(

This option only changes the location of the local repository. The path to the 
.m2 directory does not change by using this option.

A build fails with this error message:
ERROR: Failed to create /not/existing/user/dir/.m2

I've looked at the source code of the maven-plugin and saw the path is hard 
coded to the property "user.home". Is there any way to set the user.home 
property in a Maven job?


Regards

Michael


On Tuesday, March 20, 2012 1:35:58 PM UTC+1, Richard Mortimer wrote:
Hi,

You question is best addressed to 
jenkinsci-users@googlegroups.com.
jenkinsci-issues@ is used for automated JIRA messages.

That said I've answered your question below etc. and posted to -users
for others to comment as appropriate.

On 20/03/2012 11:39, Programie wrote:
> Hi,
>
> I'm using Jenkins with the Maven plugin. Jenkins is running in a Tomcat
> container.
>
> Tomcat is running using the wwwjenkins user. However the home directory of
> this user does not exist. The administrators of the server said me, they set
> it to an invalid directory to have an unique directory for each application.
> That may makes sense because multiple applications can run in the same user
> context.
>
> The problem: Maven tries to create the .m2 directory in the not existing
> home directory of the wwwjenkins user. How can I change the path used by
> Maven for the .m2 directory? I want to move it to JENKINS_HOME.
>

If you navigate to the "Manage Jenkins" page you can set the location of
the .m2 directory in the "Maven Project Configuration" section.

/configure

You can set it to be "Local to executor" or "Local to workspace". I
suspect that you want "Local to workspace".

Regards

Richard











**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Retrieve Nexus Url after build

[Nord, James]

Ah...

Assuming you only have one release repo then its possible without asking nexus.

You can get the MavenModule from Jenkins - then get its group artifact and id.
Then the URL follows the standard maven pattern which is something like -  
http://repo/repo_path/group_id_replace_dot_with_slash/artifactid/version/artifactid-version-qualifier.type

/James

> -Original Message-
> From: Nord, James
> Sent: 12 March 2012 14:32
> To: Jenkins Users
> Subject: RE: Retrieve Nexus Url after build
>
> The nexus rest implementation is what you need (see the nexus user email 
> list).
>
> You may be able to gets some information from the m2release plugin source
> but not so sure that would help in this case.
>
> /James
>
> > -Original Message-
> > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> > us...@googlegroups.com] On Behalf Of Efavre
> > Sent: 12 March 2012 13:52
> > To: Jenkins Users
> > Subject: Retrieve Nexus Url after build
> >
> > Hello,
> >
> > I have a Maven3 job which builds my artifact and deploys it to the
> > release repo on Nexus.
> > I would like to send an e-mail the the deployment team once the build
> > is done and successful. I added the E-mail Extension Plugin, but I
> > can't figure out how to retrieve the full Nexus url on which I
> > deployed the artifact (something like
> > http://my.nexus/service/local/repositories/release/content/com/mycompa
> > ny/
> > my-project/1.2.3/my-project-1.2.3.jar)
> >
> > Can anybody help ?
> >
> > Thanks,
> >
> > Eric


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Retrieve Nexus Url after build

[Nord, James]

The nexus rest implementation is what you need (see the nexus user email list).

You may be able to gets some information from the m2release plugin source but 
not so sure that would help in this case.

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Efavre
> Sent: 12 March 2012 13:52
> To: Jenkins Users
> Subject: Retrieve Nexus Url after build
>
> Hello,
>
> I have a Maven3 job which builds my artifact and deploys it to the release 
> repo
> on Nexus.
> I would like to send an e-mail the the deployment team once the build is done
> and successful. I added the E-mail Extension Plugin, but I can't figure out 
> how to
> retrieve the full Nexus url on which I deployed the artifact (something like
> http://my.nexus/service/local/repositories/release/content/com/mycompany/
> my-project/1.2.3/my-project-1.2.3.jar)
>
> Can anybody help ?
>
> Thanks,
>
> Eric


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

signatures or hashes for wars?

[Nord, James]

Hi all,

Are there any signatures available for the war that can be downloaded from 
mirrors.
I looked on cucumber but only see the war - and although I could be unfriendly 
and download from there I would like to use a mirror.
But I can't see a way to see that the war hasn't been tampered with at any 
point (OK cucumber itself could be hacked but)

Am I missing the obvious place that I should be looking?

IIRC the update center information is signed which prevents some tampering of 
plugins - but the war would be an obvious candidate as well would it not?

/James




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: Port issue

[Nord, James]

If jenkins runs out of file descriptors whilst trying to accept a socket 
connection this will (in my experience) cause the winstone listener to die.

See the last comment on https://issues.jenkins-ci.org/browse/JENKINS-9882

/james

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Didier Durand
> Sent: 27 February 2012 09:34
> To: Jenkins Users
> Subject: Re: Port issue
>
> Hi,
>
> When you say that "port 8080 gets down" does it mean that the jenkins server
> is down: i.e do you find it  via ps -ef on linux console ?
>
> Other question; is your jenkins running natively (suning embedded
> Winstone) or within a container (tomcat or other)?
>
> regards
>
> didier
>
> On Feb 27, 9:19 am, Suri  wrote:
> > Hi
> >
> > Our Jenkins server is Red Hat Linux.
> > We are frequently getting Webpage issue in Jenkins. i have checked
> > Jenkins service in server, When webpage is down.
> > Jenkins service status showing as running . but the webpage is down.
> > Not able to access Jenkins Webpage.
> >
> > I have found port 8080 is not running in server. It is frequently
> > getting down automatically.
> > We  don't know, why the port is getting down?
> > I have checked from Server and Network end. It seems to be well.
> >
> > For temporarily solution We have created a crontab entry with a
> > Jenkins service startup script, it will check the 8080 status, when
> > ever the 8080 port is down it will automatically restart the Jenkins
> > service Can anyone please advise me, Why the port is getting down
> > automatically.


**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: custom build environments?

[Nord, James]

What we have done is use maven to setup the environment with some calls to tar 
etc.
We build boost and store it (versioned) in a maven repo (as tar.gz including 
object headers etc).
Then what needs boost downloades it and unpacks it into a workspace relative 
path.The make scrips are all configured to use workspace relative paths so to 
get a different version you change the maven dependency.

Its relatively simple - just make sure you use the platform tar not maven 
assembly plugin to create the archive (or you loose the symlinks).

As you're using autoconf I would guess you then need to pass in 
-with-boost=./boost or something equivellent

Hope that helps (although the chroot sounds much better :) )

/james

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dean Yu
Sent: 23 February 2012 01:05
To: jenkinsci-users@googlegroups.com; Mark Waite
Subject: Re: custom build environments?

We have an internal plugin that manages chroots for exactly this scenario. We 
set up the chroot through a BuildWrapper, and we override the launch method so 
that each build step enters the chroot before it executes. There's a lot of 
internal-only code in here, so it's not something we can open source. However, 
if you want more information, I can sketch out some more detail for you.

  -- Dean


On 2/22/12 2:57 PM , "Mark Waite"  wrote:
I experimented once with a "chroot" environment as a way to have different 
configurations on the same Linux machine.  I found chroot to be more 
complicated than I was ready to use at the time, but I believe it can be used 
to provide different executable versions hosted over the same Linux kernel.

If you need different Linux kernels in addition to different libraries and 
tools, then I think you'll need separate machines (physical or virtual).

Mark Waite




 From: Les Mikesell 
 To: jenkinsci-users 
 Sent: Wednesday, February 22, 2012 1:19 PM
 Subject: custom build environments?


Does anyone have suggestions for how to get Jenkins to make Linux
builds that don't match the stock system environment that
autoconf/configure would find?  For example, if you want to have
multiple versions of boost installed and compile jobs that each need
some specific version.



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

[ANN] M2Release plugin

[Nord, James]

Hi all,

I don't normally do announcements but there is a new version of the 
Jenkins/Hudson m2Release plugin available.

Unlike previous versions which just worked in any Hudson or Jenkins version 
greater than declared in the plugin this version will work with either of the 
options below:


* Jenkins 1.442 or higher

* Jenkins LTS 1.424.2 or higher

* Hudson with the maven-plugin 2.2.1 or higher

See 
https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin#M2ReleasePlugin-VersionHistory
 for a list of changes.

/James





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: warnings plugin

[Nord, James]

a parser has an optimization step: it using a string matcher for each 
line that detects the existence of the word "warning". Only lines containing 
that text will be matched with the regular expression afterwards. I don't 
remember the syntax of JavaDoc warnings, is there a similar string that can be 
used?

And 750MB is a really large log file :-) As a workaround you can try to write 
the output of the javadoc processing to a different file.

Ulli



On 02/09/2012 05:32 PM, Nord, James wrote:
Hi,

We have the warnings plugin enabled – which looks for javac and javadoc 
warnings in the maven2 type build.

All is fine until I ran a release.  The warnings plugin took about 9.5 hours 
(yes nine and a half) to parse the console to find the javadoc warnings!?
A build of deploy site-deploy with the same configuration takes a few minutes.

The main difference is the maven jobs use 
-Dmaven.test.redirectTestOutputToFile=true (and as such the console was large 
~700MB)
However the javac error parsing completed in a few minutes…

(
Java Compiler
JavaDoc

)

The parser found 161 javadoc warnings – so not that many :-P

Stack trace from the job is as follows

"Executor #0 for : executing commit #5" Id=63 Group=main RUNNABLE
at java.util.regex.Pattern$CharProperty.match(Pattern.java:3694)
at java.util.regex.Pattern$Curly.match0(Pattern.java:4158)
at java.util.regex.Pattern$Curly.match(Pattern.java:4132)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
at java.util.regex.Pattern$Branch.match(Pattern.java:4500)
at java.util.regex.Pattern$Start.match(Pattern.java:3408)
at java.util.regex.Matcher.search(Matcher.java:1198)
at java.util.regex.Matcher.find(Matcher.java:591)
at 
hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:81)
at 
hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:82)
at 
hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:273)
at 
hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:278)
at 
hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:244)
at 
hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
at 
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682)
at 
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657)
at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:942)
at 
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604)
at hudson.model.Run.run(Run.java:1400)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:476)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:175)


Is there something massively different between how javadoc and javac warnings 
are tracked – I’m unclear why it took so long.

Monitoring showed there was plenty of heap available and although this is on a 
vm – it pretty much had one core of a X5690 dedicated to this parsing (Jenkins 
itself has 2 vcpus – and the whole system was mostly idle.)

Jenkins 1.424.2 with 3.26 of the warnings plugin.

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com<mailto:postmas...@nds.com> and delete it from your system as 
well as any copies. The content of e-mails as well as traffic data may be 
monitored by NDS for employment and security purposes. To protect the 
environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

warnings plugin

[Nord, James]

Hi,

We have the warnings plugin enabled - which looks for javac and javadoc 
warnings in the maven2 type build.

All is fine until I ran a release.  The warnings plugin took about 9.5 hours 
(yes nine and a half) to parse the console to find the javadoc warnings!?
A build of deploy site-deploy with the same configuration takes a few minutes.

The main difference is the maven jobs use 
-Dmaven.test.redirectTestOutputToFile=true (and as such the console was large 
~700MB)
However the javac error parsing completed in a few minutes...

(
Java Compiler
JavaDoc

)

The parser found 161 javadoc warnings - so not that many :-P

Stack trace from the job is as follows

"Executor #0 for : executing commit #5" Id=63 Group=main RUNNABLE
at java.util.regex.Pattern$CharProperty.match(Pattern.java:3694)
at java.util.regex.Pattern$Curly.match0(Pattern.java:4158)
at java.util.regex.Pattern$Curly.match(Pattern.java:4132)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
at java.util.regex.Pattern$Branch.match(Pattern.java:4502)
at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556)
at java.util.regex.Pattern$Branch.match(Pattern.java:4500)
at java.util.regex.Pattern$Start.match(Pattern.java:3408)
at java.util.regex.Matcher.search(Matcher.java:1198)
at java.util.regex.Matcher.find(Matcher.java:591)
at 
hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:81)
at 
hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:82)
at 
hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:273)
at 
hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:278)
at 
hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:244)
at 
hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
at 
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682)
at 
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657)
at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:942)
at 
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604)
at hudson.model.Run.run(Run.java:1400)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:476)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:175)


Is there something massively different between how javadoc and javac warnings 
are tracked - I'm unclear why it took so long.

Monitoring showed there was plenty of heap available and although this is on a 
vm - it pretty much had one core of a X5690 dedicated to this parsing (Jenkins 
itself has 2 vcpus - and the whole system was mostly idle.)

Jenkins 1.424.2 with 3.26 of the warnings plugin.

/James



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**