Re: Pipeline with tests and deployment

[Bert]

Unconditionally gathering the JUnit results was actually simple: just add a 
post block each test stage, see the Jenkinsfile here 
.

The input is a little harder. I know how to do it through a script, but I'd 
like to stay in the declarative model. See my follow on question here 

.

Regards,
Bert

On Wednesday, March 1, 2017 at 10:34:44 AM UTC+1, Bert wrote:
>
> Thanks!
> The input I figured out. Gathering the JUnit results (unconditionally) 
> before asking for user input is where I'm stuck at.
>
> Regards,
> Bert
>
> On Wednesday, March 1, 2017 at 10:20:44 AM UTC+1, Baptiste Mathus wrote:
>>
>> For user input, you should be able to use the "input" step.
>>
>> For real world public usage of Declarative, there's mainly one I've heard 
>> of (Declarative reached 1.0 less than one month ago), I've seen a tweet for 
>> a mozilla project but can't find it again.
>>
>> 2017-03-01 8:08 GMT+01:00 Bert :
>>
>>> Hello everyone,
>>>
>>> We recently switched to the declarative pipeline approach. The current 
>>> pipeline 
>>>  is 
>>> very simple:
>>>
>>>1. Build
>>>2. Setup test server
>>>3. Run integration tests
>>>4. Post: Gather test results
>>>
>>> No I would like to add a user input to decide whether to take it to the 
>>> next stage: deploy it to acceptance test. The user providing that input 
>>> should be able to check the test results of that job, so the junit step 
>>> needs to move out of the post block, but it needs to remain 
>>> unconditional/always.
>>>
>>> How do I do that?
>>> Related: are you aware of serious public deployment pipelines (using the 
>>> declarative syntax) with multiple deployment stages and user inputs?
>>>
>>> Thanks in advance,
>>> Bert
>>>
>>> -- 
>>> 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/cd0d4cd6-df50-4e41-a0ce-8ab41786d53c%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/e3e3facf-31af-4206-9b5c-7ad226378e9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

User input in declarative pipeline

[Bert]

Hello everyone,

One of the CloudBees support articles 

 
describes how to do a user input in a pipeline script, as alternative for 
the promoted builds plug-in. I'm trying to do that, but then with a 
declarative pipeline definition.

I know that's possible through a script block inside the pipeline 
definition, but I'd like to prevent that and stay in the declarative model.

Is that possible?

Thanks in advance,
Bert

-- 
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/c000c6af-7c68-4133-9e43-82dd6254cbfa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Why merge requests auto accepted?

[Alan Cheng]

Hello all,

I have a job configured to be triggered after a git repo merge request is 
accepted (manually), using gitlab webhooks.
But I found when user open a merge request, the job will be triggered and 
the merge request is accepted automatically.

Here is a screenshot of my job trigger configuration. Any pointer as to why 
merge requests are accepted (after build succeeded)?
Jenkins is at version 2.35, if it matters.





Let me know if more information is needed. 



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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b5f915fe-143e-4b44-a237-7e79833b4b1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Purge xUnit/jUnit test results which are showing stale information

[Cody Konior]

I've noticed that after you build a job which produces xUnit/jUnit test 
results, the front matter of the job which shows failures tends to 
"remember" the first failure in a run. 

If you then re-ran the test and it generates another error message, that 
message will NOT show through that front failure section. It DOES get 
remembered further down if you click through to the very final test result 
screen.

I've also noticed something similar with this testing information - if you 
remove a build workspace, the xUnit/jUnit trend graph will fail. However if 
you replace one build number with another (in the filesystem, and reload), 
the count of passed/failed tests is still remembered from the original 
build.

Where is this information stored? I would like to know how to delete it. I 
haven't been able to find it on the filesystem.

-- 
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/f20819a4-926e-4bca-bf93-6d2dd5c7c457%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Option to disable/archive unused/unwanted jobs in multibranch pipeline views

[Stephen Connolly]

Once the backing branch has been deleted, you should be able to manually
delete ahead of the orphaned item strategy.

Events do not delete branches, only mark as orphaned. This is because of
how strategies that retain some branches need to see all orphaned ones to
tell which ones should be retained

