Jenkins User Conference 2015 - Washington DC & London

[Alyssa Tong]

Hi All,

If you're on the East Coast or London area, pls join Kohsuke Kawaguchi and
many other prominent Jenkins community members at the Jenkins User
Conference  in Washington DC
and London in June.

Agendas for both cities are available and seatings are filling up fast.

For a limited time only, there's a* 2 for 1 special*. Register with a
friend or colleague and get the second ticket for FREE! that's a $299/299
GBP saving! Offer expires May 15 (No discount code needed).

*JUC Washington  - June
18 & 19. REGISTER HERE
*

*JUC London  - June 23 &
24. REGISTER HERE
*

Hope to see you there.

alyssa

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAC9wNaxV9-bq0gy-xWyi6LDyvp%3Dovy7AJNNsS04FzXtuVWByOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Using Groovy 2.x to run scripts in Jenkins' context

[Marcin Zajączkowski]

Hi,

I heavily use job-dsl-plugins to provision and manage jobs in Jenkins and 
it would be useful to be able to use Groovy 2.x features (like traits or 
static compilation) to write that code. Jenkins has embedded Groovy 1.8.9 
(which as a line 1.8 is quite old) which is used to run job-dsl-plugins 
scripts (and other context aware scripts like System Groovy Script from 
Groovy plugin).

Two question:
1. Is it possible to use newer Groovy version to run scripts in Jenkins' 
context?
2. If not, is it planned to upgrade Groovy provided in Jenkins (which 
unfortunately could brings some compatibility issues, but rather it has to 
be performed sooner or later anyway)?

Marcin

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/265c23ca-e8ff-44f0-b8bf-e058ce035ed0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: JENKINS REST API: queue service responds “404 not found”

[Baptiste Mathus]

As Vincent said, known issue. Did you click on the link above? I suppose
you did, obviously.
Reading the changelog: https://jenkins-ci.org/changelog you'll learn that
fix has been included in 1.605.

Cheers
Le 6 mai 2015 11:00 PM, "harperville"  a écrit :

> Hi, Vincent.  I'm confused.  I'm running 1.604 and a script that
> previously worked fails with a 404 when I'm trying to hit this endpoint.  A
> little help?
>
> On Friday, March 20, 2015 at 9:57:18 AM UTC-4, Vincent Latombe wrote:
>>
>> Hi,
>>
>> this is a known issue, see
>> https://issues.jenkins-ci.org/browse/JENKINS-27256
>>
>> Vincent
>>
>> 2015-03-20 14:24 GMT+01:00 Albert Battle :
>>
>>> I am using the latest JENKINS version 1.605.
>>>
>>> I start a job by issuing /POST /jenkins/job/jobName/build
>>>
>>> I receive a location header Location: http://
>>> {host}/jenkins/queue/item/3/
>>>
>>> Issuing /GET http://{host}/jenkins/queue/item/3/ I receive 404
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAGVYvSPmsTAN0C-Q-z6UDMoAHP_S%3Dm6N0XNWnGMvt6ZDt4Pvvw%40mail.gmail.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/e67a2e07-5b5a-4863-9512-69a76a0f4578%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5eRBhJp9oGKNBHVHtGQpt7vJOeyqwnfoWM%2BoKL1BLRmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JENKINS REST API: queue service responds “404 not found”

[harperville]

Hi, Vincent.  I'm confused.  I'm running 1.604 and a script that previously 
worked fails with a 404 when I'm trying to hit this endpoint.  A little 
help?

On Friday, March 20, 2015 at 9:57:18 AM UTC-4, Vincent Latombe wrote:
>
> Hi,
>
> this is a known issue, see 
> https://issues.jenkins-ci.org/browse/JENKINS-27256
>
> Vincent
>
> 2015-03-20 14:24 GMT+01:00 Albert Battle 
> >:
>
>> I am using the latest JENKINS version 1.605.
>>
>> I start a job by issuing /POST /jenkins/job/jobName/build
>>
>> I receive a location header Location: http://{host}/jenkins/queue/item/3/
>>
>> Issuing /GET http://{host}/jenkins/queue/item/3/ I receive 404
>>
>> -- 
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CAGVYvSPmsTAN0C-Q-z6UDMoAHP_S%3Dm6N0XNWnGMvt6ZDt4Pvvw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e67a2e07-5b5a-4863-9512-69a76a0f4578%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Display a field from every job

[Baptiste Mathus]

The simplest way is to use some groovy code. Look for Jenkins groovy on
Google and it should get you going.

