RE: Jenkins problem with clocks going back?

[James Nord (jnord)]

Hi Dirk,

I really don’t follow – unless you are on an out of date windows verison it 
does now have an option for UTC as a proper UTC unline the old “Grenwich Mean 
Time” which was actually Europe/London.

[cid:image001.png@01CFF1D2.B5F237D0]


No daylight saving options are there

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dirk Heinrichs
Sent: 27 October 2014 10:32
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins problem with clocks going back?

Am 27.10.2014 um 11:23 schrieb James Nord (jnord):

My preffered way of handling this is to always run your infrastructure in 
Etc/UTC.

Fine if it's Unix/Linux. Doesn't work on Windows, because hardware clock is 
always on localtime there.

Bye...

Dirk
--
[cid:image003.gif@01CFF1D2.B5F237D0]
Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 159 (Ansage) 1149
Email: d...@recommind.com<mailto:d...@recommind.com>
Skype: dirk.heinrichs.recommind
www.recommind.com<http://www.recommind.com>
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

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

RE: Jenkins problem with clocks going back?

[James Nord (jnord)]

> It's not a big problem for us (it might be more of a problem for others), but
> any suggestions as to how to handle this in future

My preffered way of handling this is to always run your infrastructure in 
Etc/UTC.

It means you never hit the time changing issue - and when you need to integrate 
with servers in a different timezone[1] all the logs will tie up perfectly.

Now - an enhancement would be for the Jenkins UI to convert from Server time to 
user local time to display timestamps in the UI...

/James

(you may have zero now - but you may end up using cloud or acquiring a foreign 
company in the future)

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

RE: Question about a smart logging feature

[James Nord (jnord)]

Hi,

The following plugin may help (disclaimer – never used it)

https://wiki.jenkins-ci.org/display/JENKINS/Flaky+Test+Handler+Plugin

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ricardo Junior
Sent: 23 October 2014 14:51
To: jenkinsci-users@googlegroups.com
Subject: Question about a smart logging feature

Hey everyone,

We have a Jenkins set up running some Rspec test cases performing browser 
automation, and the failure frequency of some tests are very oscillating (e.g. 
Today it passes, tomorrow fails, yesterday passes). I have the following 
question: Is there any plugin or feature of Jenkins that could organize a 
ranking of the most failing tests? This would be useful so we could see what 
tests might need to be refactored.

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

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

RE: build-flow test result aggregation not working

[James Nord (jnord)]

Last time I looked at the code jobs run from the build flow don’t actually show 
up as downstream jobs – so the report aggregation is working flawlessly and 
aggregating all downstream jobs (which is no jobs).

So it’s not a configuration issue – but a code issue.

Regards,

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Thilo-Alexander Ginkel
Sent: 22 October 2014 18:20
To: jenkinsci-users@googlegroups.com
Subject: build-flow test result aggregation not working

Hi there,

I have defined a parallel build using the build-flow plugin [1]:

-- 8< --
revision = build.properties["environment"]["GIT_COMMIT"]

parallel (
{ build("rspec", GIT_COMMIT: revision) },
{ build("cucumber-backend", GIT_COMMIT: revision) }
)
-- 8< --

Both dependent build generate test results in JUnit format located in 
tmp/test_results/*.xml and have the "Publish JUnit test result report" 
post-build action pointed to that location. Fingerprinting is also enabled for 
tmp/test_results/*.xml.

Both sub-builds display the test results correctly. What I can't seem to get 
working, though, is aggregating these results in the build-flow build, which 
has fingerprinting for **/* enabled and "Aggregate downstream test results" 
configured. Still, the build-flow build consistently states: "Latest Aggregated 
Test 
Result
 (no tests)"

Any ideas?

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

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

RE: Jenkins become unresponsive

[James Nord (jnord)]

Are you on Linux and are you using the embedded container?
If so have you upped the number of file descriptors available from Jenkins – I 
have see in the past that is was not uncommon for the HTTP receiving thread to 
die due to not being able to handle a connection correctly.

Otherwise – jstack will likely be your friend – will show any deadlocks and 
show what threads are running.

/james

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Rupali Chorghe
Sent: 21 October 2014 04:11
To: jenkinsci-users@googlegroups.com
Subject: RE: Jenkins become unresponsive


Hi Terrence,

Thanks for reply.
Problem we are facing is when Jenkins becomes unresponsive, everything that 
needs Jenkins URL, becomes inaccessible. So we decided to use Jconsole. But we 
didn't find abnormalities in CPU and memory usage when monitored using jconsole.

Regards,
Rupali
On 21-Oct-2014 2:49 am, "Dunnigan, Terrence J" 
mailto:terrence.j.dunni...@boeing.com>> wrote:
Are you using the Jenkins Monitoring plugin?

https://wiki.jenkins-ci.org/display/JENKINS/Monitoring

It might help to provide some context and additional information when Jenkins 
is not responding.

Terry

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com]
 On Behalf Of Rupali
Sent: Monday, October 20, 2014 6:46 AM
To: jenkinsci-users@googlegroups.com
Subject: Jenkins become unresponsive

Hi,

We are facing one weird issue.
Intermittently, our Jenkins URL becomes inaccessible. Only restarting Jenkins 
service resolves the issue.

We are using Jenkins 1.565. We tried to analyses memory and CPU usage when such 
state appears. But CPU usage looked very low around 2% and memory usage by 
Jenkins Java process also was around 1.7 GB which is the case usually. We have 
Master-Slave setup containing 8 slave machines of which 2 slaves have dedicated 
jobs to run.

Can you advise on how to analyze this issue to find out the root cause of 
Jenkins becoming inaccessible?

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

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

RE: Start m2release plugin execution with dsl flow

[James Nord (jnord)]

I think (not tested)
If you construct a ReleaseCause and an M2ReleaseArguments with the appropriate 
arguments
You may be able to do this programmatically by
scheduleBuild(0, new ReleaseCause(), parameters, arguments)

However I think this may require a DSL extension in the plugin.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of thibaut bourquardez
Sent: 09 October 2014 13:02
To: jenkinsci-users@googlegroups.com
Subject: Start m2release plugin execution with dsl flow

Hello,
on my project, i want to start the release of some maven project conditionnaly 
with Jenkins.
i found the build flow plugin 
(https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin) which seems to 
be great for this, except on one point :
i want to launch an execution of m2release plugin 
(https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin) on each job but 
i can't find the way to do this.
the command build("job_name") start a build, but i don't know how to call 
m2release plugin execution.
Is there a way to do it?
Thanks.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

RE: Let Build Flow Plugin pass all parent parameters

[James Nord (jnord)]

Hi Eric,

You can just pass a map and all the parameters of the flow are defined in a 
variable "params"
build(params, "jobname")

/James


> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Eric Engel
> Sent: 12 September 2014 10:53
> To: 'jenkinsci-users@googlegroups.com'
> Subject: Let Build Flow Plugin pass all parent parameters
> 
> Hello Jenkins Users,
> 
> I am using the Build Flow Plugin https://wiki.jenkins-
> ci.org/display/JENKINS/Build+Flow+Plugin and want to start a build using all
> paramters of the parent job stored at the pre-defined params variable.
> At the plugin page the following example for a single parameter is given:
> 
> build("job1", parent_param1: params["param1"])
> 
> what I want is kind of:
> 
> build("job1", $parameterName:params[$parameterName])
> 
> So that all values in params are passed to the new job. From the plugin
> description it is not clear if this can be done without explicitly writing 
> down all
> parameters. It would be great if this is possible, because there may be
> changes in parameters I do not want to adjust manually every time.
> 
> Regards,
> Eric
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

workflow scm step

[James Nord (jnord)]

Hi all,

I'm trying to get the new workflow to checkout from git with some additional 
behaviours (clone to specific dir)

Because of this the "git" step won't work - so I need to fall back to
scm $class: 'hudson.plugins.git.GitSCM' 
But the additional behaviours aren't defined in the top of the  block 
so I'm wondering how would I pass something like the following as a command.

  

  
ssh://foobar@whizbang/git/repo
  


  
*/master
  


  
  
myfunkydirectory
  

  

Anyone any suggestions?

/James

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

RE: Discard old builds - limit to snapshots?

[James Nord (jnord)]

Its part of the job configuration on the m2release plugin – I’m not sure about 
the release plugin – it may be it just always does it.

https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of James Green
Sent: 15 August 2014 12:20
To: jenkinsci-users@googlegroups.com
Subject: Re: Discard old builds - limit to snapshots?

I see a button on the per-build screen. However I'd like this configured within 
Jenkins as policy to help satisfy some auditing requirements. Is this doable or 
is this a an improvement to be logged?

On 15 August 2014 10:11, James Nord (jnord) 
mailto:jn...@cisco.com>> wrote:
HI James,

Both the m2release plugin and the release plugin have the ability to mark a 
release as keep forever – which will prevent it from being removed as part of 
the old build tidyup process.
If you are not using any of these then you always have the ability to do this 
manually or via an API call to jenkins as part of the build.

/James

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of James Green
Sent: 15 August 2014 09:20
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Discard old builds - limit to snapshots?

I'd really like to keep build history of releases but maintain only a limited 
set of snapshot history.

Is there a way to do this?

Thanks,

James

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

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

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

RE: Discard old builds - limit to snapshots?

[James Nord (jnord)]

HI James,

Both the m2release plugin and the release plugin have the ability to mark a 
release as keep forever – which will prevent it from being removed as part of 
the old build tidyup process.
If you are not using any of these then you always have the ability to do this 
manually or via an API call to jenkins as part of the build.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of James Green
Sent: 15 August 2014 09:20
To: jenkinsci-users@googlegroups.com
Subject: Discard old builds - limit to snapshots?

I'd really like to keep build history of releases but maintain only a limited 
set of snapshot history.

Is there a way to do this?

Thanks,

James

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

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

audit-trail - don;t log build cause?

[James Nord (jnord)]

Hi all,

I'm experimenting with the audit trail 
plugin but for 
the life of me I can't work out how to not get it to spam the logs with build 
started events.

The config (XML) is as follows

  
.*/(?:configSubmit|doDelete|cancelQueue|stop|toggleLogKeep|doWipeOutWorkspace|createItem|createView|toggleOffline)
  true
  

  /path/to/jenkins/data/logs/audit
  50
  2

  


Is there any way not to log build started events - or does this require a code 
change?

e.g. my output of /path/to/jenkins/data/logs/audit  is
Jul 3, 2014 4:14:38 PM job/foo/job/bar/job/commit/com.myco$my-app/ #57 Started
Jul 3, 2014 4:14:43 PM /view/All/createItem by builduser
Jul 3, 2014 4:14:47 PM job/foo/job/baz/job/baz-aat/job/commit/ #8 Started by an 
SCM change
Jul 3, 2014 4:14:49 PM /job/abc/configSubmit by builduser
Jul 3, 2014 4:15:07 PM job/foo/job/baz/job/baz-aat/job/commit/com.myco$baz-aat/ 
#8 Started
Jul 3, 2014 4:15:12 PM 
job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-validation/
 #201 Started
Jul 3, 2014 4:15:12 PM 
job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-transformer/
 #201 Started
Jul 3, 2014 4:15:12 PM 
job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-model/
 #201 Started
Jul 3, 2014 4:15:12 PM 
job/wibble/job/wibble-model/job/wibble-model/job/commit/com.myco.wibble.model$wibble-model-jms/
 #201 Started

But I just want
Jul 3, 2014 4:14:43 PM /view/All/createItem by builduser
Jul 3, 2014 4:14:49 PM /job/abc/configSubmit by builduser

/James

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

RE: Running test cases as different user in Jenkins

[James Nord (jnord)]

The slave(s) do not need to be launched from the same account that runs the 
slave.
You can run the master as j1,
Then create 2 ssh keys and put one as u1 and the other as u2.
Only give j1 the private key – then lauch the slaves as u1 and u2 from j1.
That way u1 has no access to u2 and u2 has no access to u1.
Does that no accomplish what you require?

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of varun srivastava
Sent: 03 July 2014 14:20
To: jenkinsci-users@googlegroups.com
Subject: Re: Running test cases as different user in Jenkins

My Jenkins instance is running as u1. Launching a slave as u2 might require 
some permission to u1. I can get only restricted set of permission for u1 to do 
anything as u2.

I launch my slave using following unix command
ssh hostname java -jar /data/jenkins/slave.jar

If u1 is granted permission to launch slave as u2 using above command, there is 
no restriction on what all commands can be launched on the slave which is not 
desirable.

On Thu, Jul 3, 2014 at 6:34 PM, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:
Maybe I stated poorly what I was suggesting.

Don't allow u1 to sudo to u2 and don't allow u2 to sudo to u1.  Create two 
separate jobs, one that runs as user u1 on the slave that is running as u1, and 
the other that runs as user u2 on the slave running as u2.  Use "copy 
artifacts" or a similar technique to copy from the u1 job to the u2 job so that 
the files in the u2 job will always be owned by user u2.

Mark Waite

On Thu, Jul 3, 2014 at 6:57 AM, varun srivastava 
mailto:varun.itbh...@gmail.com>> wrote:
Thanks Mark,

But running the slave node as u2 would mean that u1 can run any command as u2 
(equivalent to giving complete sudo permission for u2). I have restriction that 
u1 can sudo as u2 only for running test command/script.

On Thu, Jul 3, 2014 at 6:23 PM, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:
Could you change the requirements a little to simplify?

For example, what if you had a slave that was running as user "u2" and 
performed all its work as user "u2".  It could copy the build results from the 
job which had been performed as user "u1", then execute the tests as user "u2".

Mark Waite

On Thu, Jul 3, 2014 at 6:23 AM, varun srivastava 
mailto:varun.itbh...@gmail.com>> wrote:
Hi,

I have a centralized jenkins setup run as user u1. Different projects are set 
up on this instance. For running some testcases in some project, application 
user u2 permission is required. So I have granted permission to u1 to sudo as 
u2 only for running the test script/command. For example u1 can sudo -u u2 
run_test.sh
Now the problem is that the workspace is checked out as u1 but the test output 
files are generated with owner as u2. So I am not able to clean up the 
workspace as it contains files owned by both u1 and u2 and my cleanup plugin is 
run as u1.

Does any one has any solution for setting this up or do we have a plugin that 
can clean up the workspace as different user.

Summarizing the requirement :

1. Run jenkins as u1
2. Checkout and build project as u1.
3. Run test cases as u2. Note that u1 will have permission to sudo as u2 only 
for running restricted set of commands.
4. Able to clean up the workspace post build properly (that may contain files 
owned by both u1 and u2)

Thanks,
Varun

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Thanks!
Mark Waite
--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/mW2Dq0wbzWU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Thanks,

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



--
Thanks!
Mark Waite
--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/mW2Dq0wbzWU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com

RE: Call Perform Maven Release through REST API

[James Nord (jnord)]

You can’t automate a release via the m2release plugin via a REST like API.
You can do it using HTTP Post and curl – just have a look at the form befor you 
do a release and you should be able to craft a cURL request.

e.g.
releaseVersion=1.2.3
developmentVersion=1.2.4-SNAPSHOT

if you’re not sure of the data you need to supply – a wireshark capture of a 
test release is your friend.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Emmanuel POT
Sent: 28 May 2014 17:03
To: jenkinsci-users@googlegroups.com
Cc: m...@batmat.net
Subject: Re: Call Perform Maven Release through REST API

Hello,

Sorry I will try to be more specific. I want to use the Jenkins plugin Maven 
Release. It 
takes care of committing the correct version in the pom.xml before the release, 
with the possibility to tune the commit message...

I create a new Maven job, and activate the plugin for it. In the UI, it adds a 
new button on the left panel at job level "Perform Maven Release" that opens a 
new form in which I can precise a few things including the version. It is not a 
build parameter of the job that I could pass by calling the "classic" REST API. 
I wonder if this specific plugin can be called via the API, and if it is the 
case, how ?

Maybe the answer is not to use the Maven job configuration and the plugin 
above, and simply define shell steps with build parameters in a free-style 
project.

Cheers,
Emmanuel

On Wednesday, 28 May 2014 17:55:45 UTC+2, Baptiste Mathus wrote:

Well, you certainly want too give a wee bit more precision.

Trying to approximately answer your question though, one way to do it could be:
1) define a Jenkins job, and configure it so that the release works fine 
(define a parameter for that build)
2) through either jenkins-cli or the rest api, trigger the release build 
remotely, passing the required parameter you speak about.

Cheers
Le 28 mai 2014 09:31, "Emmanuel POT" > a écrit 
:
Hello,

I would like to perform a maven release using the maven release plugin 
remotely. Ideally, I would be able to pass as http parameters the version to 
use.

I googled for 30min but could not find a way to do that. Has anyone managed to 
do it ?

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

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

RE: Jetty or Winstone

[James Nord (jnord)]

Hi Drik,

To preserve backwards compatibility of command line arguments a shim was 
written to look like Winstone that maps arguments onto Jetty specifics.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dirk Heinrichs
Sent: 07 May 2014 08:08
To: jenkinsci-users@googlegroups.com
Subject: Jetty or Winstone

Hi,

I've just enabled access logging on a Jenkins 1.562 test installation, using 
Winstone command line options. I wonder why this can work since 
https://wiki.jenkins-ci.org/display/JENKINS/Jetty says "Jenkins 1.535 and above 
bundles Jetty (rather than Winstone)...".