On Wed 1 Mar 2017 at 23:06, Harsha Adiga  wrote:

> Hi,
>
> Is there a way to disable or move unwanted jobs from multibranch pipeline
> views. I am referring to those jobs whose corresponding branches have been
> deleted in Github. The current multibranch pipelines only seem to give
> option to either automatically delete such jobs or keep them forever. Is
> there a plan to provide more options to the user?
>
> Regards,
> Harsha
>
> --
> 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/f1090a5b-6362-4e85-a020-a9866059427c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx0P0w3fnt3wCS4B%3DLoP-LA8hsXJNepyO8LPVgWFUsuYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Option to disable/archive unused/unwanted jobs in multibranch pipeline views

[Harsha Adiga]

Hi,

Is there a way to disable or move unwanted jobs from multibranch pipeline 
views. I am referring to those jobs whose corresponding branches have been 
deleted in Github. The current multibranch pipelines only seem to give 
option to either automatically delete such jobs or keep them forever. Is 
there a plan to provide more options to the user?

Regards,
Harsha

-- 
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/f1090a5b-6362-4e85-a020-a9866059427c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there any way for a jenkins project to use the Gitlab plugin but only be built periodically and not when a change is pushed?

[Oded Badt]

Actually I tried with it both checked and unchecked and played arouns with
it back and forth and no matter what I do it still it rebuilds with every
push to the repository

On Wed, Mar 1, 2017 at 6:45 PM, suresh kumar  wrote:

> I think you have checked Poll SCM option in Build Triggers section.
> Uncheck Poll SCM and Check the checkbox Build periodically.
>
> [image:
> http://lh3.ggpht.com/-_t31sX5XYBU/VQXVt6PucQI/Bt0/gjCgub_9nH0/jenkins009_thumb%25255B1%25255D.png?imgmax=800]
>
> -Suresh
>
> On Wednesday, March 1, 2017 at 8:09:42 PM UTC+5:30, Oded Badt wrote:
>>
>> Note that:
>>
>> "Build when a change is pushed to GitLab. GitLab CI Service URL:"
>>
>> is UNCHECKED,
>> yet Jenkins keeps building the project every time I push a change to it
>> even though my intention is for it to be built periodically (with the code
>> snapshot of that moment) due to build side effects I prefer to avoid on
>> every push to my repo
>>
> --
> 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/zwbqxC196dM/unsubscribe.
> To unsubscribe from this group and all its topics, 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/02243e9c-7f5e-457f-8ae0-f92bdbdc0107%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/CAHQ5-_TE0dP_jn-oKLje7791444K0O3Hz2kf6jbRVUP5Z8qS-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recommending for cleaning up old builds when multibranch pipeline is in use?

[Baptiste Mathus]

http://javadoc.jenkins.io/hudson/tasks/LogRotator.html#LogRotator(java.lang.String,
java.lang.String, java.lang.String, java.lang.String) could be helpful.



2017-03-01 20:30 GMT+01:00 Mark Stosberg :

> Thanks for reply, and for providing both the Pipeline syntax formats. This
> is the first time I noticed that there are two distinct Pipeline syntaxes.
>
> I'm trying out the Scripted Pipeline syntax now.
>
> I tried to find documentation on the difference between 'numToKeepStr' and
> 'artifactNumToKeepStr' but couldn't. I set them both the same number in
> hopes that will have the desired effect of saving a particular number of
> builds.
>
>   Mark
>
> On Wednesday, March 1, 2017 at 4:08:53 AM UTC-5, Baptiste Mathus wrote:
>>
>> I don't think there's something per branch, but you probably want to
>> either search JIRA and/or file a new feature request about it.
>>
>> You shouldn't need a special plugin, this is a standard feature. Here's
>> the way to do it with Declarative Pipeline:
>>
>> pipeline {
>> options {
>> buildDiscarder(logRotator(numToKeepStr: '20'))
>> }
>> ...
>> }
>>
>> Or with scripted Pipeline: https://github.com/j
>> enkinsci/jenkins/blob/master/Jenkinsfile#L17-L19
>>
>> HTH
>>
>> 2017-02-28 20:24 GMT+01:00 Mark Stosberg :
>>
>>> For cleaning up old builds, the "Discard Old Builds" plugin is
>>> recommended:
>>>
>>> https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin
>>>
>>> However, the instructions for reference a "post build" step which
>>> doesn't exist in the Configure interface for Multibranch Pipeline projects.
>>>
>>> What's the recommended way to clean-up builds from multi-branch pipeline
>>> projects? Ideally I'd like different pruning policies for different
>>> branches.
>>>
>>> Thanks,
>>>
>>>  Mark
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%
>>> 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/ec6ee4ea-0deb-45f4-ba64-b5ad4f33ff8a%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/CANWgJS75FWLkkbet2FvMKuQkUpdPat%2BbkP19RjXVPvyYim815g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recommending for cleaning up old builds when multibranch pipeline is in use?