If you want something clean and durable, then you want to go for adding the
support for that field in the configuration slicing plugin (which I suppose
doesn't support that right now).

Cheers
Le 6 mai 2015 12:10 AM, "zippo7061"  a écrit :

> We are alway incrementing our release numbers.  I"d like to display the
> tfs source location of all jobs in a view so we can easlity make sure each
> job is pointing ot the right location. How can i do this?  Thank you in
> advance
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/7144fddb-6a0e-4e60-add7-355049eba18d%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4VJ6sdNg8y-mY%3DhqR5Q_thuQZArxtn%2BN0BOAksnSScyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Make jenkins checkout using cvs over ssh with given port

[tps800]

Hi!

trying to checkout a cvs-repository using transport over ssh with port 
2022. If I give it on a command line (/bin/sh):

{
export CVSROOT=anoncvs@:/cvs
export CVS_RSH=$HOME/bin/SSH
cvs -q get -P src
}

with { $HOME/bin/SSH }:
{
ssh -p 2022 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no $@
}

Will do what I expect: checkout src.

I've tried to use:
{
export CVSROOT=:ssh:anoncvs@:2022/cvs
cvs -q get -P src
}

but it does not work at all. Looks like it wants an ssh-key to access.
So here is my question: how do I have to set up jenkins cvs to have the 
checkout running, using ssh and port 2022?

Thanks in advance for any hint!

-- 
Thomas

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1848e99a-d420-409e-854f-bc6b22025c84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Git repository connection times out sometimes

[Dunnigan, Terrence J]

Hi,

I’m also encountering that very error. It seems to happen at random on various 
nodes.

Building remotely on Goku in workspace C:\Hudson_remote\workspace\code.git
> C:\Program Files (x86)\Git\cmd\git.exe rev-parse --is-inside-work-tree # 
> timeout=120
Fetching changes from the remote Git repository
> C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url 
> git@server:code # timeout=120
ERROR: Error fetching remote repo 'origin'
ERROR: Error fetching remote repo 'origin'

I’m using Jenkins LTS 1.544.3 on a Windows 2008 server running Java 7.
Git plugin 2.2.9
Git client plugin 1.12.0
The nodes are all running Windows 7, Java 7, and either 1.8.3 or git 1.9.5.

Terry

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of web-deploy
Sent: Wednesday, May 06, 2015 11:33 AM
To: jenkinsci-users@googlegroups.com
Cc: jennifer.hofmeis...@younicos.com
Subject: Re: Git repository connection times out sometimes

Hi,
I haven't encountered similar problem starting last week. Our Jenkins master 
and slaves both run on Linux tho.

...
ERROR: Timeout after 10 minutes
ERROR: Error cloning remote repo 'origin'
ERROR: Error cloning remote repo 'origin'
Retrying after 10 seconds
...

Anyone has any ideas?

On Wednesday, April 22, 2015 at 1:59:32 AM UTC-7, Jennifer Hofmeister wrote:
Hi,

just to thank everyone for your ideas and to give an update:

It was no network issue, everything looked clean on that side. Also, it was no 
git client issue on the Jenkins master side, I updated it along with the plugin 
with no effect. (Although on the repository side, it was 1.7.11.8 … so, ancient 
… no idea if that caused any trouble. Didn’t want to meddle on that system yet, 
though.)

Somehow, the server side didn’t want the master’s Git SSH key anymore. So I 
tried things out on my own system, where it worked, and copied my keys to the 
Git/.ssh directory on Jenkins master. That fixed the connection, but the 
Jenkins job still would not work compared to the command line. Since the only 
difference between these two is that the Jenkins job, running as a service, 
starts Git as SYSTEM, and cmd starts it as USER, I reconfigured the Jenkins 
service to run as USER. Problem solved for me.

Thanks for everything, though, it helped me learn a lot!

Jennifer

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Dunnigan, 
Terrence J
Sent: Freitag, 17. April 2015 18:09
To: jenkins...@googlegroups.com
Subject: RE: Git repository connection times out sometimes

I noticed the improvement in 1.9.5, but looking at the release notes it appears 
that the upgrades have been happening for a while.

https://github.com/msysgit/msysgit/releases/tag/Git-1.9.5-preview20150319
https://github.com/msysgit/msysgit/releases/tag/Git-1.9.4-preview20140815

On git 1.8.3:
$ ssh -v
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007

On git 1.9.5:
$ ssh -V
OpenSSH_6.6.1p1, OpenSSL 1.0.1i 6 Aug 2014

Yay to the git team!

Terry

From: jenkins...@googlegroups.com 
[mailto:jenk...@googlegroups.com] On Behalf Of Mark Waite
Sent: Friday, April 17, 2015 10:49 AM
To: jenkins...@googlegroups.com
Subject: Re: Git repository connection times out sometimes

I wasn't aware that the msysgit team had been able to upgrade to a newer 
version of ssh.

https://groups.google.com/forum/#!topic/msysgit/EqyLxeHudqc

describes the approximately 1 MB/second bandwidth limit when cloning over 
OpenSSH using msysgit.  Cloning with msysgit over PuTTY plink does not have 
that limitation.  Cloning with mssygit over git protocol does not have that 
limitation.  Cloning with msysgit over https or http does not have that 
limitation.

Mark Waite

On Fri, Apr 17, 2015 at 7:58 AM, Dunnigan, Terrence J 
> wrote:
Your job runs on the Jenkins master server.

What version of the git client do you have installed on your Jenkins master?

I have seen issues where earlier versions of git for Windows (pre-1.9.5) will 
hang during routine operations like git fetch. I’ve seen this happen both at my 
desk and in our Jenkins ecosystem.

The workaround pre-1.9.5 was to install Putty and set the GIT_SSH environment 
variable to use Putty’s plink.exe.

With git 1.9.5 they have seemingly improved performance such that using Putty 
is no longer necessary.

Terry

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Jennifer 
Hofmeister
Sent: Thursday, April 16, 2015 4:38 AM
To: jenkins...@googlegroups.com
Subject: Git repository connection times out sometimes

Hello,

I have several build jobs that clone from a remote Git repository. On some of 
them, the git fetch part of the command fails with the following output:

Building on master in workspace C:\Program Files 
(x86)\Jenkins\jobs\test_123\workspace
> git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git.exe config remote.origin.url 
> ssh://g...@stash.mycompany.com:port/path/test-project1.git # timeout=10

Re: Git repository connection times out sometimes

[web-deploy]

Hi,

I have encountered same problem starting last week. My Jenkins master and 
slaves are running on linux tho.

...
ERROR: Timeout after 10 minutes
ERROR: Error cloning remote repo 'origin'
ERROR: Error cloning remote repo 'origin'
Retrying after 10 seconds
...



On Wednesday, April 22, 2015 at 1:59:32 AM UTC-7, Jennifer Hofmeister wrote:
>
>  Hi,
>
>  
>
> just to thank everyone for your ideas and to give an update: 
>
>  
>
> It was no network issue, everything looked clean on that side. Also, it 
> was no git client issue on the Jenkins master side, I updated it along with 
> the plugin with no effect. (Although on the repository side, it was 
> 1.7.11.8 … so, ancient … no idea if that caused any trouble. Didn’t want to 
> meddle on that system yet, though.) 
>
>  
>
> Somehow, the server side didn’t want the master’s Git SSH key anymore. So 
> I tried things out on my own system, where it worked, and copied my keys to 
> the Git/.ssh directory on Jenkins master. That fixed the connection, but 
> the Jenkins job still would not work compared to the command line. Since 
> the only difference between these two is that the Jenkins job, running as a 
> service, starts Git as SYSTEM, and cmd starts it as USER, I reconfigured 
> the Jenkins service to run as USER. Problem solved for me. 
>
>  
>
> Thanks for everything, though, it helped me learn a lot!
>
>  
>
> Jennifer
>
>  
>  
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Dunnigan, 
> Terrence J
> *Sent:* Freitag, 17. April 2015 18:09
> *To:* jenkins...@googlegroups.com 
> *Subject:* RE: Git repository connection times out sometimes
>  
>  
>
> I noticed the improvement in 1.9.5, but looking at the release notes it 
> appears that the upgrades have been happening for a while.
>
>  
>
> https://github.com/msysgit/msysgit/releases/tag/Git-1.9.5-preview20150319 
>
> https://github.com/msysgit/msysgit/releases/tag/Git-1.9.4-preview20140815
>
>  
>
> On git 1.8.3:
>
> $ ssh -v
>
> OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
>
>  
>
> On git 1.9.5:
>
> $ ssh -V
>
> OpenSSH_6.6.1p1, OpenSSL 1.0.1i 6 Aug 2014
>
>  
>
> Yay to the git team!
>
>  
>
> Terry
>
>  
>
> *From:* jenkins...@googlegroups.com  [
> mailto:jenk...@googlegroups.com ] *On Behalf Of *Mark Waite
> *Sent:* Friday, April 17, 2015 10:49 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: Git repository connection times out sometimes
>
>  
>  
> I wasn't aware that the msysgit team had been able to upgrade to a newer 
> version of ssh.
>  
>  
>  
> https://groups.google.com/forum/#!topic/msysgit/EqyLxeHudqc
>  
>  
>  
> describes the approximately 1 MB/second bandwidth limit when cloning over 
> OpenSSH using msysgit.  Cloning with msysgit over PuTTY plink does not have 
> that limitation.  Cloning with mssygit over git protocol does not have that 
> limitation.  Cloning with msysgit over https or http does not have that 
> limitation.
>  
>  
>  
> Mark Waite
>   
>  
>  
> On Fri, Apr 17, 2015 at 7:58 AM, Dunnigan, Terrence J <
> terrence@boeing.com > wrote:
>
>  Your job runs on the Jenkins master server.
>
>  
>
> What version of the git client do you have installed on your Jenkins 
> master?
>
>  
>
> I have seen issues where earlier versions of git for Windows (pre-1.9.5) 
> will hang during routine operations like git fetch. I’ve seen this happen 
> both at my desk and in our Jenkins ecosystem.
>
>  
>
> The workaround pre-1.9.5 was to install Putty and set the GIT_SSH 
> environment variable to use Putty’s plink.exe. 
>
>  
>
> With git 1.9.5 they have seemingly improved performance such that using 
> Putty is no longer necessary.
>
>  
>
> Terry
>
>  
>  
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Jennifer 
> Hofmeister
> *Sent:* Thursday, April 16, 2015 4:38 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Git repository connection times out sometimes
>  
>  
>
> Hello,
>  
>  
>
> I have several build jobs that clone from a remote Git repository. On some 
> of them, the git fetch part of the command fails with the following 
> output:
>
>  
>
> Building on master in workspace C:\Program Files 
> (x86)\Jenkins\jobs\test_123\workspace
>
> > git.exe rev-parse --is-inside-work-tree # timeout=10
>
> Fetching changes from the remote Git repository
>
> > git.exe config remote.origin.url 
> ssh://g...@stash.mycompany.com:port/path/test-project1.git # timeout=10
>
> Fetching upstream changes from 
> ssh://g...@stash.mycompany.com:port/path/test-project1.git
>
> > git.exe --version # timeout=10
>
> > git.exe -c core.askpass=true fetch --tags --progress 
> ssh://g...@stash.mycompany.com:port/path/test-project1.git 
> +refs/heads/*:refs/remotes/origin/* # timeout=10
>
> ERROR: Timeout after 10 minutes
>
> ERROR: Error fetching remote repo 'origin'
>
> ERROR: Error fetching remote repo 'origin'
>
>  
>
> I get no more information. The process doesn’t get rejected by Stash, it 
> just 

Re: [workflow-plugin] Set build description

[Christoph Vogtländer]

You can use
currentBuild.setDescription("Your Description")

Christoph

Am 25.03.2015 18:52, schrieb Lóránt Pintér:

Hi,

Is there a way to set the description of a workflow build from a
workflow script?

Thanks,
Lorant

 --
 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.
 To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/efedf121-b274-40ed-8e6a-d0c73e4e1e94%40googlegroups.com
[1].
 For more options, visit https://groups.google.com/d/optout [2].


Links:
--
[1]
https://groups.google.com/d/msgid/jenkinsci-users/efedf121-b274-40ed-8e6a-d0c73e4e1e94%40googlegroups.com?utm_medium=email&utm_source=footer
[2] 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/764f60768b1b21e9dbfafa058474e06e%40kfpc.de.
For more options, visit https://groups.google.com/d/optout.

Re: Git repository connection times out sometimes

[web-deploy]

Hi,
I haven't encountered similar problem starting last week. Our Jenkins 
master and slaves both run on Linux tho.

...
ERROR: Timeout after 10 minutes
ERROR: Error cloning remote repo 'origin'
ERROR: Error cloning remote repo 'origin'
Retrying after 10 seconds
...

Anyone has any ideas?

On Wednesday, April 22, 2015 at 1:59:32 AM UTC-7, Jennifer Hofmeister wrote:
>
>  Hi,
>
>  
>
> just to thank everyone for your ideas and to give an update: 
>
>  
>
> It was no network issue, everything looked clean on that side. Also, it 
> was no git client issue on the Jenkins master side, I updated it along with 
> the plugin with no effect. (Although on the repository side, it was 
> 1.7.11.8 … so, ancient … no idea if that caused any trouble. Didn’t want to 
> meddle on that system yet, though.) 
>
>  
>
> Somehow, the server side didn’t want the master’s Git SSH key anymore. So 
> I tried things out on my own system, where it worked, and copied my keys to 
> the Git/.ssh directory on Jenkins master. That fixed the connection, but 
> the Jenkins job still would not work compared to the command line. Since 
> the only difference between these two is that the Jenkins job, running as a 
> service, starts Git as SYSTEM, and cmd starts it as USER, I reconfigured 
> the Jenkins service to run as USER. Problem solved for me. 
>
>  
>
> Thanks for everything, though, it helped me learn a lot!
>
>  
>
> Jennifer
>
>  
>  
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Dunnigan, 
> Terrence J
> *Sent:* Freitag, 17. April 2015 18:09
> *To:* jenkins...@googlegroups.com 
> *Subject:* RE: Git repository connection times out sometimes
>  
>  
>
> I noticed the improvement in 1.9.5, but looking at the release notes it 
> appears that the upgrades have been happening for a while.
>
>  
>
> https://github.com/msysgit/msysgit/releases/tag/Git-1.9.5-preview20150319 
>
> https://github.com/msysgit/msysgit/releases/tag/Git-1.9.4-preview20140815
>
>  
>
> On git 1.8.3:
>
> $ ssh -v
>
> OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
>
>  
>
> On git 1.9.5:
>
> $ ssh -V
>
> OpenSSH_6.6.1p1, OpenSSL 1.0.1i 6 Aug 2014
>
>  
>
> Yay to the git team!
>
>  
>
> Terry
>
>  
>
> *From:* jenkins...@googlegroups.com  [
> mailto:jenk...@googlegroups.com ] *On Behalf Of *Mark Waite
> *Sent:* Friday, April 17, 2015 10:49 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: Git repository connection times out sometimes
>
>  
>  
> I wasn't aware that the msysgit team had been able to upgrade to a newer 
> version of ssh.
>  
>  
>  
> https://groups.google.com/forum/#!topic/msysgit/EqyLxeHudqc
>  
>  
>  
> describes the approximately 1 MB/second bandwidth limit when cloning over 
> OpenSSH using msysgit.  Cloning with msysgit over PuTTY plink does not have 
> that limitation.  Cloning with mssygit over git protocol does not have that 
> limitation.  Cloning with msysgit over https or http does not have that 
> limitation.
>  
>  
>  
> Mark Waite
>   
>  
>  
> On Fri, Apr 17, 2015 at 7:58 AM, Dunnigan, Terrence J <
> terrence@boeing.com > wrote:
>
>  Your job runs on the Jenkins master server.
>
>  
>
> What version of the git client do you have installed on your Jenkins 
> master?
>
>  
>
> I have seen issues where earlier versions of git for Windows (pre-1.9.5) 
> will hang during routine operations like git fetch. I’ve seen this happen 
> both at my desk and in our Jenkins ecosystem.
>
>  
>
> The workaround pre-1.9.5 was to install Putty and set the GIT_SSH 
> environment variable to use Putty’s plink.exe. 
>
>  
>
> With git 1.9.5 they have seemingly improved performance such that using 
> Putty is no longer necessary.
>
>  
>
> Terry
>
>  
>  
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Jennifer 
> Hofmeister
> *Sent:* Thursday, April 16, 2015 4:38 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Git repository connection times out sometimes
>  
>  
>
> Hello,
>  
>  
>
> I have several build jobs that clone from a remote Git repository. On some 
> of them, the git fetch part of the command fails with the following 
> output:
>
>  
>
> Building on master in workspace C:\Program Files 
> (x86)\Jenkins\jobs\test_123\workspace
>
> > git.exe rev-parse --is-inside-work-tree # timeout=10
>
> Fetching changes from the remote Git repository
>
> > git.exe config remote.origin.url 
> ssh://g...@stash.mycompany.com:port/path/test-project1.git # timeout=10
>
> Fetching upstream changes from 
> ssh://g...@stash.mycompany.com:port/path/test-project1.git
>
> > git.exe --version # timeout=10
>
> > git.exe -c core.askpass=true fetch --tags --progress 
> ssh://g...@stash.mycompany.com:port/path/test-project1.git 
> +refs/heads/*:refs/remotes/origin/* # timeout=10
>
> ERROR: Timeout after 10 minutes
>
> ERROR: Error fetching remote repo 'origin'
>
> ERROR: Error fetching remote repo 'origin'
>
>  
>
> I get no more information. The process doesn’t get reject

Re: Git Publisher: EnvVar in tag name

[Sverre Moe]

Anyone has any idea how I can get my build environment variables over to 
the matrix parent?

tirsdag 5. mai 2015 10.59.15 UTC+2 skrev Sverre Moe følgende:
>
> It seems there is an registered JIRA issue for this problem
> https://issues.jenkins-ci.org/browse/JENKINS-15507
>
> Its 3 years old, it has not been fixed, nor updated for a year.
>
> tirsdag 5. mai 2015 09.16.23 UTC+2 skrev Sverre Moe følgende:
>>
>> I found the reason, but still not the solution.
>>
>> My projects are Multi-configuration jobs. My injected environment 
>> variables are available during both build and post-build, for each matrix 
>> axis, but not the matrix parent. The Git Publisher works on the matrix 
>> parent, and it seems like the environment variables are not available there.
>>
>> How can I get the Matrix parent to also get the environment variables?
>>
>> tirsdag 5. mai 2015 08.58.14 UTC+2 skrev Sverre Moe følgende:
>>>
>>> Something strange:
>>> I am using Inject Environment Variables, "Inject environment variables 
>>> to the following build steps and post-build actions".
>>> The variables injected from a "Properties File" are not accessible 
>>> during the post-build phase, but those I declare within "Properties 
>>> Content" are.
>>>
>>> tirsdag 5. mai 2015 08.47.32 UTC+2 skrev Sverre Moe følgende:

 I can create a Git tag using other environment variables such as 
 BUILD_TAG, but why isn't my own environment variables available during the 
 publish stage. My own environment variables are available during the build 
 stage.

 mandag 4. mai 2015 10.26.05 UTC+2 skrev Sverre Moe følgende:
>
> I am trying to use Git Publisher to create a git tag, but I cannot get 
> it to use an Environment variable in the tag name:
>
> Is it even possible to supply an Environment Variable as part of a Git 
> tag name?
>
>  > git tag -l v$VERSION # timeout=10
>  > git tag -a -f -m Jenkins Git plugin tagging with v$VERSION 
> v$VERSION # timeout=10
> Pushing tag v$VERSION to repo origin
>  > git --version # timeout=10
>  > git -c core.askpass=true push ssh://
> g...@git.company.com/packages/myLib.git v$VERSION
> ERROR: Failed to push tag v$VERSION to origin
> hudson.plugins.git.GitException: Command "git -c core.askpass=true 
> push ssh://g...@git.company.com/packages/myLib.git v$VERSION" returned 
> status code 1:
> stdout: 
> stderr: remote: invalid characters in ref or filename: 
> refs/tags/v$VERSION
> remote: error: hook declined to update refs/tags/v$VERSION
> To ssh://g...@git.company.com/packages/myLib.git
>  ! [remote rejected] v$VERSION -> v$VERSION (hook declined)
> error: failed to push some refs to 'ssh://
> g...@git.company.com/packages/myLib.git'
>
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
> at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1663)
> at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
> at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
> at hudson.remoting.UserRequest.perform(UserRequest.java:121)
> at hudson.remoting.UserRequest.perform(UserRequest.java:49)
> at hudson.remoting.Request$2.run(Request.java:325)
> at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at ..remote call to Development-openSUSE-x86_64(Native Method)
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360)
> at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
> at hudson.remoting.Channel.call(Channel.java:753)
> at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at 
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
> at com.sun.proxy.$Proxy87.execute(Unknown Source)
> at hudson.plugins.git.GitPu

Can we restrict some job config fields from update operations

[Samith Dassanayake]

Hi all,
Once we create a job, can we restrict some particular fields, for update 
using "Fetch/Update config.xml" rest endpointI.
For example assume my job config is like below and I want to restrict 
changes to "*description*"  field using rest api



<*description*>deploys to cloud instance
false


true
false

false
false

false


echo "deploying to prod"






Thanks,
Samith

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/26232936-0e83-4426-b002-c3d5afb4a6ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

App extension crashed the simulator

[irm emc]

Hello everyone,

We use Jenkins to do automation tests for an iOS Application. This iOS 
Application contains an App Extension. We install xctool to do the 
automation tests.

But the simulator crashed before any test can start. The crash report shows 
that the init function of the App Extension causes the crash. Note that we 
didn't call anything of the App Extension, and we did not test the App 
Extension yet in our automation tests. The automation tests run 
successfully inside xCode. But it has trouble to run from Jenkins using 
xctool.

It is a DocumentProvider application extension. The crash is inside the 
documentStorageURL 
system call as shown in the crash log below.

Now my questions:
1) When we do automation tests from Jenkins, shall the App Extension be 
involved? It seems to me that the init function of the App Extension shall 
not be called at all. Who is calling this function?
2) Did anyone try to do automation test from Jenkins for an Application 
with App Extension? Does this even work?

Thanks in advance.

=== Crash report from xctool in Jenkins Console Output 

Test did not run: the test bundle stopped running or crashed before the test 
suite started.

CRASH REPORT: 
DocumentProviderFileProvider_2015-05-05-131153_mobile-build-machine.crash

Process:   DocumentProviderFileProvider [60158]
Path:  ... (removed)
Identifier:DocumentProviderFileProvider
Version:   0
Code Type: X86 (Native)
Parent Process:launchd_sim [59866]
Responsible:   launchd_sim [59866]
User ID:   501

Date/Time: 2015-05-05 13:11:20.422 -0700
OS Version:Mac OS X 10.10.2 (14C109)
Report Version:11
Anonymous UUID:FC4346E1-3FDE-69F9-791D-694DCD170BF7


Time Awake Since Boot: 180 seconds

Crashed Thread:0  Dispatch queue: NSFileProviderExtension member sync 
queue

Exception Type:EXC_CRASH (SIGABRT)
Exception Codes:   0x, 0x

Application Specific Information:
abort() called
CoreSimulator 117.5.4 - Device: iPad 2 - Runtime: iOS 8.1 (12B411) - 
DeviceType: iPad 2

Thread 0 Crashed:: Dispatch queue: NSFileProviderExtension member sync queue
0   libsystem_kernel.dylib  0x03bb669a __pthread_kill + 10
1   libsystem_pthread.dylib 0x03be4f19 pthread_kill + 101
2   libsystem_sim_c.dylib   0x0396ea5a abort + 156
3   DocumentProviderFileProvider0x00266a1f uncaught_exception_handler + 
38
4   com.apple.CoreFoundation0x02fced80 __handleUncaughtException + 
832
5   libobjc.A.dylib 0x021fbd3d _objc_terminate() + 100
6   libc++abi.dylib 0x03792cf0 std::__terminate(void (*)()) 
+ 14
7   libc++abi.dylib 0x03792d72 std::terminate() + 66
8   libobjc.A.dylib 0x021fbcaf objc_terminate + 11
9   libdispatch.dylib   0x038a5052 _dispatch_client_callout + 33
10  libdispatch.dylib   0x0388cdb8 
_dispatch_barrier_sync_f_invoke + 79
11  libdispatch.dylib   0x0388c8ea dispatch_barrier_sync_f + 105
12  libdispatch.dylib   0x0388ce40 dispatch_barrier_sync + 54
13  com.apple.UIKit 0x00f1163d -[NSFileProviderExtension 
documentStorageURL] + 167
14  DocumentProviderFileProvider0x00130c25 -[FileProvider init] + 293 
(FileProvider.m:48)
15  libextension.dylib  0x04f9574f 
__105-[_NSExtensionContextVendor 
_beginRequestWithExtensionItems:listenerEndpoint:withContextUUID:completion:]_block_invoke
 + 875
16  libdispatch.dylib   0x03888a2a 
_dispatch_call_block_and_release + 15
17  libdispatch.dylib   0x038a503f _dispatch_client_callout + 14
18  libdispatch.dylib   0x0388e764 
_dispatch_main_queue_callback_4CF + 470
19  com.apple.CoreFoundation0x02f2895e 
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 14
20  com.apple.CoreFoundation0x02ee7760 __CFRunLoopRun + 2256
21  com.apple.CoreFoundation0x02ee6bcb CFRunLoopRunSpecific + 443
22  com.apple.CoreFoundation0x02ee69fb CFRunLoopRunInMode + 123
23  com.apple.Foundation0x01e03d98 -[NSRunLoop(NSRunLoop) 
runMode:beforeDate:] + 309
24  com.apple.Foundation0x01ea367b -[NSRunLoop(NSRunLoop) run] 
+ 82
25  libxpc.dylib0x03b6490d _xpc_objc_main + 423
26  libxpc.dylib0x03b6755a xpc_main + 199
27  com.apple.Foundation0x01facd16 -[NSXPCListener resume] + 186
28  com.apple.pluginkit.framework   0x01d4fa62 -[PKService run] + 552
29  com.apple.pluginkit.framework   0x01d4f6d2 +[PKService main] + 66
30  com.apple.pluginkit.framework   0x01d4fab7 +[PKService 
_defaultRun:arguments:] + 33
31  libextension.dylib  0x04fa6b6a NSExtensionMain + 60
32  libdyld.dylib

Build of Maven module executed twice

[Clifford Sanders]

Hi,

Last night a build (#468) of one of our Maven projects was started by an 
user manually by clicking on 'Rebuild Last'.
The build was marked as FAILED although the build log says "Finished: 
UNSTABLE" (two tests failed).

While looking at the "Module Builds" view I saw that one of the modules was 
built twice #468 (green) and #469 (red).

I had a look at ${JENKINS_HOME}/jobs/myJob/builds/468/module_f/build.xml


  

  clifford

  


  

  myJob/module_f
  view/myView/job/myJob/module_f/
  460
  

  


Build #460 was started a week ago, succeeded and is marked to be kept 
forever.

These are the sorted timestamps of the files/directories in 
${JENKINS_HOME}/jobs/myJob/builds/468

...
19:44:47.551809648 +0200 module_s -> 
../../modules/module_a/builds/2015-05-05_18-08-56
19:45:32.997800146 +0200 module_t -> 
../../modules/module_t/builds/2015-05-05_18-08-56
19:46:37.867786723 +0200 timestamper
19:46:37.867786723 +0200 log
19:47:09.709780194 +0200 injectedEnvVars.txt
19:47:09.910780153 +0200 build.xml
19:47:09.915780152 +0200 module_f -> 
../../modules/module_f/builds/2015-05-05_19-46-40

The console output of 
http://jenkinshost/view/myView/job/myJob/module_f/469/console

Started by user Clifford
Finished: ABORTED
FATAL: cannot change build result while in COMPLETED
java.lang.IllegalStateException: cannot change build result while in 
COMPLETED
  at hudson.model.Run.setResult(Run.java:458)
  at hudson.model.Run.execute(Run.java:1759)
  at hudson.maven.MavenBuild.run(MavenBuild.java:269)
  at hudson.model.ResourceController.execute(ResourceController.java:89)
  at hudson.model.Executor.run(Executor.java:240)


In the job configuration "Enable triggering of downstream projects" and 
"Block downstream trigger when building" are enabled.

We use
- Jenkins 1.594
- Maven Project Plugin 2.8
- Rebuild Plugin 1.22 

Can someone explain to me has happened here?

Thanks

Clifford

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e075154c-9399-487b-a354-0c3009ea7fe1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[workflow-plugin] Dir step : funny way of removing your whole master .jenkins directory

[Baptiste Mathus]

Hi,

Recently, someone in our shop had his first tries with the workflow plugin.

Some context: he wanted as a first step to ensure a specific directory in
the workspace would be removed. Here's an excerpt (warning: don't run it,
read below):

node('rhel'){
dir('workingdirectory'){
File currentWorkingDirectory = new File('.')
currentWorkingDirectory.deleteDir()
}
...
}


The thing is: it seems like the standard steps will know about this (doing
a sh 'pwd' would indeed display the
/somepath/.jenkins/jobs/workspace.../therightws/workingdirectory).

BUT, using new File('.') will NOT put you inside that subdirectory of the
WS. Guess what, it will point to $HOME :-).

So the code above will just basically totally wipe out your Jenkins master
data... The good news is that we've now thoroughly tested our backup and
it's working perfectly :-).

So, I'm not sure there's something doable, but at least that would be
desirable because of that dangerosity.

WDYT?

At least, I hope this mail will warn people to have caution in that area.

Cheers

-- 
Baptiste

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7k9UjoKJ3%3D3LXA0F65HxyYNg05tNZeY6SYP85zLsev7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Display the result of an Execute Shell

[Peter Marcoen]

Thank you Daniel, this was exactly what I was looking for!


Op woensdag 6 mei 2015 09:22:41 UTC+2 schreef Daniel Beck:
>
> These plugins should allow you to search the build log for your tool 
> output, and use it to set the build description, or (in the case of Groovy 
> Postbuild) add a separate section to the main build page: 
>
> https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Plugin (System Groovy 
> build step) 
>
> On 06.05.2015, at 08:51, Peter Marcoen > 
> wrote: 
>
> > That is correct Richard, I could go to the console output and there, 
> along with a whole lot of other output, I would see my result. 
> > For me, as a semi-experienced Jenkins user, this is doable, but for my 
> colleagues who have never seen a console output in their life, this is 
> trickier. 
> > Not to mention all the other rubbish that is printed there. So I was 
> looking if there was some other way. 
> > 
> > Op woensdag 6 mei 2015 04:25:50 UTC+2 schreef Richard Bywater: 
> > I would presume that if you are executing a Java program that outputs a 
> string it should show on the Console for the particular build of the job? 
> > 
> > Richard. 
> > 
> > On Wed, 6 May 2015 at 03:41 Peter Marcoen  wrote: 
> > I have a Jenkins Parameterized job. 
> > This job does 2 things: 
> > • Compiles a java program to a jar 
> > • Runs this jar through "Execute Shell" with the given 
> parameters 
> > The output of this java program is a single string. 
> > What I would like to accomplish is that if a user runs this job, this 
> return string is displayed to him on screen. 
> > 
> > Are there any plugins or default options that can help me achieve this? 
> > 
> > Another option would be to pipe the output of this java program to an 
> email command and get the result to the user in this way but I would prefer 
> to just stay in the Jenkins environment. 
> > 
> > I hope I make myself clear. 
> > 
> > -- 
> > 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. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/0239169f-5ae6-48c1-b7b4-9f7a8f6cf007%40googlegroups.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 . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/9fc5e732-986a-46c9-99ad-96df769b8f09%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/12e2e413-8a0f-4f74-8a87-8327789fc54e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Display the result of an Execute Shell

[Daniel Beck]

These plugins should allow you to search the build log for your tool output, 
and use it to set the build description, or (in the case of Groovy Postbuild) 
add a separate section to the main build page:

https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Plugin (System Groovy build 
step)

On 06.05.2015, at 08:51, Peter Marcoen  wrote:

> That is correct Richard, I could go to the console output and there, along 
> with a whole lot of other output, I would see my result.
> For me, as a semi-experienced Jenkins user, this is doable, but for my 
> colleagues who have never seen a console output in their life, this is 
> trickier.
> Not to mention all the other rubbish that is printed there. So I was looking 
> if there was some other way.
> 
> Op woensdag 6 mei 2015 04:25:50 UTC+2 schreef Richard Bywater:
> I would presume that if you are executing a Java program that outputs a 
> string it should show on the Console for the particular build of the job?
> 
> Richard.
> 
> On Wed, 6 May 2015 at 03:41 Peter Marcoen  wrote:
> I have a Jenkins Parameterized job.
> This job does 2 things:
>   • Compiles a java program to a jar
>   • Runs this jar through "Execute Shell" with the given parameters
> The output of this java program is a single string.
> What I would like to accomplish is that if a user runs this job, this return 
> string is displayed to him on screen.
> 
> Are there any plugins or default options that can help me achieve this?
> 
> Another option would be to pipe the output of this java program to an email 
> command and get the result to the user in this way but I would prefer to just 
> stay in the Jenkins environment.
> 
> I hope I make myself clear.
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/0239169f-5ae6-48c1-b7b4-9f7a8f6cf007%40googlegroups.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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/9fc5e732-986a-46c9-99ad-96df769b8f09%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CE934A16-DE35-4551-B6DF-95E41F3851BF%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.