Looking at jenkins.war, there's still a winstone.jar in there.

Bye...

Dirk
--
[cid:image001.gif@01CF69CF.89797960]
Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 159 (Ansage) 1149
Email: d...@recommind.com
Skype: dirk.heinrichs.recommind
www.recommind.com
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

RE: New build flow seems to break many things

[James Nord (jnord)]

You should be able to poll without a workspace with stash using the "fast 
remote polling" option of the git plugin.

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Greg Dickie
> Sent: 02 May 2014 12:51
> To: jenkinsci-users@googlegroups.com
> Subject: Re: New build flow seems to break many things
> 
> Post commit is nice but is not convenient for us as we have stash hosted in
> the cloud and jenkins behind the firewall (due to some specialized build
> slaves). We'd need to expose jenkins. Doable but should not be required
> IMHO.
> 
> We have a multi-stage build, some parallel stuff as well and build flow
> seemed like a great wrapper to encapsulate everything together.
> 
> I'm not sure about abusing the DSL, that seems more like a feature to me ;-)
> 
> Anyway thanks for the info. I appreciate the explanation.
> 
> Greg
> 
> On Fri, 2014-05-02 at 07:45 +0200, nicolas de loof wrote:
> > Issue with workspace is people are abusing the DSL and start to "code"
> > build custom steps into build flow, not delegating to jobs.
> > build flow was designed to orchestrate ("flow") jobs together. The
> > fact jenkins needs a workspace to poll scm is another story. I prefer
> > post-commit notification anyway
> >
> >
> > 2014-05-01 16:05 GMT+02:00 Greg Dickie :
> >
> >
> > Hi Nicolas,
> >
> >
> >I would like to understand the reason for that design.
> > Maybe I'm using it incorrectly but it was doing what we
> > needed. Why wouldn't you want SCM polling, artifacts, etc.? Is
> > the intention that we create build steps to handle that stuff
> > or is build flow not the right way to go for this?
> >
> >
> > Thanks,
> > Grg
> >
> >
> > On Thursday, May 1, 2014 1:42:11 AM UTC-4, Nicolas De loof
> > wrote:
> > yes, build-flow is desgined for orchestration, not as
> > a regular job with SCM workspace and all
> >
> >
> > that being said, as I can't find spare time to invest
> > on this plugin, feel free to take leadership on it and
> > make it evolve your way
> >
> >
> > 2014-05-01 0:13 GMT+02:00 Les Mikesell
> > :
> > On Wed, Apr 30, 2014 at 5:05 PM, Tim Jackson
> >  wrote:
> > > I agree that .11 is a huge step backwards
> > for me.  As far as I can tell, the
> > > build flow plugin no longer triggers the
> > failure event of the email-ext
> > > plugin.  So I am no longer getting failure
> > mails for the overall job.
> > > Setting up a new job to handle the failure
> > mail is redundant and can fail
> > > itself, thus changing the results.  I am
> > more apt to just dump the build
> > > flow plugin and find a more suitable method.
> > >
> > > It is very disappointing to have
> > functionality removed.  A lot of us have
> > > based large amounts of work on what it did.
> >
> >
> > I think the only way to make it do anything is
> > to set up one job that
> > just polls the SCM and triggers the build-flow
> > job, then pass all your
> > build parameters around to a final job
> > executed by the flow that uses
> > the copy artifacts plugin to gather up the
> > results of whatever the
> > other elements did.   Seems like a lot of
> > clutter and a confusing
> > process to have to start one job but end up
> > with the results in
> > another.
> >
> >
> > --
> >Les Mikesell
> >  lesmi...@gmail.com
> >
> > --
> > You received this message because you are
> > subscribed to the Google Groups "Jenkins
> > Users" group.
> >
> > To unsubscribe from this group and stop
> > receiving emails from it, send an email to
> > jenkinsci-use...@googlegroups.com.
> >
> > For more options, visit
> > https://groups.google.com/d/optout.
> >
> >
> >
> >
> >
> >
> --
> Greg Dickie
> 514-983-5400
> just a guy
> 
> --
> You received this message because you are subscribed to the

RE: New build flow seems to break many things

[James Nord (jnord)]

That sounds like an issue in the email-ext.  I get mails from the normal 
jenkins mailer.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Tim Jackson
Sent: 30 April 2014 23:05
To: jenkinsci-users@googlegroups.com
Subject: Re: New build flow seems to break many things

I agree that .11 is a huge step backwards for me.  As far as I can tell, the 
build flow plugin no longer triggers the failure event of the email-ext plugin. 
 So I am no longer getting failure mails for the overall job.  Setting up a new 
job to handle the failure mail is redundant and can fail itself, thus changing 
the results.  I am more apt to just dump the build flow plugin and find a more 
suitable method.

It is very disappointing to have functionality removed.  A lot of us have based 
large amounts of work on what it did.

- Tim

On Friday, April 18, 2014 10:13:26 AM UTC-6, Greg Dickie wrote:
Hi,

  We updated to the latest build flow without workspaces and all of the change 
reporting seems to have broken. In addition builds are no longer finding the 
latest git commit on branches. This is quite a setback for us. What was the 
rational for those changes and is there an alternative mechanism in the new 
plugin to get this functionality back?

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

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

RE: Trigger a job Y after an artifact from job X has been released?

[James Nord (jnord)]

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maciej Jaros
Sent: 14 April 2014 10:46
To: jenkinsci-users@googlegroups.com
Subject: Re: Trigger a job Y after an artifact from job X has been released?

dev123 (2014-04-09 22:06):
I have a few maven projects A, B and C on Jenkins. I have configured the 
maven-release-plugin for the projects so I can release them with a single click 
on the release button.

Now I have another project that picks up released artifacts, integrates them 
and runs a QA test. Currently I trigger this QA job manually.

Now I need to trigger this QA job automatically when either A, B or C is being 
released through Jenkins. I don't want to trigger the QA job each time a change 
is pushed to either A,B or C only when they have been released. Is that 
possible - to trigger a job Y if a job X has been released?

You can monitor the lastRelease permalink using the XTrigger plugins.

Regards,

/James

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

RE: Where did the "Append Jenkins Build Number" in the m2-release plugin go?

[James Nord (jnord)]

You could try setting the release version to “1.2.3-${BUILD_NUMBER}” – but I’m 
not expecting that it works – you may get lucky.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of dev123
Sent: 10 April 2014 12:54
To: jenkinsci-users@googlegroups.com
Subject: Where did the "Append Jenkins Build Number" in the m2-release plugin 
go?

Jenkins 1.558

I understand that "Append Jenkins Build Number" has been removed in the 
mvn-release plugin since it had no effect
https://issues.jenkins-ci.org/browse/JENKINS-20753

But it is possible to get this feature to work automatically work somehow 
anyway?


Before:


[https://lh5.googleusercontent.com/-2uDE5QlvPBQ/U0Z5nZL5l7I/ABQ/KvmBqWrxcwc/s320/mvn-rel.png]
After:


[https://lh3.googleusercontent.com/-ZHQYTmnmXNA/U0Z-PXKvvwI/ABc/8YXDKCgYxiI/s320/mvn-rel222.png]

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

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

RE: buildflow hang when cancelling queued builds

[James Nord (jnord)]

I Changed the handling of cancel since the last release - so that it actually 
kills the downstream projects as well (including those in the queue).
Given that there is a good chance that this is fixed - if you feel brave and 
want to try a snapshot.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Marc MacIntyre
Sent: 03 April 2014 23:21
To: jenkinsci-users@googlegroups.com
Subject: buildflow hang when cancelling queued builds

I've noticed with the buildflow plugin, when I run parallel jobs and cancel one 
of the runs of a job while it is still in the queue, the build flow never 
completes.

To illustrate - assume that job1 won't run concurrently:

   parallel(
{build(job1)},
{build(job1)},
   )

if the 2nd run of job1 is aborted while still in the queue, the build flow will 
never complete - it will schedule both jobs, and finish the first one, but 
never realize the 2nd one has been cancelled.

Anyone seen this?  Am I missing something?

On a related note; anyone have a good way to time out a build flow job?

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

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

RE: Quoting of parameters: Gerrit Event Stream => Build Parameter => ANT Call

[James Nord (jnord)]

I should have said there is a “Escape quotes in parameter values” in the 
advanced section of the Trigger,

However this is only guaranteed to cause you pain.

That is you can disable it to fix your current issue – however if someone 
checks in code with commit message containing a quote (single double…)– it may 
well cause the build to fail again…

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of James Nord (jnord)
Sent: 31 March 2014 14:23
To: jenkinsci-users@googlegroups.com
Subject: RE: Quoting of parameters: Gerrit Event Stream => Build Parameter => 
ANT Call

Hi Ralf/Dermagg?

There are unfortunately a few different issues all around quoting (that effect 
different platforms differently) and to my knowledge there is not a good cross 
platform way to escape quotes.

https://issues.jenkins-ci.org/browse/JENKINS-20808
https://issues.jenkins-ci.org/browse/JENKINS-16211
https://issues.jenkins-ci.org/browse/JENKINS-15074
https://issues.jenkins-ci.org/browse/JENKINS-11779
https://issues.jenkins-ci.org/browse/JENKINS-10984
https://issues.jenkins-ci.org/browse/JENKINS-10440

Depending on your needs – I may guess that a generic solution to 
https://issues.jenkins-ci.org/browse/JENKINS-10692 would provide you with a 
working option – but so far as I can tell attempts to fix the errors have just 
moved the error somewhere else.

The other issue with quoting is you may well be calling a batch file (in this 
case ant.bat) who may then blindly attempt to quote arguments in order to be 
safe – which then breaks as things are already correctly quoted ☹

/James



From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dermagg B. Magnusson
Sent: 31 March 2014 14:14
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Quoting of parameters: Gerrit Event Stream => Build Parameter => ANT 
Call

Hello,

hope someone can give some hints to the following problem:

I have Jenkins Gerrit Trigger Plugin setup to listen to the Gerrit Event Stream.

Jenkins: Jenkins ver. 1.509.4
Gerrit Trigger: 2.11.1
Running on Windows Server 2008 R2, 64 Bit


Some parameter include the mail address of the commiting user. This address, in 
the build parameters looks like this:

GERRIT_CHANGE_OWNER:   \"Lastname, Firstname\" 
mailto:firstname.lastn...@somedomain.tld>>

So when it comes to call ANT it look like this:


$ cmd.exe /C '""c:\Program Files\Apache\apache-ant-1.9.2\bin\ant.bat" ... 
"-DGERRIT_PATCHSET_UPLOADER=\""Lastname, Firstname\"" 
mailto:firstname.lastn...@somedomain.tdl>>" 
... "'

Here the relevant part (extra "" have been added):

"
-DGERRIT_PATCHSET_UPLOADER=
\"
"
Lastname, Firstname
\"
"
mailto:firstname.lastn...@somedomain.tdl>>
"
Outcome: quoting is broken, lastname (in bold letters) becomes the first 
non-paramter string in the ANT call and by this gets interpreted as build 
target.

So, would be great to get some answers/ideas!

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

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

RE: Quoting of parameters: Gerrit Event Stream => Build Parameter => ANT Call

[James Nord (jnord)]

Hi Ralf/Dermagg?

There are unfortunately a few different issues all around quoting (that effect 
different platforms differently) and to my knowledge there is not a good cross 
platform way to escape quotes.

https://issues.jenkins-ci.org/browse/JENKINS-20808
https://issues.jenkins-ci.org/browse/JENKINS-16211
https://issues.jenkins-ci.org/browse/JENKINS-15074
https://issues.jenkins-ci.org/browse/JENKINS-11779
https://issues.jenkins-ci.org/browse/JENKINS-10984
https://issues.jenkins-ci.org/browse/JENKINS-10440

Depending on your needs – I may guess that a generic solution to 
https://issues.jenkins-ci.org/browse/JENKINS-10692 would provide you with a 
working option – but so far as I can tell attempts to fix the errors have just 
moved the error somewhere else.

The other issue with quoting is you may well be calling a batch file (in this 
case ant.bat) who may then blindly attempt to quote arguments in order to be 
safe – which then breaks as things are already correctly quoted ☹

/James



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dermagg B. Magnusson
Sent: 31 March 2014 14:14
To: jenkinsci-users@googlegroups.com
Subject: Quoting of parameters: Gerrit Event Stream => Build Parameter => ANT 
Call

Hello,

hope someone can give some hints to the following problem:

I have Jenkins Gerrit Trigger Plugin setup to listen to the Gerrit Event Stream.

Jenkins: Jenkins ver. 1.509.4
Gerrit Trigger: 2.11.1
Running on Windows Server 2008 R2, 64 Bit


Some parameter include the mail address of the commiting user. This address, in 
the build parameters looks like this:

GERRIT_CHANGE_OWNER:   \"Lastname, Firstname\" 
mailto:firstname.lastn...@somedomain.tld>>

So when it comes to call ANT it look like this:


$ cmd.exe /C '""c:\Program Files\Apache\apache-ant-1.9.2\bin\ant.bat" ... 
"-DGERRIT_PATCHSET_UPLOADER=\""Lastname, Firstname\"" 
mailto:firstname.lastn...@somedomain.tdl>>" 
... "'

Here the relevant part (extra "" have been added):

"
-DGERRIT_PATCHSET_UPLOADER=
\"
"
Lastname, Firstname
\"
"
mailto:firstname.lastn...@somedomain.tdl>>
"
Outcome: quoting is broken, lastname (in bold letters) becomes the first 
non-paramter string in the ANT call and by this gets interpreted as build 
target.

So, would be great to get some answers/ideas!

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

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

RE: Downstream cleanup job

[James Nord (jnord)]

You can use build flow extensions plugin to block[1] the flows.

/James

[1] 
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Extensions+Plugin#BuildFlowExtensionsPlugin-block

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Curtis Kline
Sent: 26 March 2014 23:31
To: jenkinsci-users@googlegroups.com
Subject: Downstream cleanup job

I have a scenario that seems like it would be pretty common, and is maybe 
somewhat similar to the one David Campos posted to the list recently.

b1, b2, and b3 are QA testing jobs that each rely on a “clean” VM. b4 is the 
job that cleans the VMs.

For awhile, we had b4 set up as a downstream job from each of b1, b2, and b3. 
However sometimes one of the testing jobs would get queued up while another 
testing job was being run, and would end up running before the cleanup job. 
That breaks everything.

Next we tried using the Throttle Concurrent builds plugin, and put all four of 
the above jobs into one group with a max concurrent of 1. We had the same 
problem as before, in that if a testing job was queued while another testing 
job was running, the cleanup job would run too late.

Next we tried three Build Flow jobs, with the Guard - Rescue form. Each testing 
job would be in the Guard section, and the cleanup job in the Rescue section. 
We put all three of the Build Flow jobs in one group for Throttle Concurrent 
Builds. However we immediately found that multiple build flow jobs would run at 
the same time, as it seems that Build Flow jobs ignore the Throttle Concurrent 
Builds plugin.

Any suggestions here?  We just need the cleanup job to always run after a 
testing job, so the VMs are fresh before the next testing job runs. I am 
probably missing something simple.

Thanks!
Curtis


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

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

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

[James Nord (jnord)]

Attempting to do this is a bad idea for the future.

The workspace does not exist in the latest version of the plugin (and having it 
allowed people to abuse its functionality from being an orchestrator.)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of slopes...@gmail.com
Sent: 20 March 2014 17:00
To: jenkinsci-users@googlegroups.com
Subject: Re: Cannot write file to disk using the build Flow plugin

I can write to a file successfully by adding the Jenkins workspace to the path. 
try something like this:

workspace = build.environment.get("WORKSPACE");
new File("${workspace}/foo.ini").withWriter { out ->
out.writeLine("this is a test")
}


On Tuesday, March 4, 2014 3:59:29 AM UTC-8, dev123 wrote:
I have a build flow job where the first step I need to execute is writing a 
file to disk:


Properties props = new Properties();
props.setProperty("Var1", "asdasd");
File f = new File("Configs.properties");
OutputStream out = new FileOutputStream( f );
props.store(out,null);

When I run the job I get:


Building in workspace /var/lib/jenkins/workspace/test-flow

ERROR: Failed to run DSL Script

java.io.FileNotFoundException:
 Configs.properties (Permission denied)

at java.io.FileOutputStream.open(Native Method)

at java.io.FileOutputStream.(FileOutputStream.java:209)

at java.io.FileOutputStream.(FileOutputStream.java:160)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:532)

at 
org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:77)

at 
org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:102)

at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:54)

at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:182)

at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:190)

at Script1.run(Script1.groovy:4)

at Script1$run.call(Unknown Source)

at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)

at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)

at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)

at 
com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:82)

at com.cloudbees.plugins.flow.FlowRun$RunnerImpl.doRun(FlowRun.java:154)

at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566)

at hudson.model.Run.execute(Run.java:1678)

at hudson.model.Run.run(Run.java:1625)

at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:133)

at hudson.model.ResourceController.execute(ResourceController.java:88)

at hudson.model.Executor.run(Executor.java:231)

at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43)

FATAL: Configs.properties (Permission denied)