[Mark Stosberg]

Thanks for reply, and for providing both the Pipeline syntax formats. This 
is the first time I noticed that there are two distinct Pipeline syntaxes.

I'm trying out the Scripted Pipeline syntax now.  

I tried to find documentation on the difference between 'numToKeepStr' and 
'artifactNumToKeepStr' but couldn't. I set them both the same number in 
hopes that will have the desired effect of saving a particular number of 
builds. 

  Mark

On Wednesday, March 1, 2017 at 4:08:53 AM UTC-5, Baptiste Mathus wrote:
>
> I don't think there's something per branch, but you probably want to 
> either search JIRA and/or file a new feature request about it.
>
> You shouldn't need a special plugin, this is a standard feature. Here's 
> the way to do it with Declarative Pipeline: 
>
> pipeline {
> options {
> buildDiscarder(logRotator(numToKeepStr: '20'))
> }
> ...
> }
>
> Or with scripted Pipeline: 
> https://github.com/jenkinsci/jenkins/blob/master/Jenkinsfile#L17-L19
>
> HTH
>
> 2017-02-28 20:24 GMT+01:00 Mark Stosberg  >:
>
>> For cleaning up old builds, the "Discard Old Builds" plugin is 
>> recommended:
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin
>>
>> However, the instructions for reference a "post build" step which doesn't 
>> exist in the Configure interface for Multibranch Pipeline projects. 
>>
>> What's the recommended way to clean-up builds from multi-branch pipeline 
>> projects? Ideally I'd like different pruning policies for different 
>> branches. 
>>
>> Thanks,
>>
>>  Mark
>>
>> -- 
>> 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/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%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/ec6ee4ea-0deb-45f4-ba64-b5ad4f33ff8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to access Jenkins server using Python Or JenkinsApi for Windows

[Indra Gunawan (ingunawa)]

HI Sujith,

Are you proficient in Python?  At the very least you know how to install python 
module the easy way using pip install right?

From:  on behalf of Sujith Cherukuri 

Reply-To: "jenkinsci-users@googlegroups.com" 
Date: Monday, February 27, 2017 at 9:38 PM
To: Jenkins Users 
Subject: Re: How to access Jenkins server using Python Or JenkinsApi for Windows

Hello Eric,

Thanks for your reply, could you please let me know, how to install Jenkinsapi 
for Windows. I am not able to find any documentation for that.

Thanks and Regards,
Sujith

On Monday, February 27, 2017 at 8:06:49 PM UTC+5:30, Eric Pyle wrote:
I use Jenkinsapi for both Linux and Windows with no problem. You just need to 
install Jenkinsapi module in the Python installation used by each build 
machine, e.g. by "pip install jenkinsapi". Then in a shell or batch script 
build step, you call a Python script and "import jenkinsapi" in the script.

Eric
On 2/27/2017 5:08 AM, Sujith Cherukuri wrote:
Hello,

My build server is based on Windows. I want to trigger a Build using pythons 
scripts. As of now from http://pythonhosted.org/jenkinsapi/, it seems that, api 
only for Linux System.

Thanks and Regards,
Sujith
--
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/8d4a4967-b410-4c2f-bda9-f4f97a775e1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Eric Pyle

Siemens PLM Software

Lebanon, NH

+1 603-277-3060 (T)