java.io.FileNotFoundException:
 Configs.properties (Permission denied)



Why does jenkins not have rights to write a file to the workspace where its 
executing the job?
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

RE: Is it possible to have non editable execute shell for users?

[James Nord (jnord)]

I also pointed out to CB that what I really wanted was to be able to apply 
parameters specified in the SCM to a template (via literate builds).

So instead of

Environment
==

· jdk1.6.0_64, RedHat_6
Build


* mvn random command.

I would like a way in source to describe the CB template I want and its 
parameters
Template
===
* Standard Code review build
* Standard Commit build
* Standard Documentation build
Parameters
=
* Java:jdk1.6.0_64
* Label:RedHat_6

Now in reality I would also like to go one step further – and be able to assume 
the template (or at least set it in a the literate job)

e.g.
Parameters
=
* Java:jdk1.6.0_64
* Label:RedHat_6
* email: devteam...@example.com


Such that I have a foobar_commit job (using the “commit” template) – that takes 
the parameters for the template from the parameters in the source code, a 
foobar_doc (suing the “documentation” template) etc etc..
Any values not specified optionally would fail the build, or use defaults.

It sounds like I am not quite alone in this request – although Stephen will 
probably shoot me when I mention the maven project type (or its new 
replacement)…

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Christian Willman
Sent: 11 March 2014 15:52
To: jenkinsci-users@googlegroups.com
Subject: Re: Is it possible to have non editable execute shell for users?

Stephen,

I'm really interested in the Literate plugin! Like I mentioned to you and Jesse 
before (through Cloudbees support vis-a-vis my work), it's futile for us unless 
we can keep devs from creating FreestyleBuilds.

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

RE: Doesn't poll for subversion changes when set to H * * * * or H/1 * * * * but polls fine with * * * * * and H/2 * * * * !?

[James Nord (jnord)]

Obligatory link to polling is evil.

http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 11 March 2014 14:36
To: jenkinsci-users@googlegroups.com
Subject: Re: Doesn't poll for subversion changes when set to H * * * * or H/1 * 
* * * but polls fine with * * * * * and H/2 * * * * !?

If you have enough jobs it's an option on the main jenkins configuration page 
(I forget the exact name or the number of jobs to get the option to display)

On 11 March 2014 14:32, mailto:k...@quipsy.de>> wrote:
Sounds interesting. How to do that?

Am Dienstag, 11. März 2014 13:25:04 UTC+1 schrieb Stephen Connolly:
just limit concurrent polling and they'll form a queue

On 11 March 2014 12:18, mailto:ka...@quipsy.de>> wrote:
Actually what I want is "once a minute, but not exactly at second number zero", 
as I have lots of SVN jobs and want to spread these evenly of the current 
minute.

Am Dienstag, 11. März 2014 13:13:17 UTC+1 schrieb Stephen Connolly:
It's a hacky syntax...

H * * * * can only sensibly mean once per hour as if you want every minute you 
just type * * * * *

The /n formats are a different set of logic

On 11 March 2014 11:52, mailto:ka...@quipsy.de>> wrote:
Understood. But why is H/2 working, while H/1 is not?

Am Dienstag, 11. März 2014 12:29:27 UTC+1 schrieb Stephen Connolly:
AFAIK `H * * * *` means poll once per hour at a random minute in the hour

On 11 March 2014 11:25, mailto:ka...@quipsy.de>> wrote:
I have enabled a Jenkins job to poll for subversion changes every minute (H * * 
* * or H/1 * * * *).
When I check the last poll status, it says last poll was an hour ago! So it 
does not poll every minute, aparently, using H * * * * or H/1 * * * *!
The Jenkins log file does not contain any particularly interesting SCM news.
When I set the frequency to * * * * * or H/2 * * * * instead of H * * * * then 
it polls correctly!
So what is wrong here whith the "H"?
(Jenkins LTS 1.532.2)
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-use...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

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

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

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

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

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

RE: maven job parallel on slaves

[James Nord (jnord)]

Hi,

Take a look at 
https://wiki.jenkins-ci.org/display/JENKINS/Parallel+Test+Executor+Plugin that 
may help.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Hodeffi
Sent: 10 March 2014 14:48
To: jenkinsci-users@googlegroups.com
Subject: maven job parallel on slaves

HI all
I have read this question 
:https://groups.google.com/forum/#!searchin/jenkinsci-users/Maven$20Job$20on$20multiple$20nodes/jenkinsci-users/CigQHchfV1k/i0SbpWYfnhsJ
does some on know how can i make multi configuration combined with maven job?
Is there any way to run a job twice parallel?what does it mean #number of 
executores?
I really dont want to create two jobs that will use the same pom .
my motivation is running integration test on 2 slaves parallel using same 
pom.xml  file , so i will have less configuration on jenkins.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

RE: Is it possible to have non editable execute shell for users?

[James Nord (jnord)]

I don't want to allow concurrent builds as that would swamp the hardware - 
running code coverage and full site builds can take hours, wheras a simple unit 
test takes 20 minutes.

I originally thought I couldn't get multiple different builds with literate - 
but I forgot I can change the name of the "README.md" file and could have 2 
litterate jobs for each SCM. (although the linking of them then requires manual 
intervention (unless I have missed something else...)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 10 March 2014 14:21
To: jenkinsci-users@googlegroups.com
Subject: Re: Is it possible to have non editable execute shell for users?



On 10 March 2014 14:19, Stephen Connolly 
mailto:stephen.alan.conno...@gmail.com>> wrote:
At present it is manual trigger only. I am looking into adding a "automatic" 
trigger which will trigger if the build succeeds and a "named promotions" 
trigger which will trigger if the named promotion succeeds... the last one 
might be a join style trigger or an any style trigger or configurable as either.

If you allow concurrent builds in a specific branch (not sure if I exposed that 
yet) then you'd not be blocked by subsequent commits. In any case, lightweight 
promotions

not lightweight promotions, more the new SCM API that multibranch uses and 
hence I can expose to lightweight promotions in literate

have the advantage that they ensure you are running in the GIT Hash of the 
original build... and by default any archived artifacts have been put back 
where they were found!

On 10 March 2014 14:06, James Nord (jnord) 
mailto:jn...@cisco.com>> wrote:
Hi Stephen,

Is there any documentation (other than source) on the lightweight promotions - 
my google karma is letting me down.

I'm wondering if it can solve the use case where you want to run one set of 
commands first, then a different set of commands only if the first set passed 
and  you want to be able to coalesce the run of the second set of commands such 
that you don't want to block another commit.
ie. the "old style" analogy would be JobA (trigger on commit) -> JobB (trigger 
on JobA success) - where both use the same SCM.

/James



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: 10 March 2014 12:55
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: Is it possible to have non editable execute shell for users?

I added the lightweight promotions support last month: 
https://github.com/jenkinsci/literate-plugin/commits/master  but the next set 
of things are stuff that happens in other plugins... so in a sense some of that 
is not visible until I think it is ready to show ;-)

On 10 March 2014 12:46, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:
Knowing that your time is limited on literate is actually a comfort.  I read 
your earlier blog entry and thought it was a great idea, but then didn't see 
any further progress so I worried that the idea had died quietly.  If it is 
still your vision but with limited time, then I'll explore and report what I 
find.

On Mon, Mar 10, 2014 at 6:42 AM, Stephen Connolly 
mailto:stephen.alan.conno...@gmail.com>> wrote:
JIRA. That way others can help try and fix. My time on literate is limited 
right now too though... so that is an issue.

Glad you like my vision!

On 10 March 2014 12:33, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:
That is a great vision.  I'd like to help the vision with some testing and can 
provide you some feedback.  How would you prefer the feedback?  I can submit 
bug reports through JIRA, or send mail to the list, or some other technique.

Testing time is limited, and must be squeezed around my real job and my family, 
but I'm sure I can provide some testing and some feedback if there are 
indications they will be helpful to your efforts.

Mark Waite

On Mon, Mar 10, 2014 at 6:28 AM, Stephen Connolly 
mailto:stephen.alan.conno...@gmail.com>> wrote:
I will give you my vision.

In my vision there are two types of things:

1. Things that depend on the stuff in a build job itself
2. Things that depend on the inter-relationship of jobs within a CI server.

Traditionally, Jenkins takes the view that there is just one type of thing. So 
you end up configuring everything in the Jenkins job (or you use the evil 
one<http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html>
 and have slightly less to configure)

This leads people to want to lock down access to some portions of the 
configuration... in a sense you need to let some people tweak the first type of 
things (because they are changing the code b

RE: Is it possible to have non editable execute shell for users?

[James Nord (jnord)]

Hi Stephen,

Is there any documentation (other than source) on the lightweight promotions - 
my google karma is letting me down.

I'm wondering if it can solve the use case where you want to run one set of 
commands first, then a different set of commands only if the first set passed 
and  you want to be able to coalesce the run of the second set of commands such 
that you don't want to block another commit.
ie. the "old style" analogy would be JobA (trigger on commit) -> JobB (trigger 
on JobA success) - where both use the same SCM.

/James



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 10 March 2014 12:55
To: jenkinsci-users@googlegroups.com
Subject: Re: Is it possible to have non editable execute shell for users?

I added the lightweight promotions support last month: 
https://github.com/jenkinsci/literate-plugin/commits/master  but the next set 
of things are stuff that happens in other plugins... so in a sense some of that 
is not visible until I think it is ready to show ;-)

On 10 March 2014 12:46, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:
Knowing that your time is limited on literate is actually a comfort.  I read 
your earlier blog entry and thought it was a great idea, but then didn't see 
any further progress so I worried that the idea had died quietly.  If it is 
still your vision but with limited time, then I'll explore and report what I 
find.

On Mon, Mar 10, 2014 at 6:42 AM, Stephen Connolly 
mailto:stephen.alan.conno...@gmail.com>> wrote:
JIRA. That way others can help try and fix. My time on literate is limited 
right now too though... so that is an issue.

Glad you like my vision!

On 10 March 2014 12:33, Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:
That is a great vision.  I'd like to help the vision with some testing and can 
provide you some feedback.  How would you prefer the feedback?  I can submit 
bug reports through JIRA, or send mail to the list, or some other technique.

Testing time is limited, and must be squeezed around my real job and my family, 
but I'm sure I can provide some testing and some feedback if there are 
indications they will be helpful to your efforts.

Mark Waite

On Mon, Mar 10, 2014 at 6:28 AM, Stephen Connolly 
mailto:stephen.alan.conno...@gmail.com>> wrote:
I will give you my vision.

In my vision there are two types of things:

1. Things that depend on the stuff in a build job itself
2. Things that depend on the inter-relationship of jobs within a CI server.

Traditionally, Jenkins takes the view that there is just one type of thing. So 
you end up configuring everything in the Jenkins job (or you use the evil 
one
 and have slightly less to configure)

This leads people to want to lock down access to some portions of the 
configuration... in a sense you need to let some people tweak the first type of 
things (because they are changing the code being built and thus may break the 
instructions as to how to build it) but you don't want to let them tweak the 
second type of things (e.g. how the built application gets put into the staging 
environment and which job(s) to trigger so that the pre-production tests run 
against the staging environment)

The folly people then run down is trying to get a division of permission scopes.

There is, however, a split... if you let people commit to source control, then 
in reality you let them change the build script that lives in source control 
(unless you are using SVN and lock the build script down with permissions... 
but at some point a refactoring needs a tweak to the build script and giving 
developers a world of pain to make those changes only pisses them off)... or 
they write a unit test that does the changes on the fly as a hack around the 
fact you haven't given them the ability to tweak the build script... so now 
your build script is part build script part unit test hacks that "fix" the 
build script.

So the simple fact is that however you set up your build script, you have to 
accept that developers will be able to change the build script. This probably 
means that you have code review for changes to the build script... not that the 
devs are making malicious changes... more that they are making appropriate 
changes.

In my view a CI build job should not need configuration changes to reflect a 
change in the build script... the CI job should be able to pick up the 
configuration relevant to the build script from the source tree itself... hence 
the literate job type.

This unlocks a lot of great power... tracking multiple branches is now trivial, 
as each branch stores the detail of how that branches version of the build 
script should be interpreted...

All the Type 1 things are configuration that naturally should sit within source 
control. People who can change the build script can then change the 
corresponding jenkins co

RE: Maven Release Plugin throws Authentication Required error

[James Nord (jnord)]

Hi Vijay,

Try setting the username and password in the release options - or make sure you 
run subversion client on your slave and get it to store the subversion 
credentials in its cache.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of D Vijay
Sent: 04 March 2014 08:36
To: jenkinsci-users@googlegroups.com
Subject: Re: Maven Release Plugin throws Authentication Required error

Hi,
The issue is with configuring the M2Release plugin in Jenkins. I wanted some 
help in configuring this plugin in Jenkins like the steps that we need to 
follow.
Vijay

On Mon, Mar 3, 2014 at 9:28 PM, Baptiste Mathus 
mailto:bmat...@batmat.net>> wrote:

Hi,
Imo wrong mailing list. This is a pure maven question. Better ask it on maven 
users.
Cheers
Le 3 mars 2014 12:06, "D Vijay" 
mailto:vijayd1...@gmail.com>> a écrit :

Dear All,



I need help in configuring the Maven Release plugin. I am trying to configure 
the plugin in Jenkins job. I am getting authentication exception. For invoking 
maven release plugin do we need to have svn client from where we are invoking 
the release? PFA the errors & the configuration that I used for this. The 
requirement is as follows:

My requirement is to configure maven release plugin as follows:

1. My current version is at 1.0.0-SNAPSHOT and once testing is done and ready 
for movement to production the maven release plugin will be invoked from 
Jenkins job to move the code from branch to trunk.
2. The configuration has to check out the source from branch, update all the 
POMs to version 1.0.0, tag the source code and check in the code at trunk 
location. The tags folder will contain the tagged version at 1.0.0 (as best 
practice we need to change the version from 1.0.0-SNAPSHOT to 1.0.0 once the 
product is ready for production, right? or while moving to UAT itself it should 
be done?).
3. Also, the next snapshot version will be updated to 1.0.1-SNAPSHOT(which is 
configurable in release plugin) and checked in at branch level for the next 
development.

I am able to configure this, but somehow it is not working. I am getting 
authentication exception.
svn: Authentication required for 
'>'.



Thank you,

Vijay.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/wA80C4CgMtc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

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

RE: Number of users hitting jenkins?

[James Nord (jnord)]

The monitoring plugin will give you this information

https://wiki.jenkins-ci.org/display/JENKINS/Monitoring

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Richard Bywater
Sent: 26 February 2014 00:34
To: jenkinsci-users@googlegroups.com
Subject: Re: Number of users hitting jenkins?

If you fronted it with Apache or similar web server then you could just use 
(e.g.) awstats to get the info.

Not sure if there's something similar for embedded mode.

Richard.

On Wed, Feb 26, 2014 at 10:02 AM, Bob Hansen 
mailto:hansen...@gmail.com>> wrote:
Is there a plugin that generates statics on the number of hits there are a 
jenkin installation?

Trying to determine how many different hits there on my site, to determine 
usage (everyone uses the anonymous support).

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

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

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

RE: Howto : Jenkins executable WAR and rotating log files

[James Nord (jnord)]

For log rotation you have a few options

Option 1
Use logrotoate.

[foo@host ~]# cat /etc/logrotate.d/jenkins
/opt/jenkins/logs/jenkins.log /opt/jenkins/logs/access_log {
compress
dateext
maxage 365
rotate 99
size=+4096k
notifempty
missingok
create 644
postrotate
if [ -s /var/run/jenkins.pid ]; then
JPID=`cat /var/run/jenkins.pid`
test -n "`find /proc/$JPID -maxdepth 0 -user jenkins 2>/dev/null`" 
&& kill -s ALRM $JPID || :
fi
endscript
}

Option 2
onfigure java logging (pass 
-Djava.util.logging.config.file=/opt/jenkins/logging.properties to the JVM) and 
specify the configurationtion and implementation to do rollover/deletion.


For your second question – confluence has markedup the double dash -- as a 
strikethrough command (and it should be makred as nomarkup in the wiki).

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of hanasaki-jenkins
Sent: 26 February 2014 08:13
To: jenkinsci-users@googlegroups.com
Subject: Howto : Jenkins executable WAR and rotating log files

Q: How can the Jenkins self executable be configured to rotate log files 
automatically?
It is running from a linux bash script with the "-logfile=" option as in the 
below referenced link.

Q: Why is the line half covered in a "strike through"? (below referenced link)

reference: 
https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

RE: best approach to automate/manage jenkins jobs?

[James Nord (jnord)]

Finger slipped - this time with some links.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin
[2] 
http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-features-templates-plugin.cb

From: James Nord (jnord)
Sent: 21 February 2014 16:20
To: jenkinsci-users
Subject: RE: best approach to automate/manage jenkins jobs?

Hi Phil,

There is also the Job DSL plugin[1] and Cloudbees Templates[2].
The DSL plugin (not used it) can store the DSL in source control - you can add 
the Cloudbees templates (done it) to an SCM like git and commit & push them 
after you make any changes.

/James

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of phil swenson
Sent: 21 February 2014 15:15
To: jenkinsci-users
Subject: best approach to automate/manage jenkins jobs?

Hi, we have a large number of jenkins jobs and would like to automate and 
version control their configuration.

>From what I can tell, most people just manually config their jobs via the UI.  
>Unless there are only a few very simple jobs, this leads to an unmanageable 
>mess.

I think the jobs should be coded in a DRY fashion, version controlled, and 
deployed via a scripted system.

Here are the approaches I am aware of:

1) scripting via command line (jenkins cli)
2) scripting via the rest web services
3) chef cookbook http://community.opscode.com/cookbooks/jenkins

What are most people doing?
Any recommendations?

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

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

RE: best approach to automate/manage jenkins jobs?

[James Nord (jnord)]

Hi Phil,

There is also the Job DSL plugin[1] and Cloudbees Templates[2].
The DSL plugin (not used it) can store the DSL in source control - you can add 
the Cloudbees templates (done it) to an SCM like git and commit & push them 
after you make any changes.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of phil swenson
Sent: 21 February 2014 15:15
To: jenkinsci-users
Subject: best approach to automate/manage jenkins jobs?

Hi, we have a large number of jenkins jobs and would like to automate and 
version control their configuration.

>From what I can tell, most people just manually config their jobs via the UI.  
>Unless there are only a few very simple jobs, this leads to an unmanageable 
>mess.

I think the jobs should be coded in a DRY fashion, version controlled, and 
deployed via a scripted system.

Here are the approaches I am aware of:

1) scripting via command line (jenkins cli)
2) scripting via the rest web services
3) chef cookbook http://community.opscode.com/cookbooks/jenkins

What are most people doing?
Any recommendations?

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

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

RE: Git Plugin: "Clean after checkout" exclusions?

[James Nord (jnord)]

You can't clean in the maven pom - as the maven pom is what will use what you 
are trying to clean :-o

However - even if Max could selectively clean the repo I don't think it would 
scale.

With Gerrit - you can end up with many changes submitted at the same time - and 
you don't want to run them serially (feedback loop is too long).
As such you need multiple workspaces - and you need multiple executors as well.
As no one writes well behaved unit tests the best practice is to use 1 executor 
per slave.  At this point the likely hood of getting a slave that has the 
workspace that Jenkins wants is possibly slim.

So even if you could - you may end up getting wildly different build times in 
various cases.
There is likely more to be gained (long term) from using shallow clones and 
reference repositories.

If you have a good maven chache close to you build server - the time to 
download isn't the dominating factor anymore (and downloads can be performed in 
parallel, and modules can be built in parallel with Maven3 - so the download 
time end up not blocking/contributing to the build time by any significant 
amount)

What possibly would help is layered local maven repository support (something 
that Jason has mooted several times on the Maven lists) - but nothing is 
available yet.  (but that then assumes that all projects use the same maven 
settings (for all mirrors and have a mirror of * fallback).

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: 13 February 2014 23:53
To: jenkinsci-users@googlegroups.com
Subject: Re: Git Plugin: "Clean after checkout" exclusions?

If the "Clean after checkout" option you are referencing is the option from the 
git plugin, then I would rather suggest that you should adapt and maintain some 
form of build specific clean within your maven pom.xml, rather than 
complicating the git plugin with inclusions and exclusions for the operation.

The "Clean after checkout" option in the git plugin is conceptually mapped to 
"git clean -xfd".  Your exclusion / inclusion proposal has no matching concept 
in the git command line nor in JGit.  I'd rather not see the git plugin stray 
from its conceptual mapping to git commands.  It is complicated enough already.

Mark Waite

On Thu, Feb 13, 2014 at 4:34 PM, Max Spring 
mailto:m2spr...@springdot.org>> wrote:
I'm using the "Clean after checkout" option a lot with my Gerrit verification 
Maven jobs.
I also have these jobs use a local repository, sitting in the job's workspace.

Because of the "Clean after checkout" option set, the job's local repository 
gets wiped and
the subsequent build has to time-consumingly repopulate it with lots of 
artifacts.

I'd like to speed this up.

Ideally, I'd like to exclude certain directories/files from being removed when 
using the "Clean after checkout" option is set.
Sort of: "exclude=$WORKSPACE/.repository"

In addition to an exclude option for "Clean after checkout",
I would like to have an include option, where I would then specify
certain hierarchies within the private local repository to be cleaned,
like "include=$WORKSPACE/.repository/org/myorg/".

-Max

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



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

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

RE: Failed to parse Cucumber JSON with Cucumber json test reporting plugin

[James Nord (jnord)]

Hi Josh,

There’s no results at all in that json file – so the plugin won’t know if it 
ran ok or failed.

I would ask on the cucumber mailing list why the ruby implantation is missing 
this vital information (unless I am missing something..)

/James





From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Josh Lesch
Sent: 13 February 2014 14:25
To: jenkinsci-users@googlegroups.com
Subject: Re: Failed to parse Cucumber JSON with Cucumber json test reporting 
plugin

I am using the cucumber ruby implementation and its version 1.3.10. I am using 
an Scenario Outline with Examples. I am trying to switch to this reporting 
plugin because the other Cucumber Reports plugin can't handle Scenario Outlines 
right and always fails the build.

Scenario Outline: Verify the footer links that open in a new modal
Given I am on website
When I click on the "" link in the footer
Then I should see a modal pop up

  Examples:
|Footer Links |
|Sign In  |
|Create an Account|
|Free Shipping |

[
  {
"keyword": "Feature",
"name": "Footer",
"line": 1,
"description": "\nAs a customer\nI want to test the footer 
functionality\nSo I can verify that everything is working as expected",
"id": "footer",
"uri": "features\\footer.feature",
"elements": [
  {
"keyword": "Scenario Outline",
"name": "Verify the footer links that open in a new modal",
"line": 59,
"description": "",
"id": "footer;verify-the-footer-links-that-open-in-a-new-modal",
"type": "scenario_outline",
"steps": [
  {
"keyword": "Given ",
"name": "I am on website",
"line": 60,
"match": {
  "location": "features/step_definitions/account.rb:7"
}
  },
  {
"keyword": "When ",
"name": "I click on the \"\" link in the footer",
"line": 61,
"match": {
  "arguments": [
{
  "offset": 16,
  "val": "Sign In"
}
  ],
  "location": "features/step_definitions/footer.rb:1"
}
  },
  {
"keyword": "Then ",
"name": "I should see a modal pop up",
"line": 62,
"match": {
  "location": "features/step_definitions/footer.rb:30"
}
  }
],
"examples": [
  {
"keyword": "Examples",
"name": "",
"line": 64,
"description": "",
"id": "footer;verify-the-footer-links-that-open-in-a-new-modal;",
"rows": [
  {
"cells": [
  "Footer Links"
],
"line": 65,
"id": 
"footer;verify-the-footer-links-that-open-in-a-new-modal;;1"
  },
  {
"cells": [
  "Sign In"
],
"line": 66,
"id": 
"footer;verify-the-footer-links-that-open-in-a-new-modal;;2"
  },
  {
"cells": [
  "Create an Account"
],
"line": 67,
"id": 
"footer;verify-the-footer-links-that-open-in-a-new-modal;;3"
  },
  {
"cells": [
  "Free Shipping"
],
"line": 68,
"id": 
"footer;verify-the-footer-links-that-open-in-a-new-modal;;4"
  }
]
  }
]
  }
]
  }
]

On Wednesday, February 12, 2014 5:14:34 PM UTC-6, teilo wrote:
Which cucumber implementation (eg cucumber-jvm) and version are you running the 
tests with?
Can you put the offending Jason online somewhere?

It sounds like you have a step that is missing a resuilt , they should all have 
even if the step not run.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

RE: Git plugin 2.0 with Gerrit Trigger plugin

[James Nord (jnord)]

Do you use a clean workspace each time (requiring a clone rather than fetch)?
I found a non-clean workspace + fetch worked – but clean workspace + clone 
failed.
This however have been fixed in 2.0.1


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Robert Sandell
Sent: 12 February 2014 16:00
To: jenkinsci-users@googlegroups.com
Subject: Re: Git plugin 2.0 with Gerrit Trigger plugin

I have it working on both of my test servers, but haven't upgraded in the 
production environment yet.
The only previous known issues I've heard of is a nullpointer exception when 
the changelog was calculated, but that was fixed in 2.11 of the trigger.

/B

Den onsdagen den 12:e februari 2014 kl. 02:10:45 UTC+1 skrev Curtis Kline:
Is anyone using the 2.0 Git plugin and the Gerrit Trigger plugin together 
successfully? I know there was a thread back around 10/29/2013 about this, but 
there didn't seem to be a clear answer as to whether these two plugins would 
now co-exist.

I tried a quick trial on my test instance and the Gerrit Trigger did not seem 
to be working when I had the Git Plugin 2.0 installed.

Curtis

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

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

RE: LTS 1.532.2 release date

[James Nord (jnord)]

That looks suspiciously like https://issues.jenkins-ci.org/browse/JENKINS-18895

Did this regress?

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 28 January 2014 11:14
To: jenkinsci-users@googlegroups.com
Subject: Re: LTS 1.532.2 release date

At least 13 threads blocked on <0x00070ee143b8>

On 28 January 2014 11:09, Stephen Connolly 
mailto:stephen.alan.conno...@gmail.com>> wrote:
Looks like a deadlock/livelock/lock contention that then starves the servlet 
thread pool...

On 28 January 2014 11:07, Stephen Connolly 
mailto:stephen.alan.conno...@gmail.com>> wrote:
Seems like a lot of these:




"Handling GET /view/%C2%A7%20Radiators%20%C2%A7/view/-%20ci%20radiator%20-/ : 
RequestHandlerThread[#464]" daemon prio=10 tid=0x7f79fc034000 nid=0x4e18 
waiting for monitor entry [0x7f79262dd000]







   java.lang.Thread.State: BLOCKED (on object monitor)

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:649)



- waiting to lock <0x00070ee143b8> (a hudson.model.RunMap)

On 28 January 2014 11:03, Arnaud Héritier 
mailto:aherit...@gmail.com>> wrote:
No sign of OOME. My JVM is configured with Xmx = 4G
Another day, another WSOD : https://gist.github.com/aheritier/8665709

On Mon, Jan 27, 2014 at 11:32 AM, Daniel Beck 
mailto:m...@beckweb.net>> wrote:

On 27.01.2014, at 03:33, Arnaud Héritier 
mailto:aherit...@gmail.com>> wrote:

> My instance is again broken this morning with a With Screen of the death
> I attached another dump and this time there is no reference to the project 
> stats plugin (even if I didn't yet had the time to remove it)  : 
> https://issues.jenkins-ci.org/browse/JENKINS-21487?focusedCommentId=193514&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-193514
I don't see why RequestHandlerThread[#269] should be blocked.

Are you out of memory? The heap information at the end looks like you only have 
a 1GB heap and it's used up.

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



--
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



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

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

RE: Build Flow - abort all the subjobs when the Main Job is aborted

[James Nord (jnord)]

The plugin is a flywieght task, and its use is  that just to co-ordingate other 
jobs.
Because of this the “build flow” job won’t have a workspace allocated to it,  
the jobs it triggers will behave exactly as they normally would,

This changed post 0.10 so if you have a 0.10 job and use its workspace to copy 
artifacts into or collate results etc then it will no longer function correctly.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Roberto González
Sent: 20 January 2014 11:59
To: jenkinsci-users@googlegroups.com
Cc: James Nord (jnord)
Subject: Re: Build Flow - abort all the subjobs when the Main Job is aborted

what do you mean with the removal of the workspace? My main job needs a 
workspace (i know that the build flow doesnt have it) to copy the artifacts 
(generated by the subjobs). The workspace folder is not created anymore with 
the lastest version of the plugin?

El lunes, 20 de enero de 2014 11:33:22 UTC, James Nord (jnord) escribió:
The version in git is stable – (if you can live with the removal of the 
workspace) (which is a feature) then go with latest.
I’ve been running it in production for a fair while without any issues.

/James
From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Roberto González
Sent: 20 January 2014 11:27
To: jenkins...@googlegroups.com
Subject: Build Flow - abort all the subjobs when the Main Job is aborted

Hi.

Im using the Build Flow plugin to make an dinamic flow of subjobs (that can run 
X subjobs given by param).
If the main job runs 200 subjobs, and the user aborts the parent job, all the 
subjobs are still running or in queue, so the user must abort them one by one.
How can i propagate the abort to all subjobs?

I saw the issue:
https://issues.jenkins-ci.org/browse/JENKINS-19423

It has an commit to Git, but there is no notice of the date when it will be 
release?

There is any form of cancel all the subjobs when the main job is aborted 
without download the last (and probably unstable) version of the plugin from 
Git?
Anybody knows the date of the release of the next version of the plugin?


Thanks and excuse my limited english.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.

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

RE: Build Flow - abort all the subjobs when the Main Job is aborted

[James Nord (jnord)]

The version in git is stable – (if you can live with the removal of the 
workspace) (which is a feature) then go with latest.
I’ve been running it in production for a fair while without any issues.

/James
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Roberto González
Sent: 20 January 2014 11:27
To: jenkinsci-users@googlegroups.com
Subject: Build Flow - abort all the subjobs when the Main Job is aborted

Hi.

Im using the Build Flow plugin to make an dinamic flow of subjobs (that can run 
X subjobs given by param).
If the main job runs 200 subjobs, and the user aborts the parent job, all the 
subjobs are still running or in queue, so the user must abort them one by one.
How can i propagate the abort to all subjobs?

I saw the issue:
https://issues.jenkins-ci.org/browse/JENKINS-19423

It has an commit to Git, but there is no notice of the date when it will be 
release?

There is any form of cancel all the subjobs when the main job is aborted 
without download the last (and probably unstable) version of the plugin from 
Git?
Anybody knows the date of the release of the next version of the plugin?


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

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

RE: What exactly is 'response time'?

[James Nord (jnord)]

Hi David,

160ms for a ping seems rather high.  Are the master/slave in different 
continents?

VM to VM (hosted on different co-located physical machine) I am getting sub 
millisecond.
   rtt min/avg/max/mdev = 0.172/0.434/0.844/0.278 ms

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: 17 January 2014 14:37
To: jenkinsci-users@googlegroups.com
Subject: RE: What exactly is 'response time'?

Hi

Pinging the slave from the master's command line consistently gives a response 
time of 160ms, as opposed to 12s.

BR

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 17 January 2014 14:32
To: jenkinsci-users@googlegroups.com
Subject: Re: What exactly is 'response time'?

Its the time the last ping packet took to route through the remoting layer.

12s does sound a bit bad... the ping may have hit the node when busy archiving 
artifacts or during a GC pause... or are some of your slaves VMs?

On 17 January 2014 14:12, David Aldrich 
mailto:david.aldr...@emea.nec.com>> wrote:
Hi

The 'Manage nodes' page of our Jenkins installation shows widely different 
response time for our slaves, ranging from 31ms to 12s.  The figure at the top 
of the column is 17min.

Our master and most slaves run Linux.  All run on an internal network.

What exactly does 'response time' indicate in this context?

Is 12s something to worry about?

What does the top figure (17mins) indicate?

Thanks in advance.

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

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

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

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

RE: Problems with Gerrit not aborting jobs cleanly

[James Nord (jnord)]

I take it you have thought about the obvious - but just incase I will restate 
it.

Use a clean workspace each time.
I actually consider this good practice as it will remove any crud that bad 
code/tests etc has left behind.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Øyvind Harboe
Sent: 13 December 2013 15:41
To: jenkinsci-users@googlegroups.com
Subject: Problems with Gerrit not aborting jobs cleanly

I'm having problems with Gerrit and Jenkins in combination not aborting jobs in 
a nice manner(*). This causes followon jobs to see a corrupted workspace and 
then these subsequent jobs fail.


I want to enable the "Build Current Patches Only" which will get rid of queued 
jobs that are no longer necessary to build because there is a more recent 
patches, thus improving throughput.

However, the problem is that "Build Current Patches Only" also aborts currently 
running jobs and therefore I'm tripped over by JENKINS-17116.

Any idea on how this could be addressed?

Ideally, I'd like JENKINS-17116 to be fixed, but it would help *greatly* if I 
could tell the Gerrit trigger not to abort jobs that have already started.


(*) This is a known problem: https://issues.jenkins-ci.org/browse/JENKINS-17116
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

RE: [ANN] Buildflow extensions plugin

[James Nord (jnord)]

Hi Domi,

Thanks for letting me know, I've update the wiki.

'build-flow-concurrent-extensions' is _currently_ correct.  I was going to 
remove the "build-flow" prefix as it's pretty obvious that you want a build 
flow extension but haven't yet done so :)


/James

From: jenkinsci-...@googlegroups.com [mailto:jenkinsci-...@googlegroups.com] On 
Behalf Of Dominik Bartholdi
Sent: 04 December 2013 17:38
To: Jenkins Developers
Cc: jenkinsci-users@googlegroups.com
Subject: Re: [ANN] Buildflow extensions plugin

Hi James,
the documentation is already inconstant: there arte two different names mention 
to register the extension, which one is correct?
- extension.'build-flow-concurrent-extensions'
or
- extension.'concurrent-extensions'
regards Domi

On 03.12.2013, at 15:02, James Nord (jnord) 
mailto:jn...@cisco.com>> wrote:


Hi all,

As per the Jenkins user conference in Palo Alto - I can now officially announce 
the open sourcing of the build flow extensions 
plugin<https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Extensions+Plugin>.

This plugin adds an extension to aid in the co-ordinating of the jobs within in 
a single when the flow is run concurrently and is at different stages. (for 
more details see these slides or 
recording<http://www.cloudbees.com/jenkins/juc2013/juc2013-palo-alto-abstracts.cb#JamesNord>)

Currently you will have to build this from source and it requires an unreleased 
version of 
thebuildflow<https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin> 
plugin.

Regards

/James


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

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

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

[ANN] Buildflow extensions plugin

[James Nord (jnord)]

Hi all,

As per the Jenkins user conference in Palo Alto - I can now officially announce 
the open sourcing of the build flow extensions 
plugin.

This plugin adds an extension to aid in the co-ordinating of the jobs within in 
a single when the flow is run concurrently and is at different stages. (for 
more details see these slides or 
recording)

Currently you will have to build this from source and it requires an unreleased 
version of the 
buildflow plugin.

Regards

/James

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

[ANN] Cucumber Results plugin.

[James Nord (jnord)]

Hi all,

As per the Jenkins user conference in Palo Alto - I can now officially announce 
the beta release (and open sourcing) of a Cucmber 
integration
 to Jenkins.

This is available in the experimental plugins update 
center.

We have been running this internally for a few months - however it may not have 
been exposed to every variation of cumbers json output so there may be some 
quirks (this leverages Gherkin itself to parse the report so quirks should be 
limited to rendering the report only).
The API (testReport/API) may still be subject to some change so should not be 
considered 100% stable.

Regards

/James

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

RE: Problem with Build Flow Plugin

[James Nord (jnord)]

That's not the flow that's stopping it but job2.

Most likely you have some post build reports (configuration ) that compare to 
the previous run to generate new/resolved issues (e.g. test results, static 
anlaysis with new violations identified...)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Zofia Majenka
Sent: 15 November 2013 17:13
To: jenkinsci-users@googlegroups.com
Subject: Problem with Build Flow Plugin

Hi,

We are using the Build Flow Plugin in Jenkins. This is scenario:

Start the flow 1: Job1 -> Job2 -> Job3 

Start the flow 2: Job1 -> Job2 -> Job3 

Start the flow 3: Job1 -> Job2 -> Job3 

The same flow is started 3 times with a few minutes delay between them.

We have noticed that thought the Job2 in the flow 3 is finished, it hangs on 
upstream notification and the Job3 within the same flow 3 could not be started. 
It waits until the Job2 in flow1 is finished and  Job2 in flow2 is finished.
Is it how it always works? The same job started in parallel (several execution 
of the same test flow on different resources) tends to become a serial?


Start Job2 flow1
Start Job2 flow2
Start Job2 flow3

Finish Job2 flow1
Finish Job2 flow2
Finish Job2 flow3

Is it possible to start as above but finish like this:

Finish Job2 flow3 and start Job3
Finish Job2 flow2 and start Job3
Finish Job2 flow1 and start Job3


Or there is something in configuration we are missing? The job is configured to 
be executed in parallel.

Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 takes 
long time to execute?

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

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

RE: build flow, early exit from parallel construct?

[James Nord (jnord)]

The changes I have put in to support this are not in a release version of the 
buildflow - so you will need to download source and compile, or grab it from 
the Jenkins ci instance.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Åsmund Østvold
Sent: 28 October 2013 17:34
To: jenkinsci-users@googlegroups.com
Subject: Re: build flow, early exit from parallel construct?

Thank you James,

I finally freed up some time and was able do a new stab at this.  I have 
inlined some questions and feedback.

On Fri, Oct 25, 2013 at 6:33 AM, James Nord (jnord) 
mailto:jn...@cisco.com>> wrote:
KillRunningjobs is called internally if the flow is aborted (or one of the jobs 
is aborted).
Internallyt this is handled by catching either  (IIRC) a JobAborteException (or 
also an IOException).

I did search for 10 minutes for "JobAborteException" or something close to 
this. But my Jenkins/Java knowledge is limite...

The IOException will show a stack trace in your console output - wheres the 
jobAbortEx will just show "Aborted" (and the cause if you set one),

I did try the blow but was not able to abort flow job. Job 'pass' takes 20s and 
job 'fail' taks only 5s:

parallel(
 {  b = build("pass");
if (b.getResult() == Result.FAILURE) {
throw new java.io.IOException("foo")
} },
 {  b = build( "fail" );
if (b.getResult() == Result.FAILURE) {
throw new java.io.IOException("foo")
}}
)

Console output:




parallel {

Schedule job fail<http://ao:8080/job/fail/>

Schedule job pass<http://ao:8080/job/pass/>

Build fail #40<http://ao:8080/job/fail/40/> started

Build pass #33<http://ao:8080/job/pass/33/> started

fail #40<http://ao:8080/job/fail/40/> completed  : FAILURE

pass #33<http://ao:8080/job/pass/33/> completed

}


I am probably doing something wrong but I am not able to see it. Any help would 
be appreciated.

So just throw one of those.  I guess I should add this to the extensions so you 
can just call ext.abortFlow("Reason") :)

With my limited understanding I believe this would be very good to have. If you 
add this could you consider adding something like:

  ext.failFlow("Reason")

It should do the same was for abortFlow("foo") but fail the build. For my use 
case this would "keep" the overall status as if all the jobs in the parallel 
section had finished. To also cover 'UNSTABLE' and 'SUCCESS' could the 
generalisation be exposing something like:

   terminateFlow(Result r, String s)

?

Also no need to check the string - check getResult() == Result.FAILURE or 
getResult().isWorseOrEqual(Result.FAILURE)

Thanks for this.

Asmund

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

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

RE: build flow, early exit from parallel construct?

[James Nord (jnord)]

Hi Åsmund ,

KillRunningjobs is called internally if the flow is aborted (or one of the jobs 
is aborted).
Internallyt this is handled by catching either  (IIRC) a JobAborteException (or 
also an IOException).
The IOException will show a stack trace in your console output - wheres the 
jobAbortEx will just show "Aborted" (and the cause if you set one),
So just throw one of those.  I guess I should add this to the extensions so you 
can just call ext.abortFlow("Reason") :)

Also no need to check the string - check getResult() == Result.FAILURE or 
getResult().isWorseOrEqual(Result.FAILURE)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Åsmund Østvold
Sent: 24 October 2013 14:28
To: jenkinsci-users@googlegroups.com
Subject: Re: build flow, early exit from parallel construct?

thank you James,

I will have a look at the new code tomorrow.

What I have now is:
parallel(
 {  b = build("pass");
if (b.getResult().toString() == "FAILURE") {
build.doStop();
}},
 {  b = build( "fail" );
if (b.getResult().toString() == "FAILURE") {
build.doStop();
}}
)

What I think I would like to be able to call is:

 private void killRunningJobs(FlowRun flowRun, BuildListener listener)

Asmund



On Thu, Oct 24, 2013 at 9:55 PM, James Nord (jnord) 
mailto:jn...@cisco.com>> wrote:
I think I made some changes in the code that may be able to help with this by 
chaining the abort to the rest of the build.

If you combine this with some groovy to abort the build (by throwing the 
relavant exception) then the jobs in progress should be aborted.

You will need to get the latest code and build it.

As always there may be other ways to achieve the same thing.

Regards,

/James

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Åsmund Østvold
Sent: 24 October 2013 08:22
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: build flow, early exit from parallel construct?

Build Flow Plugin very useful plugging.

Is it possible to get the parallel construct to "terminate" still executing 
jobs at first job exiting with none success? Or at least early fail the 
job/section containing the parallel construct.

Use case is that I have a total long(30min) check-in regression test time. Some 
tests finishes in 2 min some take 30 min. Because of early feedback and 
resources issues I would like to fail a change as early as possible.

Asmund

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

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

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

RE: build flow, early exit from parallel construct?

[James Nord (jnord)]

I think I made some changes in the code that may be able to help with this by 
chaining the abort to the rest of the build.

If you combine this with some groovy to abort the build (by throwing the 
relavant exception) then the jobs in progress should be aborted.

You will need to get the latest code and build it.

As always there may be other ways to achieve the same thing.

Regards,

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Åsmund Østvold
Sent: 24 October 2013 08:22
To: jenkinsci-users@googlegroups.com
Subject: build flow, early exit from parallel construct?

Build Flow Plugin very useful plugging.

Is it possible to get the parallel construct to "terminate" still executing 
jobs at first job exiting with none success? Or at least early fail the 
job/section containing the parallel construct.

Use case is that I have a total long(30min) check-in regression test time. Some 
tests finishes in 2 min some take 30 min. Because of early feedback and 
resources issues I would like to fail a change as early as possible.

Asmund

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

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

RE: Jenkins OutOfMemory while Recording Tests Results

[James Nord (jnord)]

Which version of Jenkins?

1.509.4 should have a fixed fix for this issue (unless all your tests are 
failing.)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mehdi Hayani
Sent: 23 October 2013 15:23
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins OutOfMemory while Recording Tests Results

i'm using -Xmx2048m, Are you sure that chaging JVM property is the only way to 
solve this problem ?
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

RE: URLTrigger and content inspection

[James Nord (jnord)]

Hi Schalk,

Poll job/lastSuccessfulBuild/buildNumberinstead and skip the whole xpath  - it 
will work and be lighter weight on the target server :)