+1 603-359-8670 (M)

...@siemens.com 

http://www.siemens.com/plm 

--
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/316fd8b4-d8ac-4152-8524-fc6a7b5e8c73%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/CBAB4170-2CBE-4C35-8D1F-220FF451BAD9%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub Org/Repo/Branch job cannot poll multiple repos? Missing PollSCM at Org / cannot edit PollSCM at branch

[Justin Vallon]

Stephen,

This link
https://github.com/jenkinsci/workflow-scm-step-plugin/blob/master/README.md#polling
shows how the workflow-scm-step-plugin is supposed to interact with the
"Poll SCM Plugin".  It appears the GitHub Org/branch builder is performing
some of the functionality of the PollSCM Plugin, but not capturing (or
responding to) all the activity on all the repos that the job actually
performed.

It appears that what is missing is:

a) Being able to specify settings for BuildTrigger / Poll SCM in the Org
job, or

b) Having the GitHub Org/branch be sensitive to the actual repo/branch that
was used in prior builds when routing a commit hook event to appropriate
rebuild jobs or

c) Being able to enable "PollSCM" in the branch job (not ideal, since those
jobs are created dynamically)

What is the forum to report this?  Specifically: github-org-folder makes a
branch job that does not work as expected with workflow-scm-step-plugin
(when checkout poll:true); poll-scm-plugin cannot be enabled

-Justin

On Tue, Feb 28, 2017 at 6:10 PM, Justin Vallon 
wrote:

> I'm talking about PollSCM that enables incoming commit-hooks to trigger
> the launching of jobs, not "poll scm every 5 minutes".
>
> If the Jenkinsfile does an explicit checkout, can't the job record the
> dependent URLs, and rescan those?  I am not asking for a general
> configuration solution at the job level, but if, like a
> Pipeline+Jenkinsfile job, the script does checkout additional URLs, then
> let that job be dependent on those checkouts.
>
> My sample would be:
>
> libA {
>   checkout self
>   build
> }
>
> appB {
>   checkout self
>   checkout libA on master branch
> }
>
> Pull requests on libA would build the new libA.  Merge to master would
> trigger appB to rebuild since it (previously) pulled from libA/master.
>
> The problem with triggering downstream builds is that libA might be used
> in appB, appC, libD, appE.  The dependency of appB on libA is present in
> appB;  inverting that dependency by moving it to libA creates a maintenance
> problem.
>
> MultiSCM rebuilding (appB) works with Pipeline + Jenkinsfile.  Commit in
> appB (branch or master) or libA (master) triggers rebuild of appB.
>
>
> On Tue, Feb 28, 2017 at 4:07 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> Multibranch is designed to remove the need for individual jobs to poll.
>>
>> When a scan is performed, we get - in one set of requests - all the head
>> revisions and then trigger builds for all branches with changes. This
>> reduces the impact of many jobs polling. Additionally events are
>> consolidated on a single path meaning that jobs get triggered without
>> needing a scan at all and with only verification of the event details.
>>
>> The down-side (currently) is that we do not have a good solution for
>> where you want to check out multiple sources. This in part reflects some of
>> the difficulties involved. For one, there is the question of how to align
>> branches:
>>
>> * do you always check out the "master" branch of the second repository?
>>
>> * do you always check out the same named branch?
>>
>> * do you check out the same named branch and fall back to the master
>> branch if there is no matching one?
>>
>> * what about more complex flows like with git flow?
>>
>> * it is highly unlikely that PRs against different repos will get the
>> same number, how do you determine the branch to use for PRs
>>
>> And that is just the start of the problem.
>>
>> Right now my recommendation is to use a Jenkinsfile in the second repo
>> that just triggers the build in the first repo. That way the commit against
>> the second repo will trigger a build of your main job that checks out the
>> primary and secondary repos.
>>
>> On Tue 28 Feb 2017 at 16:45,  wrote:
>>
>>> I am able to create a Pipeline job, and have the job do a git clone of
>>> two repos.  When there are commits in either repo, the job is triggered.
>>>
>>> However, I cannot get this to work with GitHub Org Folder / Repo /
>>> Branch.  The job is only triggered when the repo/branch is modified,
>>> despite it checking out other repos.
>>>
>>> I also noticed that in the GitHub Org job, there is no "PollSCM" in the
>>> top-level GitHub Org job.  However, in the repo/branch job, there is a
>>> "PollSCM", but the configuration of the job is read-only.  In order for the
>>> Pipeline build to work with multiple repos, then "PollSCM" option must be
>>> enabled.
>>>
>>> I would like to be able to do this:
>>>
>>> https://github.com/user/mylib - builds a library
>>> https;//github.com/user/myapp - builds an app
>>>
>>> myapp/Jenkinsfile:
>>>   dir("mylib") { git "https://github.com/user/mylib; }
>>>   dir("myapp") { git "https://github.com/user/myapp; }
>>>   sh 'do-build'
>>>
>>> Then, have the myapp job get triggered when there is a commit in either
>>> mylib or myapp.
>>>
>>> I have tried with a fresh download of Jenkins and up-to-date plugins.
>>> 

Re: Jenkins:error in archive the artifacts:**/*.war’ doesn’t match anything: ‘**’ exists but not ‘**/*.war’

[suresh kumar]

Hi Pranitha,
Is your build generates war?
Are you expecting artifacts from your build process and the above fileset 
didn't returned any files means build process is not generating any 
artifacts.
Cross check with your configuration and the type of build targets you are 
calling.

And also just providing an error message and seeking help is not the good 
way to seek help from the forum. 
Provide as much as possible information so people can understand where and 
what reason causing problem or failure and then accordingly you can get 
guidance.

-Suresh

On Wednesday, March 1, 2017 at 4:51:04 PM UTC+5:30, Pranitha jupalli wrote:
>
> Hi users..
> i have got the above error while building and my job was failed.
> pls help me 
>
> thanks 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/30dd1014-5f0a-414e-a42e-03b930382ffa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there any way for a jenkins project to use the Gitlab plugin but only be built periodically and not when a change is pushed?

[suresh kumar]

I think you have checked Poll SCM option in Build Triggers section. Uncheck 
Poll SCM and Check the checkbox Build periodically.

[image: 
http://lh3.ggpht.com/-_t31sX5XYBU/VQXVt6PucQI/Bt0/gjCgub_9nH0/jenkins009_thumb%25255B1%25255D.png?imgmax=800]

-Suresh

On Wednesday, March 1, 2017 at 8:09:42 PM UTC+5:30, Oded Badt wrote:
>
> Note that:
>
> "Build when a change is pushed to GitLab. GitLab CI Service URL:"
>
> is UNCHECKED,
> yet Jenkins keeps building the project every time I push a change to it 
> even though my intention is for it to be built periodically (with the code 
> snapshot of that moment) due to build side effects I prefer to avoid on 
> every push to my repo
>

-- 
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/02243e9c-7f5e-457f-8ae0-f92bdbdc0107%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows Slave / LinuxMaster hang

[jerome]

I wonder if this is related:

   1. https://issues.jenkins-ci.org/browse/JENKINS-28759
   2. https://issues.jenkins-ci.org/browse/JENKINS-33164

So I'm not the only one who have issue with the bat command hanging it 
seem. Wonder if it will ever get fixed?

-- 
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/712fbb9c-992a-4a2d-a0a9-aa3a7a6d2c32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is there any way for a jenkins project to use the Gitlab plugin but only be built periodically and not when a change is pushed?

[Oded Badt]

Note that:

"Build when a change is pushed to GitLab. GitLab CI Service URL:"

is UNCHECKED,
yet Jenkins keeps building the project every time I push a change to it 
even though my intention is for it to be built periodically (with the code 
snapshot of that moment) due to build side effects I prefer to avoid on 
every push to my repo

-- 
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/4c7e7c35-a7f2-472b-8254-0432e7043b88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins:error in archive the artifacts:**/*.war’ doesn’t match anything: ‘**’ exists but not ‘**/*.war’

[Daniel Beck]

> On 01.03.2017, at 12:21, Pranitha jupalli  wrote:
> 
> i have got the above error while building and my job was failed.

There are no war files in the directory you try to archive.

-- 
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/F19FC53F-4113-4A0B-B0B9-C068B4399B5D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Jenkins World 2017 Sponser Link is Insecure

[Krunal Patel]

Visiting https://www.cloudbees.com/jenkinsworld/home
and then clicking on "Become a Sponsor" gives "Your connection is not 
private".  Can the Webmaster look into this?

-- 
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/33dd0b4e-5eca-4e80-8369-1e2a8ca24f54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins:error in archive the artifacts:**/*.war’ doesn’t match anything: ‘**’ exists but not ‘**/*.war’

[Pranitha jupalli]

Hi users..
i have got the above error while building and my job was failed.
pls help me 

thanks 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/a721adf5-0df0-41d3-91cb-e800ee9b9fe5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline with tests and deployment

[Bert]

The Tweet you referred to is this one 
. The Jenkinsfile 
is here on GitHub 

.
Thanks for mentioning it.

Regards,
Bert


On Wednesday, March 1, 2017 at 10:20:44 AM UTC+1, Baptiste Mathus wrote:
>
> For user input, you should be able to use the "input" step.
>
> For real world public usage of Declarative, there's mainly one I've heard 
> of (Declarative reached 1.0 less than one month ago), I've seen a tweet for 
> a mozilla project but can't find it again.
>
> 2017-03-01 8:08 GMT+01:00 Bert :
>
>> Hello everyone,
>>
>> We recently switched to the declarative pipeline approach. The current 
>> pipeline  
>> is very simple:
>>
>>1. Build
>>2. Setup test server
>>3. Run integration tests
>>4. Post: Gather test results
>>
>> No I would like to add a user input to decide whether to take it to the 
>> next stage: deploy it to acceptance test. The user providing that input 
>> should be able to check the test results of that job, so the junit step 
>> needs to move out of the post block, but it needs to remain 
>> unconditional/always.
>>
>> How do I do that?
>> Related: are you aware of serious public deployment pipelines (using the 
>> declarative syntax) with multiple deployment stages and user inputs?
>>
>> Thanks in advance,
>> Bert
>>
>> -- 
>> 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/cd0d4cd6-df50-4e41-a0ce-8ab41786d53c%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/4554dfd6-90cc-4131-95a4-1252b5bf61a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline with tests and deployment

[Bert]

Thanks!
The input I figured out. Gathering the JUnit results (unconditionally) 
before asking for user input is where I'm stuck at.

Regards,
Bert

On Wednesday, March 1, 2017 at 10:20:44 AM UTC+1, Baptiste Mathus wrote:
>
> For user input, you should be able to use the "input" step.
>
> For real world public usage of Declarative, there's mainly one I've heard 
> of (Declarative reached 1.0 less than one month ago), I've seen a tweet for 
> a mozilla project but can't find it again.
>
> 2017-03-01 8:08 GMT+01:00 Bert :
>
>> Hello everyone,
>>
>> We recently switched to the declarative pipeline approach. The current 
>> pipeline  
>> is very simple:
>>
>>1. Build
>>2. Setup test server
>>3. Run integration tests
>>4. Post: Gather test results
>>
>> No I would like to add a user input to decide whether to take it to the 
>> next stage: deploy it to acceptance test. The user providing that input 
>> should be able to check the test results of that job, so the junit step 
>> needs to move out of the post block, but it needs to remain 
>> unconditional/always.
>>
>> How do I do that?
>> Related: are you aware of serious public deployment pipelines (using the 
>> declarative syntax) with multiple deployment stages and user inputs?
>>
>> Thanks in advance,
>> Bert
>>
>> -- 
>> 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/cd0d4cd6-df50-4e41-a0ce-8ab41786d53c%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/a43d33d5-bfe9-4028-bd9f-a54a3da61b3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline with tests and deployment

[Baptiste Mathus]

For user input, you should be able to use the "input" step.

For real world public usage of Declarative, there's mainly one I've heard
of (Declarative reached 1.0 less than one month ago), I've seen a tweet for
a mozilla project but can't find it again.

2017-03-01 8:08 GMT+01:00 Bert :

> Hello everyone,
>
> We recently switched to the declarative pipeline approach. The current
> pipeline 
> is very simple:
>
>1. Build
>2. Setup test server
>3. Run integration tests
>4. Post: Gather test results
>
> No I would like to add a user input to decide whether to take it to the
> next stage: deploy it to acceptance test. The user providing that input
> should be able to check the test results of that job, so the junit step
> needs to move out of the post block, but it needs to remain
> unconditional/always.
>
> How do I do that?
> Related: are you aware of serious public deployment pipelines (using the
> declarative syntax) with multiple deployment stages and user inputs?
>
> Thanks in advance,
> Bert
>
> --
> 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/ms
> gid/jenkinsci-users/cd0d4cd6-df50-4e41-a0ce-8ab41786d53c%
> 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/CANWgJS5zG7ND%2BR_TLDPn%3DwqxxUu%3D%3DG3oLFXpmFsC%2BcMKJ4am9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Recommending for cleaning up old builds when multibranch pipeline is in use?

[Baptiste Mathus]

I don't think there's something per branch, but you probably want to either
search JIRA and/or file a new feature request about it.

You shouldn't need a special plugin, this is a standard feature. Here's the
way to do it with Declarative Pipeline:

pipeline {
options {
buildDiscarder(logRotator(numToKeepStr: '20'))
}
...
}

Or with scripted Pipeline:
https://github.com/jenkinsci/jenkins/blob/master/Jenkinsfile#L17-L19

HTH

2017-02-28 20:24 GMT+01:00 Mark Stosberg :

> For cleaning up old builds, the "Discard Old Builds" plugin is recommended:
>
> https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin
>
> However, the instructions for reference a "post build" step which doesn't
> exist in the Configure interface for Multibranch Pipeline projects.
>
> What's the recommended way to clean-up builds from multi-branch pipeline
> projects? Ideally I'd like different pruning policies for different
> branches.
>
> Thanks,
>
>  Mark
>
> --
> 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/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%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/CANWgJS6mM4%2B_hVif-X5ED6WA8G7TdmLfpU4h3kH0ff77zQoFJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JNLP - Moving from random to fixed ports

[Baptiste Mathus]

Agent is connecting to master.

Yes, switching to fixed port is fine. Actually this should be the default,
probably will some day.

2017-02-28 9:19 GMT+01:00 Daniel Becroft :

> Hey guys,
> We are currently running multiple build nodes configured just with a
> Random TCP port for JNLP communication. Due to firewall rules now, we need
> to move to a fixed port.
>
> Is there anything special about moving from random to fixed? Do I need to
> stop all the nodes at the same time, change the port, and restart? Or can
> each node be bounced independently?
>
> Also, what direction are the connections made? Is it the Jenkins master
> creating the connection to the slave on the JNLP port, or vice versa? Or
> both?
>
> Cheers,
> Daniel B.
>
> --
> 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/CAJM0iSQkKw_uVeABzMyZyTB8uVGSo0oiXhZ45p4DO
> tMfR0O2Jw%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/CANWgJS5oh1Nz1yxnnkyOgCySVG5D%3Dd4Oe_sGimTdsO-_qY6XvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sending mail from pipeline not working

[Thorsten Meinl]

Afaik I have to configure the contents of "mail" myself. However, I just 
want the same mail sent by pipeline jobs as by freesytle jobs, i.e. 
depending on the job's status with different subjects, etc. I checked the 
mail server's log files and no sign of any mails sent from pipelines.
This whole pipeline stuff seems very buggy to me, not being able to send 
mails is just one of many issues...

On Wednesday, March 1, 2017 at 9:53:42 AM UTC+1, Baptiste Mathus wrote:
>
> Out of curiosity, why are you using the "step" step, instead of plain 
> "mail" or "email" one. I can confirm mail is working for us, and email too 
> for sure. So I would look into the server logs, maybe your email is getting 
> refused out for some reason due to the content or so.
>
> Did you try using the snippet generator to get the right syntax?
>
> 2017-02-27 12:48 GMT+01:00 Thorsten Meinl  >:
>
>>
>> Anything interesting in the build log? 
>>>
>>> Nope, only
>>
>> [Pipeline] stage[Pipeline] { (Send mail)[Pipeline] step[Pipeline] 
>> }[Pipeline] // stage
>>
>>  
>>
>> -- 
>> 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/ff777064-1eaf-43a6-9079-fdc67df074bf%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/190bf5c8-98b3-4461-b73b-0944e237df4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forcing Update Center to use a specific mirror? Or creating my own?

[Baptiste Mathus]

Hi,

Probably better to direct that kind of question either to the jenkins-infra
ML, or on the #jenkins-infra IRC channel.

Cheers!

2017-02-27 18:13 GMT+01:00 Jeff :

> Our Jenkins server is inside a secure environment with very limited
> external connectivity.  I was able to finally convince the powers that be
> to create an exception in our proxy to allow the Jenkins master to contact
> the update center URL.  However when I try to download, it redirects to a
> mirror which is not allowed.
>
> Can I somehow tell the update center to NOT use a mirror or use a specific
> mirror that I can whitelist so I don't have to allow all possible mirror
> URLs?
>
> Alternatively could I configure my own local mirror that I can use?
>
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAPJK9%3DLcu9ZsAnEQzy%3DsRRBx1e06QcSdn2BX%
> 2BYzz0KA9ApyS3w%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/CANWgJS4fP8v235Z9cbt-iGs0BgMccVKVTQnsPbHT0yxpZhdAWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sending mail from pipeline not working

[Baptiste Mathus]

Out of curiosity, why are you using the "step" step, instead of plain
"mail" or "email" one. I can confirm mail is working for us, and email too
for sure. So I would look into the server logs, maybe your email is getting
refused out for some reason due to the content or so.

Did you try using the snippet generator to get the right syntax?

2017-02-27 12:48 GMT+01:00 Thorsten Meinl :

>
> Anything interesting in the build log?
>>
>> Nope, only
>
> [Pipeline] stage[Pipeline] { (Send mail)[Pipeline] step[Pipeline] }[Pipeline] 
> // stage
>
>
>
> --
> 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/ff777064-1eaf-43a6-9079-fdc67df074bf%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/CANWgJS7R13uO%2BH%3DAT2bR3EmU4XiNxvgwmH4esLwOBasDODdYJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Picky success criteria in pipeline

[Baptiste Mathus]

FWIW, you should really consider moving to Pipeline if you want to use
something used by others where you have far bigger chance of feedback.
Build Flow is deprecated.

My 2 cents

2017-02-24 8:21 GMT+01:00 Tomasz Szandała :

> Greetings All,
> I am trying to go from build flow to Pipeline(and Jenkins2.x), but I have
> encountered an issue:
> I have complicated workflow, that should cause deploy. But deploy
> requirements are fluent. Let's say I have something like this:
>
> I need all green ones to be requirements, but yellow ones to be perfomed,
> but not mandatory success full in order to start blue one.
> I was thinking about: each job editting some kind of map ["jobA":
> "SUCCESS", "jobB": "FAILURE"] or in properties file. But how can I ensure
> concurrency?
>
> Kind regards,
> Tomasz
>
> P.S.
> Keep in mind that requirements can change, so try / catch are too static.
>
> --
> 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/5964a845-594e-4cd0-8b88-fac2980186e9%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/CANWgJS6hsjm2yyq9HO-VcT9LK8jN29VX8GNBQoGT8bzD5Z%2BTUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins workspace got deleted from Slave

[Baptiste Mathus]

Hi, you probably want to clarify what you mean, what you did, and what you
expect. Workspace should be considered transient, but I'm not sure what you
did.

2017-02-23 19:16 GMT+01:00 TN :

> Hi,
> I am new in Jenkins. Not sure how my workspace got deleted from Jenkins.
> Now it's looking for workspace in master. Jenkins can't build project
> anymore, it's failing. what should i do in this case?
>
> Thanks,
> TN
>
> --
> 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/19100471-1af1-4046-81b0-b2d83d9a61f3%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/CANWgJS6UK0z0H09OvfTNq9cbM8ypf5zUVjGBCN8a0%3DEkh5htOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.