/James



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Schalk Cronjé
Sent: 16 October 2013 14:38
To: jenkinsci-users@googlegroups.com
Subject: URLTrigger and content inspection

I am trying to monitor a remote Jenkins using the URLTrigger. I set monitoring 
to look at a XML content change in the build number i.e. using xpath of 
//number/text().

All I get is the following in the Trigger Log
[URLTrigger] - Poll with a URL

Inspecting XML content for URL 
http://OTHER_JENKINS_URL/job/OTHER_JOB_NAME/lastSuccessfulBuild/api/xml

Polling started on Oct 16, 2013 7:56:50 PM

Polling for the job JOB_NAME

Looking nodes where the poll can be run.

Looking for a node to the restricted label master.

Restrict on master label. Polling on master.



Polling on master.

Invoking the url:

 
http://OTHER_JENKINS_URL/job/OTHER_JOB_NAME/lastSuccessfulBuild/api/xml

Inspecting the content

[ERROR] - Polling error...

[ERROR] - Error message: The size between old results and new results has to be 
the same.

I have tried the same with a JSON trying both .number and 
lastSuccessfulBuild.number as JSON paths. Results are still the same.

Any ideas?

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

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

RE: build flow job artifacts

[James Nord (jnord)]

Hi Les,

I don't think there is a way to get the svn to checkout the same revision 
(however I may be wrong.)
But you can have one build checkout the code - and then archive that builds 
workspace "as an SCM", and then get your other jobs to checkout from that build.
(ie have a job that only does a checkout)
https://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin 

As for collating the artifacts - you could probably do that as a build flow 
extenstion if you feel like writing some code.

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Les Mikesell
> Sent: 06 September 2013 17:21
> To: jenkinsci-users
> Subject: build flow job artifacts
> 
> I'd like to use the build flow plugin as an alternative to a matrix build to 
> run
> approximately the same job on different platforms but with a bit more
> control.  But, is there any way to (a) ensure that the jobs it triggers all 
> build
> from the same (subversion) revision that triggered the parent, and (b) to
> collate all of the artifacts under the parent job?
> 
> --
>Les Mikesell
>  lesmikes...@gmail.com
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

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

RE: Build flow plugin: How to copy results from downstream jobs

[James Nord (jnord)]

The problem with a flow is that the flow can be dynamic - so having to specify 
the jobs may lead to incorrect jobs being aggregated - or maintinaing duplicate 
information.

It also appears to rely upon getDownStreamRelationship that relies on 
fingerprints to work unless overridden.

Perhaps this should be moved to the dev list...

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 30 August 2013 15:52
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin: How to copy results from downstream jobs

I don't want to follow this direction, as I know people won't consider the 
warning on documentation.

AggregatedTestResultPublisher can be configured with a set of jobs, maybe this 
require some tweaks on UI, not sure (sorry, don't have much time to investigate 
on this topic today)

2013/8/30 John Russell mailto:jjruss...@gmail.com>>
I see the class javadoc for that class but how would I use that to actually 
aggregate the junit tests to report in the build-flow plugin?

Is it also possible to discourage people in the documentation and yet leave the 
workspace there so its possible?

On Fri, Aug 30, 2013 at 9:22 AM, nicolas de loof 
mailto:nicolas.del...@gmail.com>> wrote:
I indeed removed workspace support especially to discourage such a "write some 
custom jenkins code using DSL" approach.
build-flow is about orchestrating jobs, not creating custom plugins

junit aggregator is using the original location for junit results, and 
dynamically aggregating. It doesn't copy to local project.

2013/8/30 John Russell mailto:jjruss...@gmail.com>>
Teilo, When did build flow stop having a workspace? I finally got this to work 
by archiving all of the junit files from the downstream jobs onto the master, 
running build-flow on the master, and directly copying the files from the 
archive of the downstream build to build flow and running the junit results 
post build step.

So this won't work anymore? If there is no workspace how would any junit result 
post build step work?


On Friday, August 30, 2013 4:14:04 AM UTC-4, teilo wrote:
The BuildFlow doesn't use a workspace anymore[1] - so your workaround most 
likely won't work as you expect.

I'm not convinced that this is a good thing as like you I would like to show 
test results in the main flow job - not have another job that is just aggregate 
& report.

On Monday, 12 August 2013 20:17:54 UTC+1, John Russell wrote:
Do you guys have any idea how to pull files, specifically test results, from 
the jobs started in a build flow up to the build flow job itself so it can be 
the one that presents all of the test results?

I presume that if I can copy them from the slaves up to the workspace of the 
build flow build that the post build step of processing the test results will 
get them all. Any thoughts on how to get those files back to the master?

On Thursday, January 3, 2013 2:30:31 AM UTC-5, Nicolas De loof wrote:
sure, rescue handle whatever happens in gard block, that has no restriction on 
nested content
2013/1/3 Patrick van der Velde 
mailto:petrikva...@gmail.com>>
Thanks for that suggestion. One question about the guard statement. Can it 
handle multiple statements? i.e. is the following allowed?

guard {
build("job1")
build("job2")
} rescue {
build("finaljob")
}

or even this

guard {
parallel(
{ build("job1a") },
{ build("job2a") },
)

parallel(
{ build("job1b") },
{ build("job2b") },
)
} rescue {
build("finaljob")
}

My script looks a bit like that last one but when I tried putting a guard 
clause around it I got the following error:










ERROR: Failed to run DSL Script

groovy.lang.MissingMethodException:
 No signature of method: com.cloudbees.plugins.flow.FlowDelegate.rescue() is 
applicable for argument types: (Script1$_run_closure1_closure3) values:

Removing the guard clause made it work. So I'm guessing guard can only handle 1 
item?

Thanks

Petrik

On Wed, Jan 2, 2013 at 10:16 PM, nicolas de loof 
mailto:nicolas...@gmail.com>> wrote:
use gard+rescue so you can execute a post-job even when some jobs are unstable

2013/1/2 Patrick mailto:petrikva...@gmail.com>>
Ok I'm going to have to amend this answer. My idea of having a separate job at 
the end to gather the results would work if it wasn't for the fact that the 
build flow plugin kills the build as soon as one of the jobs fails. That means 
I only can get the results if the build works which is not what I want. I want 
the results gathering to always take place, even if the all the build jobs 
fail. Any way to achieve this?

Thanks

Petrik


On Wednesday, 2 January 2013 11:46:54 UTC+13, Patrick wrote:
Hi

Mmm ok, I guess I could create a separate job to gather all the test results. 
Thanks for the advice :)

Regards

Petrik





--
You received this message because you

RE: Build flow plugin: How to copy results from downstream jobs

[James Nord (jnord)]

If the things you are aggregating aren't junit like test reports you're a bit 
lost though.

E.g. https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin

Whilst cucumber does support JUnit output which could be used by the 
Aggregated...Publisher - it is exceptionally limited to the point that it is 
virtually useless.
And whilst this could be a classed as a deficiency in the cucumber plugin or 
cucumber - mapping cucumber results to Jenkins SuiteResult/CaseResults doesn't 
really fit - so you end up trying to put a square peg into a round hole.

/James


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 30 August 2013 09:28
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin: How to copy results from downstream jobs

AggregatedTestResultPublisher should work with build-flow, passing the list of 
jobs to aggregate. I'm not sure it could automatically support the downstream 
mode, need to setup a test instance to check what prevent this, but can image 
few reasons.

2013/8/30 teilo mailto:teilo+goo...@teilo.net>>
The BuildFlow doesn't use a workspace anymore[1] - so your workaround most 
likely won't work as you expect.

I'm not convinced that this is a good thing as like you I would like to show 
test results in the main flow job - not have another job that is just aggregate 
& report.


On Monday, 12 August 2013 20:17:54 UTC+1, John Russell wrote:
Do you guys have any idea how to pull files, specifically test results, from 
the jobs started in a build flow up to the build flow job itself so it can be 
the one that presents all of the test results?

I presume that if I can copy them from the slaves up to the workspace of the 
build flow build that the post build step of processing the test results will 
get them all. Any thoughts on how to get those files back to the master?

On Thursday, January 3, 2013 2:30:31 AM UTC-5, Nicolas De loof wrote:
sure, rescue handle whatever happens in gard block, that has no restriction on 
nested content
2013/1/3 Patrick van der Velde 
mailto:petrikva...@gmail.com>>
Thanks for that suggestion. One question about the guard statement. Can it 
handle multiple statements? i.e. is the following allowed?

guard {
build("job1")
build("job2")
} rescue {
build("finaljob")
}

or even this

guard {
parallel(
{ build("job1a") },
{ build("job2a") },
)

parallel(
{ build("job1b") },
{ build("job2b") },
)
} rescue {
build("finaljob")
}

My script looks a bit like that last one but when I tried putting a guard 
clause around it I got the following error:






ERROR: Failed to run DSL Script

groovy.lang.MissingMethodException:
 No signature of method: com.cloudbees.plugins.flow.FlowDelegate.rescue() is 
applicable for argument types: (Script1$_run_closure1_closure3) values:

Removing the guard clause made it work. So I'm guessing guard can only handle 1 
item?

Thanks

Petrik

On Wed, Jan 2, 2013 at 10:16 PM, nicolas de loof 
mailto:nicolas...@gmail.com>> wrote:
use gard+rescue so you can execute a post-job even when some jobs are unstable

2013/1/2 Patrick mailto:petrikva...@gmail.com>>
Ok I'm going to have to amend this answer. My idea of having a separate job at 
the end to gather the results would work if it wasn't for the fact that the 
build flow plugin kills the build as soon as one of the jobs fails. That means 
I only can get the results if the build works which is not what I want. I want 
the results gathering to always take place, even if the all the build jobs 
fail. Any way to achieve this?

Thanks

Petrik


On Wednesday, 2 January 2013 11:46:54 UTC+13, Patrick wrote:
Hi

Mmm ok, I guess I could create a separate job to gather all the test results. 
Thanks for the advice :)

Regards

Petrik





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

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

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

RE: Build Flow Plugin - Groovy libraries

[James Nord (jnord)]

Hi Bob,

You could package it up in an extension (plugin).
See 
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin#BuildFlowPlugin-ExtensionPoint

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
Sent: 28 August 2013 15:51
To: jenkinsci-users@googlegroups.com
Subject: RE: Build Flow Plugin - Groovy libraries

After thinking about this a little more, I think that the best workaround is to 
treat Jobs as libraries. The Build Flow job can invoke "common library" jobs 
that can execute Groovy code.

Bob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
Sent: Wednesday, August 28, 2013 10:24 AM
To: jenkinsci-users@googlegroups.com
Subject: Build Flow Plugin - Groovy libraries

Hi,

I have been using the Build Flow Plugin for a while now, and it works great.


I have multiple Build Flow Plugin jobs that have common groovy code that I'd 
like to put into a Groovy library (call it Library.groovy). The Build Flow 
Plugin uses groovy.lang.GroovyShell to execute the groovy code and I have not 
found a way to have it include common groovy library code.

Has anyone found a way to include common Groovy library code into multiple 
Build Flow Plugin jobs? I don't think it is possible, but then again, I may be 
missing something.

Thanks for your time,
Bob

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

RE: [POLL] how addicted are you to the current Subversion plugin's authentication model?

[James Nord (jnord)]

Hi Stephen,

OK - so just had a play with it.

There is a slight flaw in your plan - and that is how it would appear to break 
multiple sites and cloudbees templates.

Looking at the node configuration the credentials the credentials are linked by 
ID not name (which is probably a good thing!), however now we need to sync 
across not only cloudbees templates definitions but also credentials and some 
systems have credentials that others for security reasons shouldn't have and 
there will be no way of knowing what ID should be used in any job template :-o

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 08 August 2013 13:50
To: jenkinsci-users@googlegroups.com
Subject: Re: [POLL] how addicted are you to the current Subversion plugin's 
authentication model?

You will create a credentials domain in the Manage Credentials screen which has 
a specification like:

  URI Scheme: svn+ssh,ssh
  Hostname and port: include=*.foo.com:22<http://foo.com:22>

You will add the single ssh key into that credential domain.

When you type in any url that matches the domain specification, then that 
credential will be added to the drop down.

In the normal case you will not have any global ssh type credentials, so as 
soon as you start to type svn+ssh: the domain requirements will narrow down to 
only those that are in svn+ssh domains... then when you get as far as 
svn+ssh://someserver.foo.com/<http://someserver.foo.com/> any other credential 
domains for different hosts will have been eliminated and you will be left with 
the single choice.

The connection check will tell you if you have got the required credentials as 
before... I'll see if I can get some screenshots to illustrate, but the 
credential domain screenshot on 
https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin should give you 
a better idea

On 8 August 2013 13:20, James Nord (jnord) 
mailto:jn...@cisco.com>> wrote:
Hi Stephen,

Can you explain some more about what you mean by "relevant credentials for that 
URL" - and how you may determine what is relevant?

Currently for svn+ssh we don't need to add every single repositrory URL into 
Jenkins: I have defined one and one credential for Jenkins for 
svn+ssh://mysvnserver.foo.com/<http://mysvnserver.foo.com/>  even though the 
repositories are actually 
svn+ssh://mysvnserver.foo.com/svn/repo1<http://mysvnserver.foo.com/svn/repo1>, 
svn+ssh://mysvnserver.foo.com/svn/repo2<http://mysvnserver.foo.com/svn/repo2> 
etc..

The other thing if you are doing this from a generic usability point is perhaps 
think about if multiple options are available being able to set one as a 
default such that users who are unsure of which option to choose will, if they 
do nothing, get the correct option 80% of the time.

/James


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: 08 August 2013 13:02
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>

Subject: [POLL] how addicted are you to the current Subversion plugin's 
authentication model?

In working on integrating with the Credentials plugin there is, from my point 
of view, a lot of insanity and crazy ways of doing auth.

How attached are people to the existing way?

The way I want to deliver is that you have a drop down underneath any of the 
module remote url fields which lists the relevant credentials for that URL 
(including none) and you would always make a selection (even if that selection 
is leaving the default of "none" selected)

I would like to ditch entirely the existing model of credentials and go 
straight for this simplified model.

What do people think?


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


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

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>

RE: interogate other buildflow runs?

[James Nord (jnord)]

Hi Nicolas,

Sorry for the delay but I have just been able to get around to starting this.

I see concurrency as an integral part of a flow manager - are you sure you want 
this in a extension plugin?

There are some advantages to it being in the main plugin

* the state is easy to maintain - no Listeners to check for job 
deletion etc.

* Anyone wanting to do something else orchestrated across multiple runs 
doesn't have to re-invent state management

* It is more performant as reduces the granularity of locking required 
(locking Object state only occurs at the Job level not at the Jenkins Level)

I've already started on fixing the buildflow so it can run concurrently but 
without some form of flow aware throttling the flows can easily overwhelm a 
Jenkins instance where the trigger of a flow is happening often (after a 
"source code commit build") but the flow contains longer running jobs (e.g. 
multiple levels of acceptance tests).

e.g.

-- begin example flow_def --
build(job1)
block("longRunning1") {
// this job would take 10 minutes and give some "smoke test" coverage
 build("bigjob", parameter1:upstream.param.foobar")
 }
block("longRunning2") {
// this job would take 30 minutes each,  and has some more indepth tests
parallel {
   build("biggerjob", parameter1=upstream.param.foobar, testset= "subset1")
   build("biggerjob", parameter1=upstream.param.foobar, testset= "subset2")
}
}
block("longRunning3") {
// this job would take 60 minutes each, and has some very detailed in depth 
tests
parallel {
   build("biggerjob", parameter1=upstream.param.foobar, testset= "subset1")
   build("biggerjob", parameter1=upstream.param.foobar, testset= "subset2")
  }
}
-- end example flow_def --

/**
 * The block DSL ensures that only one FlowRun of a particular BuildFlow 
will execute the steps contained within it concurrently.
 * It further will only allow the most recent FlowRun to proceed if 
multiple FlowRun are waiting on the same block.
 */

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 28 June 2013 22:43
To: jenkinsci-users@googlegroups.com
Subject: Re: interogate other buildflow runs?

I would prefer this to be part of some extension plugin. Extension point exist 
so you can introduce some new SDL functions

2013/6/28 James Nord (jnord) mailto:jn...@cisco.com>>
If I managed to get the buildflow plugin to build and pass unit tests (master 
is broken on my windows box), and got my IDE to understand the groovy stuff, 
and added this support is this something that you would accept as a patch, or 
would you prefer that it would live in a separate plugin as an extension?

/James

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of nicolas de loof
Sent: 28 June 2013 17:55
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: interogate other buildflow runs?

this isn't possible, this require state management between flows execution that 
build-flow plugin don't offer

2013/6/28 James Nord (jnord) mailto:jn...@cisco.com>>
Hi all,

I would like to have a buildflow job "flowjob" that kicks of job1, job2 & job3 
sequentially.

The trigger for the flowjob is a successful build of "upstream".

I want to be able to run flowjob for every upstream trigger (so far so simple)

But I only want the flowjob to run as far as any other flowjob has currently 
got to.
e.g.
if flowjob#1 is currently running job2
then flowjob#1 should run job1 but not job2 or job3.

to make this more interesting in the future I want to replace job2 with a 
parallel invocation of job2 with multiple different parameters, and job3 may 
just be another job2 but with different parameters...

Is this possible?  Can I get access to the Jenkins job object for the flow to 
interrogate it somehow - or do I need to write an extension that I can call.

Any hints or tips greatly appreciated.

Regards,

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



--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkins

RE: [POLL] how addicted are you to the current Subversion plugin's authentication model?

[James Nord (jnord)]

Hi Stephen,

Can you explain some more about what you mean by "relevant credentials for that 
URL" - and how you may determine what is relevant?

Currently for svn+ssh we don't need to add every single repositrory URL into 
Jenkins: I have defined one and one credential for Jenkins for 
svn+ssh://mysvnserver.foo.com/  even though the repositories are actually 
svn+ssh://mysvnserver.foo.com/svn/repo1, 
svn+ssh://mysvnserver.foo.com/svn/repo2 etc..

The other thing if you are doing this from a generic usability point is perhaps 
think about if multiple options are available being able to set one as a 
default such that users who are unsure of which option to choose will, if they 
do nothing, get the correct option 80% of the time.

/James


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Stephen Connolly
Sent: 08 August 2013 13:02
To: jenkinsci-users@googlegroups.com
Subject: [POLL] how addicted are you to the current Subversion plugin's 
authentication model?

In working on integrating with the Credentials plugin there is, from my point 
of view, a lot of insanity and crazy ways of doing auth.

How attached are people to the existing way?

The way I want to deliver is that you have a drop down underneath any of the 
module remote url fields which lists the relevant credentials for that URL 
(including none) and you would always make a selection (even if that selection 
is leaving the default of "none" selected)

I would like to ditch entirely the existing model of credentials and go 
straight for this simplified model.

What do people think?


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


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

RE: trigger a build ONLY when there has been a M2_RELEASEBUILD

[James Nord (jnord)]

Currently there is no simple way, hoiwever I think you can achieve what you 
want with the following:


1)  use a URLtrigger (XTrigger plugin) on latestRelease permalink and 
inspect the content to cause job B to run.

2)  use a RunParameter on job B to get the parameters from the release 
build (I have not tried this).
  From https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build
* To use a Run Parameter, the value should be in the format 
jobname#buildNumber (eg. "&MyRunParam=foo-job%2399" for foo-job #99)

/James



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maven User
Sent: 06 August 2013 22:26
To: jenkinsci-users@googlegroups.com
Subject: trigger a build ONLY when there has been a M2_RELEASEBUILD

I think I may be over engineering this one a bit (headed to post-build groovy 
scripting hell), but I was wondering - is there an easy way to trigger another 
build (with two parameters from the release plugin) when a maven release has 
been triggered?

For instance, when you run the maven release plugin on job "A", I want to call 
job "B" only if "A" was both successful AND if it if "IS_M2RELEASEBUILD" is 
true.

I looked at all sorts of things but wondering if there's something off the 
shelf I can use before going back to groovy...

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


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

RE: M2 Release Plugin (release:branch not working for me)

[James Nord (jnord)]

The console output appears to show the shell is running after the maven build 
(as the shell output is after the line "Waiting for Jenkins to finish 
collecting data
")

What is printed before that output

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of spacegoose
Sent: 08 July 2013 19:47
To: jenkinsci-users@googlegroups.com
Subject: M2 Release Plugin (release:branch not working for me)

I'm trying to use the M2 Release Plugin in a Jenkins 1.517 job with github, but 
it doesn't seem to be working ...


I only want to use it to release:branch at the moment and want to give the 
branchName as a parameter, I have tried it as a parameter and hard coded (with 
and w/o -e):

-Dresume=false -e release:branch -DbranchName=monkey-rc2 
-DupdateWorkingCopyVersions=false -DupdateBranchVersions=false -DdryRun=false
-Dresume=false -e release:branch -DbranchName=${branchname} 
-DupdateWorkingCopyVersions=false -DupdateBranchVersions=false -DdryRun=false


but it fails to execute in my job, I have an "execute shell" right before the 
m2 plugin, (e.g. echo "before m2 plugin") and that is pretty much the last 
thing that happens:



Waiting for Jenkins to finish collecting data

channel stopped

[nyuCMS-test] $ /bin/sh -xe /tmp/hudson7449209946030619405.sh

+ echo 'before m2 plugin'

before m2 plugin

Finished: SUCCESS

I do see this in the jenkins.log:

(scm manipulator not settled !)

I am able to execute:

-Dresume=false -e release:branch -DbranchName=monkey-rc2 
-DupdateWorkingCopyVersions=false -DupdateBranchVersions=false -DdryRun=false

on the command line, and within the project's execute shell script 
functionality, and that works, would like to use the plugin however.

The Jenkins machine has push / pull access to my git repo.

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


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

RE: Disable fingerprinting? (1.509.1 LTS)

[James Nord (jnord)]

For Maven2/3 type jobs you don't have the ability to disable fingerprinting.

For the other Freestyle job IIRC you have to enable fingerprinting of files.

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Steffen Breitbach
> Sent: 08 July 2013 10:10
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Disable fingerprinting? (1.509.1 LTS)
> 
> 
> Hi Chris!
> 
> On 05.07.2013 18:58, Chris Withers wrote:
>  >
>  > What problem are you experiencing that make you think you want to go out
> > of your way to disable fingerprinting?
>  >
>  > If you don't need it, don't actively use it, but it being there does you  
> > no
> harm...
> 
> Well, unfortunately, that isn't entirely true. We have the same problem as
> described in https://issues.jenkins-ci.org/browse/JENKINS-13154 on our
> machine (apart from having I/O issues in general which are made worse by
> this).
> There is one comment in this issue:
> "Seems to me that the size of the "fingerprints" folder has quite an impact on
> the performance of "collecting data". Today I backed up and removed the
> fingerprint data (~1,3Gb) and restarted Jenkins. Data collection now takes ~10
> seconds instead of 10-15 minutes."
> 
> We had the same problem so I also deleted the fingerprints as a possible
> solution. We had a number of fingerprints with 6 digits (can't remember the
> exact number right now). Just after restarting Jenkins with an empty
> fingerprints folder, we had about 2500 new fingerprints.
> 
> Also it seems that the "Fingerprint cleanup.log" is never written.
> 
> Anyhow, as we don't use it I'd rather disable it completely.
> 
> Regards
>Steffen
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 

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

RE: Unable to release project from a specific jenkins box using m2 release plugin and perforce SCM

[James Nord (jnord)]

Passwords with any shell special characters aren't handled properly (there is 
an open JIRA).

So '\' on Unix like OSs will want some escaping - try your password with \\ 
instead of a single backslash - or put quotes around it.

Is your other box which can perform releases a windows box?  That's the only 
reason I can think of that it works on one and not on another.

/James


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Usman Ismail
Sent: 06 July 2013 01:15
To: jenkinsci-users@googlegroups.com
Subject: Unable to release project from a specific jenkins box using m2 release 
plugin and perforce SCM

I am using the maven release plungin using the jenkins m2release plugin and 
keep getting the error shouwn below.

The username and password is correct as I have tested it on other machines and 
also to get source from this jenkins box. The password only fails on release 
and not at any other point.

The only weird thing I can think off is that the user name has a '\' in it but 
this does seem to the phase my other jenkins box which works correctly.

Is there anything I can do get a more detailed error message or debug whats 
going on?

[INFO]
[INFO] --- maven-release-plugin:2.4:prepare (default-cli) @ cascade-proto ---
[INFO] Verifying that there are no local modifications...
[INFO]   ignoring changes on: **/pom.xml.backup, **/release.properties, 
**/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
[ERROR] CommandLineException Exit code: 1 - Perforce password (P4PASSWD) 
invalid or unset.

Command line was:p4 -d /opt/hudson_workspace01/jobs/JOB-NAME/workspace -p 
perforceserver.com:1666 -u "A\b" -P *** opened 
//X/XX/XX-XXX/...
org.codehaus.plexus.util.cli.CommandLineException: Exit code: 1 - Perforce 
password (P4PASSWD) invalid or unset.

Command line was:p4 -d /opt/hudson_workspace01/jobs/JOB-NAME/workspace -p 
perforceserver.com:1666 -u "A\b" -P *** opened 
//X/XX/XX-XXX/...
at 
org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.readOpened(PerforceStatusCommand.java:116)
at 
org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.executeStatusCommand(PerforceStatusCommand.java:59)
at 
org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java:44)
at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
at 
org.apache.maven.scm.provider.perforce.PerforceScmProvider.status(PerforceScmProvider.java:226)
at 
org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:793)
at 
org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.execute(ScmCheckModificationsPhase.java:126)
at 
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:234)
at 
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
at 
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
at 
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
at 
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:277)
at 
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:232)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
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.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:98)
at hudson.maven.Maven3Builder.call(

RE: interogate other buildflow runs?

[James Nord (jnord)]

If I managed to get the buildflow plugin to build and pass unit tests (master 
is broken on my windows box), and got my IDE to understand the groovy stuff, 
and added this support is this something that you would accept as a patch, or 
would you prefer that it would live in a separate plugin as an extension?

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 28 June 2013 17:55
To: jenkinsci-users@googlegroups.com
Subject: Re: interogate other buildflow runs?

this isn't possible, this require state management between flows execution that 
build-flow plugin don't offer

2013/6/28 James Nord (jnord) mailto:jn...@cisco.com>>
Hi all,

I would like to have a buildflow job "flowjob" that kicks of job1, job2 & job3 
sequentially.

The trigger for the flowjob is a successful build of "upstream".

I want to be able to run flowjob for every upstream trigger (so far so simple)

But I only want the flowjob to run as far as any other flowjob has currently 
got to.
e.g.
if flowjob#1 is currently running job2
then flowjob#1 should run job1 but not job2 or job3.

to make this more interesting in the future I want to replace job2 with a 
parallel invocation of job2 with multiple different parameters, and job3 may 
just be another job2 but with different parameters...

Is this possible?  Can I get access to the Jenkins job object for the flow to 
interrogate it somehow - or do I need to write an extension that I can call.

Any hints or tips greatly appreciated.

Regards,

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



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


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

interogate other buildflow runs?

[James Nord (jnord)]

Hi all,

I would like to have a buildflow job "flowjob" that kicks of job1, job2 & job3 
sequentially.

The trigger for the flowjob is a successful build of "upstream".

I want to be able to run flowjob for every upstream trigger (so far so simple)

But I only want the flowjob to run as far as any other flowjob has currently 
got to.
e.g.
if flowjob#1 is currently running job2
then flowjob#1 should run job1 but not job2 or job3.

to make this more interesting in the future I want to replace job2 with a 
parallel invocation of job2 with multiple different parameters, and job3 may 
just be another job2 but with different parameters...

Is this possible?  Can I get access to the Jenkins job object for the flow to 
interrogate it somehow - or do I need to write an extension that I can call.

Any hints or tips greatly appreciated.

Regards,

/James

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

RE: Perform Maven Release error in build 1.519

[James Nord (jnord)]

For google searching purposes, the issue was fixed in m2Release 0.10.0 so a 
Jenkins upgrade is not needed.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of glsilver...@pssd.com
Sent: 27 June 2013 20:30
To: jenkinsci-users@googlegroups.com
Subject: Re: Perform Maven Release error in build 1.519

Problem corrected. I updated to version 1.520 and also updated the Maven 
Release plugin. That did the trick.

On Thursday, June 27, 2013 11:48:59 AM UTC-7, 
glsil...@pssd.com wrote:
I'm getting the following error when I do a "Perform Maven Release" and click 
on "Schedule Maven Release Build" button:

Status Code: 500

Exception: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to 
net.sf.json.JSONObject
Stacktrace:

javax.servlet.ServletException: java.lang.ClassCastException: 
net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject

   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)

   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

   at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)

   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)

   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

   at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)

   at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)

   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

   at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)

   at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)

   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)

   at org.kohsuke.stapler.Stapler.service(Stapler.java:214)

   at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)

   at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)

   at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)

   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)

   at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)

   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)

   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)

   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)

   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)

   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)

   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)

   at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)

   at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)

   at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)

   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)

   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)

   at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)

   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)

   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)

   at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)

   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)

   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)

   at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)

   at 
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227)

   at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)

   at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)

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

   at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)

   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

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

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


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from thi

RE: Update to strange Jenkins version number?

[James Nord (jnord)]

It is 1.518 with a potential fix for Jenkins-14362[1] added for testing.

More info is in the bug - possibly shouldn't be in the update site but I will 
leave that for someone else to comment on.

/James

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

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Louis Roché
Sent: 18 June 2013 08:48
To: jenkinsci-users@googlegroups.com
Cc: matthew.web...@diamond.ac.uk
Subject: Re: Update to strange Jenkins version number?

Same 'problem' here.

On Tuesday, June 18, 2013 9:43:32 AM UTC+2, 
matthew...@diamond.ac.uk wrote:
My Jenkins release, currently 1.518, is telling me:
--> New version of Jenkins (1.518.JENKINS-14362-jzlib) is available for download

Does anyone know what this is about? http://jenkins-ci.org/changelog tells me 
that that is the latest release number, but I could find no other reference to 
it anywhere. Is this an official release?

Thanks
Matthew


--
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom



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


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

RE: Jenkins vs. EBCDIC

[James Nord (jnord)]

Looks like jenkins serves up its JNLP pages without an XML prolog (the  bit)...

If you save the file and add an XML prolog for UTF-8 and run from that without 
setting the encoding - does that work?

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dirk Haun
Sent: 12 June 2013 15:03
To: jenkinsci-users
Subject: Re: Jenkins vs. EBCDIC

Ah, the default encoding. It seems we *have* to set it to something other than 
EBCDIC so we can even get a connection to our master.
The slave is connected via Java Web Start and started like so:

java -Dfile.encoding=ISO8859_1 -jar slave.jar -text -jnlpUrl 
http:///computer/sva-zpdt-emul/slave-agent.jnlp
 -auth :
Without the -Dfile.encoding (or setting it to EBCDIC), the slave can not get a 
connection to the master.

Connecting via ssh is not an option, as it's not available on the emulator.
Any suggestions?

On Wed, Jun 12, 2013 at 11:14 AM, Kohsuke Kawaguchi 
mailto:k...@kohsuke.org>> wrote:
This should work out of the box, because we take the encoding of the slave into 
account for obvious reasons.

the "Execute Shell" feature uses the CommandInterpreter class, which uses the 
FilePath.createTextTempFile method to create a shell script. This file takes 
contents as String, then uses the encoding of the slave when it does "new 
FileWriter(f)". So it should write the shell script in EBCDIC.

Does your slave JVM have a proper default encoding configured?


2013/6/12 Dirk Haun <68k...@gmail.com>
We're trying to use Jenkins to build our software on OS/390 (using the Hercules 
emulator, not real hardware, but still). This OS uses EBCDIC as its native 
character set, not ASCII. We've successfully managed to check out from our SVN 
repository (yay!), but now we would need to run commands to build the software. 
And this is where we run into problems ...
The problem is that commands that we type into the text field of the "Execute 
shell" build step need to be translated from ASCII to EBCDIC when run on the 
OS/390 side. We confirmed that this is the problem by manually translating a 
simple command to EBCDIC and typing those characters into the text input field 
- the command was then executed.
However, a lot of EBCDIC characters have non-printable ASCII equivalents, so 
this is not an option in practice (besides it being a pain in the back to 
maintain).
Is there any any plugin that can handle this situation?
Alternatively, is there a plugin that would simply let us run a script that's 
already on the OS/390 side? Please note that again, there's the problem of 
character set translation - this time with the file name; but since the SVN 
plugin does work as expected, maybe some part of Jenkins is already doing the 
right thing.
We're stuck at this point, so any help is appreciated. Thank you.
bye, Dirk
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





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



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


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

RE: Having real problem importing a job config.xml from another Jenkins server

[James Nord (jnord)]

Hi Michael,

If you check the target server logs you will probably see an xstream exception 
which may give you a clue.
Once you have that clue try upgrading that plugin (rinse & repeat).

Just hope it's not a jenkins version issue as then you will have to upgrade 
your Jenkins...

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
michael.brown...@cisco.com
Sent: 11 June 2013 17:23
To: jenkinsci-users@googlegroups.com
Subject: Re: Having real problem importing a job config.xml from another 
Jenkins server

Any idea how to get around this, if I don't have access to the other Jenkins 
server?

Thanks,
Michael

On Tuesday, June 11, 2013 9:18:50 AM UTC-7, KT wrote:

It is possible that plugin versions or the version of Jenkins is not the same 
as the other server and a configuration setting is causing a problem with it 
being displayed.



Are you using promotions?



From: "michael browning" >
To: jenkins...@googlegroups.com
Sent: Tuesday, June 11, 2013 11:00:12 AM
Subject: Having real problem importing a job config.xml from another Jenkins 
server
I am having problems importing a job config.xml from another Jenkins server.  I 
don't have access to the other Jenkins server so I can not use the URL to 
import the job.  I have tried creating a new Job in jenkins and then replacing 
the config.xml with the one from the other server.  As soon as I select "Reload 
Configuration from Disk" the new job disappears.  I have also tried using the 
commandline: java -jar /home/saba/jenkins-cli.jar -s 
http://saba-ci.us.nds create-job Mike-Nam2 < 
/home/saba/config_NAM_IPAD-RELEASES.xml.

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


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


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

Gerrit Trigger warning

[James Nord (jnord)]

Hi all (or most likely Robert!),

Should I be worried about the following entry in the log when starting Jenkins

com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory 
started
WARNING: Build started without being registered first.

Regards,

/James

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

RE: Jenkins has a long startup time, how to avoid it?

[James Nord (jnord)]

I use VMWare :)

What kind of datastore are you using then - it's likely that it is just not up 
to the job (even 16 * local SAS disks with 1GB FBWC couldn't cope!)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Eduardo Dias
Sent: 04 June 2013 14:56
To: jenkinsci-users
Subject: Re: Jenkins has a long startup time, how to avoid it?

Hi james,

thanks, I will check the JVM config, regarding disk, I use VMWare and I can 
notuse SDD.

Regards,

Eduardo

2013/6/4 James Nord (jnord) mailto:jn...@cisco.com>>
Hi Eduardo,

I replaced a local RAID 5 array with a single SSD for a test and startup time 
went from hours to minutes...
YMMV, but look at the system and look at IOWait, disk read latencies etc..

(This is with Jenkins prior to Lazy loading)

You may also want to look at the JVM, is it spending too much time in GC etc.

/James


From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Eduardo Dias
Sent: 03 June 2013 20:28

To: jenkinsci-users
Subject: Jenkins has a long startup time, how to avoid it?

Hi All,

our Jenkins has a long startup time after system reboot, it is not common, but 
some times heppens.
Has any tip to avoid it?
I can not clean up my job history.

regards,

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


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





--

Atenciosamente,

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


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

RE: Jenkins has a long startup time, how to avoid it?

[James Nord (jnord)]

Hi Eduardo,

I replaced a local RAID 5 array with a single SSD for a test and startup time 
went from hours to minutes...
YMMV, but look at the system and look at IOWait, disk read latencies etc..

(This is with Jenkins prior to Lazy loading)

You may also want to look at the JVM, is it spending too much time in GC etc.

/James


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Eduardo Dias
Sent: 03 June 2013 20:28
To: jenkinsci-users
Subject: Jenkins has a long startup time, how to avoid it?

Hi All,

our Jenkins has a long startup time after system reboot, it is not common, but 
some times heppens.
Has any tip to avoid it?
I can not clean up my job history.

regards,

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


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

RE: Maven-release-plugin pushing snapshots instead of releases

[James Nord (jnord)]

Hi Brett,

There are several ways that Jenkins publishes things (post deploy, or as part 
of the build).
Can you be more exact about what is happening and what you think is wrong (also 
how are you triggering the release?)

Regards,

/James


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brett Delle Grazie
Sent: 29 May 2013 12:00
To: jenkinsci-users@googlegroups.com
Subject: Maven-release-plugin pushing snapshots instead of releases

Hi,

We've got an odd situation with Jenkins 1.509.1 LTS and latest plugins 
including maven2 release.

When triggering a release build, Jenkins is publishing a SNAPSHOT build instead 
of the release build configured.

Has anyone come across this before?

Thanks,

Brett
--
Best Regards,

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


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

RE: m2 release plugin versioning policy

[James Nord (jnord)]

From: Hilikus [mailto:thehili...@gmail.com]
Sent: 17 May 2013 18:57
To: jenkinsci-users@googlegroups.com
Cc: James Nord (jnord)
Subject: Re: m2 release plugin versioning policy

when you say it will be coming back you mean what? being able to set a 
different version in the UI for each submodule

[JTN] Yes

or letting maven decide based on the SNAPSHOT version in the pom?

[JTN] if the issues with it can be worked out – and I think I have a plan.

or both?

[JTN] the individual one first, if the plan for using maven works, then using 
maven will be done after (or possibly at the same time).


How complex are the changes?

For the prompt the user – not very, it’s a buncy of Jelly config and moving 
some parameters around (and checking that no new modules have been introduced 
since the last build)

could someone without jenkins plugin experience do it in a couple of days?

[JTN] I would think so – the code did exist and was removed – so there is 
already some guidance on how to do this.

it sounds to me like just a matter of constructing the correct command line 
invocation

[JTN] that’s the easy bit (assuming you’re not on windows and don’t blow the 
command line argument length!).  You need to store the variables in a the 
Action and get them from the post, and have the UI prompt for them.

On Friday, 17 May 2013 12:02:06 UTC-4, James Nord (jnord) wrote:
If you require that functionality you will need to downgrade to an earlier 
version (I think 0.7.1).

The functionality will be coming back but I have no current ETA.
See https://issues.jenkins-ci.org/browse/JENKINS-11466

/James

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Hilikus
Sent: 17 May 2013 16:50
To: jenkins...@googlegroups.com
Subject: m2 release plugin versioning policy

Hello everyone,

It looks like the current behaviour when doing a maven release from jenkins in 
a multi-module project is to assign the version specified in the web ui of 
jenkins to ALL the submodules

e.g in a project like this

1.0.0-SNAPSHOT  (A)
   |...1.0.0-SNAPSHOT (A1)
   |...2.3.0-SNAPSHOT (A2)

if I specify in the ui that the version of the root pom (A in my example) 
should be 1.0.0 then even the second submodule (2.3.0-SNAPSHOT) will be 
released with version 1.0.0, probably due to the -B -DreleaseVersion arguments 
combo. Is there any way to change this behaviour? what I want is to release 
A1=1.0.0, A2=1.0.0 and A3=2.3.0

I see a "default versioning mode" in the configuration that seems to do just 
that; however, 1) it never keeps its state, whatever I change it to, it goes 
back to none 2) it doesn't even look like the actual behaviour is none, since 
none seems to be what I want. The behaviour I see is "specify one version for 
all modules"

I'm using m2release 0.10 and jenkins 1.460


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


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

RE: m2 release plugin versioning policy

[James Nord (jnord)]

If you require that functionality you will need to downgrade to an earlier 
version (I think 0.7.1).

The functionality will be coming back but I have no current ETA.
See https://issues.jenkins-ci.org/browse/JENKINS-11466

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Hilikus
Sent: 17 May 2013 16:50
To: jenkinsci-users@googlegroups.com
Subject: m2 release plugin versioning policy

Hello everyone,

It looks like the current behaviour when doing a maven release from jenkins in 
a multi-module project is to assign the version specified in the web ui of 
jenkins to ALL the submodules

e.g in a project like this

1.0.0-SNAPSHOT  (A)
   |...1.0.0-SNAPSHOT (A1)
   |...2.3.0-SNAPSHOT (A2)

if I specify in the ui that the version of the root pom (A in my example) 
should be 1.0.0 then even the second submodule (2.3.0-SNAPSHOT) will be 
released with version 1.0.0, probably due to the -B -DreleaseVersion arguments 
combo. Is there any way to change this behaviour? what I want is to release 
A1=1.0.0, A2=1.0.0 and A3=2.3.0

I see a "default versioning mode" in the configuration that seems to do just 
that; however, 1) it never keeps its state, whatever I change it to, it goes 
back to none 2) it doesn't even look like the actual behaviour is none, since 
none seems to be what I want. The behaviour I see is "specify one version for 
all modules"

I'm using m2release 0.10 and jenkins 1.460


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


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

RE: multi configuration project with different git branches

[James Nord (jnord)]

Your setup is more akin to requiring multiple jobs than a multi config job. As 
the source you want to build is different.
As it is different you will want to build only the branch that changed on any 
commit, not all of them.

Alternativly you can have a single normal job and have git checkout whichever 
branch changed - however I do not recommend this as trend reports become 
meaningless (and you may have different people maintinaing different branches 
and so want to change other settings like email notification etc.)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of kabustalek
Sent: 17 May 2013 08:38
To: jenkinsci-users@googlegroups.com
Subject: multi configuration project with different git branches

Hi

Can someone tell me whats the best way to checkout different git branches on a 
multi configuration project? i have a project (lets call it API) which has a 
java 1.6 branch and a java 1.7 branch, so i created a new multi configuration 
project with JDK1.6 and JDK1.7 (soon there will be a JDK1.8 i guess). how can i 
now configure the git checkout in jenkins to checkout a different branch 
regarding on the parameter? at the moment, jenkins always checks out the 1.6 
branch because the API project is configured to use ** as repository. 
Unfrotunately i can not define it on sub-project basis.

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


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

RE: Jenkins is extremely slow and takes 100% cpu

[James Nord (jnord)]

Your stack shows that Jenkins is trying to load all the builds looking for the 
last failed.

By any chance do you have a lot of jobs and a lot of history in these jobs?

https://issues.jenkins-ci.org/browse/JENKINS-16023

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Christian Petry
Sent: 16 May 2013 11:28
To: jenkinsci-users@googlegroups.com
Subject: Jenkins is extremely slow and takes 100% cpu

Hi,

i run jenkins with about 200 Jobs and working with it becomes quite painful. 
The overview page seems to take forever to load (about 4 minutes), and when 
jenkins is idle, it consumes 100% cpu.

I am using Jenkins 1.514

I have the following plugins installed:

  *   Ant Plugin
  *   Checkstyle Plugin
  *   Credentials Plugin
  *   Depenency Graph Plugin
  *   External Monitor Job Type Plugin
  *   Findbugs Plugin
  *   Javadoc Plugin
  *   Jenkins CVS Plugin
  *   Jenkins jQuery Plugin
  *   Jenkins Mailer Plugin
  *   Jenkins Sonar Plugin
  *   Jenkins SSH Slaves Plugin
  *   Jenkins Subversion Plugin
  *   Jenkins Translation Assistance Plugin
  *   LDAP Plugin
  *   Maven Ingtegration Plugin
  *   pam-auth
  *   PMD-Plugin
  *   SSh Credentials Plugin
  *   Static Analysis Collector Plugin
  *   Static Analysis Utilities
  *   View Job Filters
  *   Warnings Plug-ins
I have a TreadDump attached.

Jenkins runs in a virtual box on an Ubuntu Linux 12.04.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


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

RE: Subversion authentication issues

[James Nord (jnord)]

Ahh I should have looked more closely at the stack trace - sorry.

I have seen this happen when there is a proxy in between the server and the 
request for svnb goes via the proxy and svna goes direct.  (in which case it 
was the proxy denying the operation rather than the subversion server - and 
there where differences between Jenkins and the command line).   Other than 
that hopefully someone else may have some better ideas.

Regards,

/James


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Barbato
Sent: 03 May 2013 17:00
To: jenkinsci-users
Subject: Re: Subversion authentication issues

Hi James,

That's exactly where I'm trying to enter the credentials (well linked to by the 
config job page, but I just tried going directly to that URI too), and then 
getting the error I pasted when I submit it that page being 
${jenkinsURL}/scm/SubversionSCM/postCredential

Dan

On 3 May 2013 11:54, James Nord (jnord) 
mailto:jn...@cisco.com>> wrote:
HI Daniel,

Have you tried entering the credentials at 
${jenkinsURL}/scm/SubversionSCM/enterCredential ?

Althought the servers may use the same credentials the challenge that will be 
sent from the server will be for a different repository - and so Jenkins will 
probably not know anything about it and use what it knows which is nothing.

/James

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Daniel Barbato
Sent: 03 May 2013 16:44
To: jenkinsci-users
Subject: Subversion authentication issues

Hi,

I'm having some strange issues with subversion authentication within jenkins. 
My jenkins system and all plugins are fully up to date, jenkins master and 
nodes are all running Centos.

We have two different svn servers that Jenkins needs to be able to interact 
with, let's call them SVN-A and SVN-B. Both servers user the same credentials 
to authenticate.

>From the command line on each node and the master I'm able to successfully 
>authenticate and interact with both servers over https.

Within jenkins I'm able to successfully authenticate against SVN-A and have 
been for a long time. I'm trying to set up  authentication details for SVN-B, 
when I attempt the authentication from within Jenkins (using username / 
password) I constantly get a 403 Forbidden (full log below). Checking the SVN 
server logs, I can see no sign that any attempt has been made to authenticate.

Any advice is more than welcome!

Thanks In Advance!

Copy of trace from authentication attempt with server name and repo name 
obsured :)


Failed to authenticate: svn: E170001: OPTIONS of '/repo/svn/repo/core/trunk': 
403 Forbidden (https://SVN-B)

FAILED: svn: E175002: OPTIONS /repo/svn/repo/core/trunk failed

org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS 
/repo/svn/repo/core/trunk failed

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:628)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99)

at 
hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1939)

at 
hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1884)

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

at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)

at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)

at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)

at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)

at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)

at 
org.koh

RE: Subversion authentication issues

[James Nord (jnord)]

HI Daniel,

Have you tried entering the credentials at 
${jenkinsURL}/scm/SubversionSCM/enterCredential ?

Althought the servers may use the same credentials the challenge that will be 
sent from the server will be for a different repository - and so Jenkins will 
probably not know anything about it and use what it knows which is nothing.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Barbato
Sent: 03 May 2013 16:44
To: jenkinsci-users
Subject: Subversion authentication issues

Hi,

I'm having some strange issues with subversion authentication within jenkins. 
My jenkins system and all plugins are fully up to date, jenkins master and 
nodes are all running Centos.

We have two different svn servers that Jenkins needs to be able to interact 
with, let's call them SVN-A and SVN-B. Both servers user the same credentials 
to authenticate.

>From the command line on each node and the master I'm able to successfully 
>authenticate and interact with both servers over https.

Within jenkins I'm able to successfully authenticate against SVN-A and have 
been for a long time. I'm trying to set up  authentication details for SVN-B, 
when I attempt the authentication from within Jenkins (using username / 
password) I constantly get a 403 Forbidden (full log below). Checking the SVN 
server logs, I can see no sign that any attempt has been made to authenticate.

Any advice is more than welcome!

Thanks In Advance!

Copy of trace from authentication attempt with server name and repo name 
obsured :)


Failed to authenticate: svn: E170001: OPTIONS of '/repo/svn/repo/core/trunk': 
403 Forbidden (https://SVN-B)

FAILED: svn: E175002: OPTIONS /repo/svn/repo/core/trunk failed

org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS 
/repo/svn/repo/core/trunk failed

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:628)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018)

at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99)

at 
hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1939)

at 
hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1884)

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

at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)

at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)

at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)

at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)

at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)

at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)

at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)

at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)

at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)

at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)

at org.kohsuke.stapler.Stapler.service(Stapler.java:214)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)

at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)

at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)

at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)

at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)

at 
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)

at 
hudson.util.PluginServletFilter$1.doF

RE: Execute Clean Up on Build Cancel

[James Nord (jnord)]

Or you may be able to write a simple "build wrapper" plugin

http://javadoc.jenkins-ci.org/hudson/tasks/BuildWrapper.Environment.html#tearDown(hudson.model.AbstractBuild,
 
hudson.model.BuildListener)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of 
david.doug...@barclays.com
Sent: 03 May 2013 14:48
To: jenkinsci-users@googlegroups.com
Subject: RE: Execute Clean Up on Build Cancel

You will probably need to do something with a groovy system script; that would 
interact with the JVM that Jenkins runs in, you might be able to extract the 
information about the calling job, slave it ran on, etc.?

I can't recall if cancelling a job will generate the console log output on the 
Master (something worth checking), as that would contain the node which the job 
ran on. You could then do something with a rush/ssh (assuming you can deploy 
Cygwin or similar) to clean up the slave environment.


dD

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Paul Weiss
Sent: 03 May 2013 13:45
To: jenkinsci-users@googlegroups.com
Subject: Re: Execute Clean Up on Build Cancel


But how do you guarantee that the second job runs on the same slave as the 
first, unless you pin both jobs to a single slave?
On May 3, 2013 12:12 AM, "Martin Ba" 
<0xcdcdc...@gmx.at> wrote:
On 03.05.2013 03:36, Eric Blom wrote:
Hello Everyone,

We started using Jenkins about a year ago and have been very happy with it. We 
keep finding more way to use it! Some of our jobs use hardware connected to the 
slave and when that slave job is canceled we need to execute a clean up step, 
how can this be done?

I'm looking for a solution for both Linux and Windows. On Linux I've tried 
using the trap command, but, I can't find any signal that trap can trap. On 
windows I haven't found any solution yet.

...
Can anyone offer me some advice on how to implement a clean up on cancel for 
Linux and Windows?

Idea: Move the cleanup to a second job that you run downstream from the first 
one. You start the second job always ("Complete (always trigger)") and it will 
run even when the first job was aborted.

And if you use the parameterized trigger plugin and load the parameters for 
job#2 from a file, you can have it starting depend on the file existing. 
("Don't trigger if any files are missing.")

cheers,
Martin

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



This e-mail and any attachments are confidential and intended solely for the 
addressee and may also be privileged or exempt from disclosure under applicable 
law. If you are not the addressee, or have received this e-mail in error, 
please notify the sender immediately, delete it from your system and do not 
copy, disclose or otherwise act upon any part of this e-mail or its attachments.

Internet communications are not guaranteed to be secure or virus-free.
The Barclays Group does not accept responsibility for any loss arising from 
unauthorised access to, or interference with, any Internet communications by 
any third party, or from the transmission of any viruses. Replies to this 
e-mail may be monitored by the Barclays Group for operational or business 
reasons.

Any opinion or other information in this e-mail or its attachments that does 
not relate to the business of the Barclays Group is personal to the sender and 
is not given or endorsed by the Barclays Group.

Barclays Bank PLC.Registered in England and Wales (registered no. 1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.

Barclays Bank PLC is authorised and regulated by the Financial Services 
Authority.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 

RE: Changelog for LTS versions?

[James Nord (jnord)]

http://jenkins.361315.n4.nabble.com/Another-LTS-release-needed-td4652460.html 
implies it is already in 1.480.3 but not noted in the changelog?

If not the next LTS is probably out in a couple of weeks and will be based off 
a mainline that includes this fix.

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Les Mikesell
> Sent: 30 April 2013 18:04
> To: jenkinsci-users
> Subject: Re: Changelog for LTS versions?
> 
> On Tue, Apr 30, 2013 at 11:15 AM, James Nord (jnord) 
> wrote:
> >
> > The LTS changelog is at
> > http://jenkins-ci.org/changelog-stable
> >
> > any backports from later mainline versions mentioned for the first (.1)
> release.
> >
> 
> Thanks!   Any idea when a release might include the fix in issue 15466?
> 
> --
>Les Mikesell
>  lesmikes...@gmail.com
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 

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

RE: Changelog for LTS versions?

[James Nord (jnord)]

Hi Les,

The LTS changelog is at 
http://jenkins-ci.org/changelog-stable

any backports from later mainline versions mentioned for the first (.1) release.

Regards,

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Les Mikesell
> Sent: 30 April 2013 16:16
> To: jenkinsci-users
> Subject: Changelog for LTS versions?
> 
> What is the best way to track the changes in the LTS releases?   I'm
> seeing the problem where workspace files can't be deleted:
> https://issues.jenkins-ci.org/browse/JENKINS-15466
> but don't know how to tell when/if the change happened for LTS versions.
> 
> Also, I recall being surprised when a security-related fix announced for a 
> later
> non-LTS release appeared in an earlier-numberd LTS version.  Is there a
> separate changelog that shows the different changes going into the LTS
> versions?
> 
> --
>Les Mikesell
>  lesmikes...@gmail.com
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 

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

RE: [M2Release] MAVEN RELEASE - SVN 403 Forbidden

[James Nord (jnord)]

The only difference I see between what is working on my environment is the 
servers used to copy from and to are different.

One will come from where Jenkins has checked out from, the other will come from 
your pom.

Although "mydomain" and 192.168.30.48 are very possibly the same machine you 
could try changing Jenkins/pom.xml so they are both identical.
(I recommend using the fully qualified domain name)

Other than that - I am not an expert on WebDAV and don't know if not hading 
access at the root of the repo would/should/could block that user being able to 
create the tag.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Angelo Scaldaferri
Sent: 30 April 2013 13:12
To: jenkinsci-users@googlegroups.com
Subject: Re: [M2Release] MAVEN RELEASE - SVN 403 Forbidden

I understand what you mean, but in my configuration I've already specified the 
user and password that have to be passed to the maven release plugin, in fact 
these are visible in the log file, as you can see:

[LOG]
Executing Maven:  -B -f /opt/...thepath.../pom.xml 
-DdevelopmentVersion=1.2.31-SNAPSHOT -DreleaseVersion=1.2.30 
-Dusername=myusername -Dpassword=* 
-DscmCommentPrefix=[maven-release-plugin] -Dtag=1.2.30 -Dresume=false 
release:prepare release:perform
[/LOG]

I suspect that Jenkins try to reach the root of the svn folder in the 
release:prepare phase with the user that I've specified, but this user can see 
only the leaf of the project and not the root of the company's svn...

svn --username myusername --password '*' --no-auth-cache --non-interactive 
copy --file /tmp/maven-scm-1426693027.commit --revision 26982 
http://mydomain/svn/svnroot/myproject/trunk 
http://192.168.30.48/svn/svnroot/myproject/tag/1.2.30

>> in response to PROPFIND request for '[root_dir_svn]'


Regards
Angelo

Il giorno lunedì 29 aprile 2013 22:56:56 UTC+2, teilo ha scritto:
The release process will use the authentication available to the subversion 
command line client when run as the user that Jenkins runs as on the slave.

If you have not told the release plugin otherwise it won't pass a user to the 
svn client either, so if Jenkins is running as root it will try and create the 
tag as the root user.

It sounds like you need to use a user other than root and if you don't want to 
have to specify a username/password eachtime then you can add -Dusername=myuser 
to the real ease goals and put the password for this used in the subversion 
credential cache (this is not the Jenkins svn credential store)
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


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

RE: M2 Release Plugin configuration does NOT appear in my job

[James Nord (jnord)]

HI Eric,

The plugin only works with the m2/3 job type - so this is expected[1].

Regards,

/James

[1] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Eric Turley
Sent: 08 April 2013 17:55
To: jenkinsci-users@googlegroups.com
Subject: Re: M2 Release Plugin configuration does NOT appear in my job

Update: Creating a new Job from the "maven2/3 project" template *DOES* provide 
the option.
However, creating a new "free-style" job does not.
More importantly, editing a job I currently have (which is building via maven 
as a build step) does *NOT* provide the option.

On Monday, April 8, 2013 11:50:16 AM UTC-5, Eric Turley wrote:

I've installed the plugin, and restarted Jenkins.

But for both existing and new jobs, my Build Environment section does not 
contain the "Maven release build" option as indicated at 
https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin

What am I missing?

Here's a pic of the job I'm trying to build.

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


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


<>

RE: Antwort: Installing operating systems on slaves via Jenkins

[James Nord (jnord)]

I recall you can accomplish cleaning a slave with one of the cloud plugins -you 
create a new slave on the fly from a template and destroy it after a job.  But 
I don't recall which of the cloudy plugins it was and so will depend on what 
your VM tech is.

The alternative as Andreas suggested is to not have the tests run on the slave 
but on a separate VM and have that controlled by Jenkins.  We do this using the 
CLoudbees paid VMWare autoscaling plugin, but there may now be other free 
plugins that perfrom a similar job.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Andreas Schilling
Sent: 30 January 2013 10:31
To: jenkinsci-users@googlegroups.com
Subject: Antwort: Installing operating systems on slaves via Jenkins

Hi Manish,

the very simple answer is: you can't do this.
A slave is not sort of "remote controlled" in the sense of performing any 
operation on it you could imagine. Even if you could manage to trigger a OS 
installation on it: how should the Master communicate with it afterwards? You 
would burn the bridge you're standing on.
What I *could* imagine to do is to perform the tests on a VM and to somehow 
trigger the VM host to start from a fresh VM image every time you execute the 
test. But I'm no expert on that sort of stuff in any way so I have no clue 
whether you could trigger that sort of stuff in a headless manner at all.

A very basic question of course must be asked as well: isn't there a flaw in 
your test process if you need a complete fresh OS to run it? Then again, I have 
no idea what you are actually testing so of course there might be good reasons 
to do so.

Kind regards,

Andreas Schilling
CAE Processes & Data Management
---
Dipl. Inf. Andreas Schilling
Senior Software Architect

TWT GmbH
Science & Innovation
Bernhäuser Str. 40 - 42
73765 Neuhausen

Tel: +49.7158.17 15.6 73
Mobil: +49.1 72.6 22 88 70
E-Mail: andreas.schill...@twt-gmbh.de

www.twt-gmbh.de

Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (Stv.), Frank 
Beutenmüller (Stv.)
Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778
Umsatzsteuer: ID-Nr.: DE147841145




Von:Manish Singh mailto:munsi...@gmail.com>>
An:
jenkinsci-users@googlegroups.com
Datum:30.01.2013 11:12
Betreff:Installing operating systems on slaves via Jenkins
Gesendet von:
jenkinsci-users@googlegroups.com




Hello All,

I have a requirement, where I need to reinstall OS on slave machines before a 
job is executed. This is needed as we need a clean OS before executing the 
tests.

What are the best ways to do this via Jenkins?

-Manish

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


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