[JIRA] (JENKINS-39365) Can't restrict a pipeline job to agents to run on

2016-10-29 Thread el...@elnur.pro (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Elnur Abdurrakhimov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39365  
 
 
  Can't restrict a pipeline job to agents to run on   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Oct/30 1:46 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Elnur Abdurrakhimov  
 

  
 
 
 
 

 
 Pipeline jobs should not be aware of the environment they run on. Stuff like agent nodes should not be specified in Jenkinsfile or the like. Agent nodes restriction should be configurable on pipeline jobs via UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This mess

[JIRA] (JENKINS-31396) Access to submitter ID from return value of input step

2016-10-29 Thread jswa...@alohaoi.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jason Swager commented on  JENKINS-31396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access to submitter ID from return value of input step   
 

  
 
 
 
 

 
 Submitted https://github.com/jenkinsci/pipeline-input-step-plugin/pull/8 to address this, because I want the feature too. Just not sure what the process is of getting a code review performed and getting it merged.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread pt...@roshitech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasad Tadi closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 this is a configuration issue from my end.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39236  
 
 
   Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
Change By: 
 Prasad Tadi  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-39236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
 Yes, please. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-33874) Upgrade git-plugin to new parent POM

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-33874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade git-plugin to new parent POM   
 

  
 
 
 
 

 
 Code changed in jenkins User: Mark Waite Path: pom.xml src/main/java/hudson/plugins/git/BranchSpec.java src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/GitStatus.java src/main/java/hudson/plugins/git/browser/GitoriousWeb.java src/main/java/hudson/plugins/git/browser/RhodeCode.java src/main/java/hudson/plugins/git/browser/Stash.java src/main/java/hudson/plugins/git/util/BuildData.java src/test/java/hudson/plugins/git/AbstractGitProject.java src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/GitPublisherTest.java src/test/java/hudson/plugins/git/GitSCMTest.java src/test/java/hudson/plugins/git/RevisionParameterActionTest.java src/test/java/hudson/plugins/git/TestGitRepo.java src/test/java/hudson/plugins/git/browser/TFS2013GitRepositoryBrowserTest.java http://jenkins-ci.org/commit/git-plugin/7a7da1e174099cdc09973de64b5edde9e9ef5c99 Log: Merge branch 'JENKINS-33874' of git://github.com/andresrc/git-plugin into 2.5.0-beta2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread pt...@roshitech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasad Tadi commented on  JENKINS-39236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
 Agreed thanks. Do I need to close this issue?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please submit questions related to authentication failures, and other configuration failures to the jenkins users mailing list. There are many more people on the mailing list who can assist with configuration errors. The output shows that you can't read from the remote repository. That's not usually a plugin bug. It is much more often a configuration error which many more people can assist.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39236  
 
 
   Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread pt...@roshitech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasad Tadi assigned an issue to Mark Waite  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39236  
 
 
   Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
Change By: 
 Prasad Tadi  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread pt...@roshitech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasad Tadi reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I marked it as resolved pre maturely  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39236  
 
 
   Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
Change By: 
 Prasad Tadi  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread pt...@roshitech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasad Tadi commented on  JENKINS-39236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
 BTW.. I am not sure if this is related . sometimes the plugin to "GIT Polling log" gives error as follows  I have to force the "POLL SCM" and select "update" to fix this issue. Any idea how we can resolve this? == Poll SCM = You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. UPDATE Git Polling Log  Git Polling Log Started on Oct 29, 2016 1:59:35 PM Using strategy: Default [poll] Last Built Revision: Revision 601beb34d132cdf40ec14e7eafae8f40467573b8 (refs/remotes/origin/rel-5.5.0.0) > /usr/bin/git ls-remote -h git@thoroughbred:flt/root.git # timeout=10 FATAL: hudson.plugins.git.GitException: Command "/usr/bin/git ls-remote -h git@thoroughbred:flt/root.git" returned status code 128: stdout:  stderr: ssh_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. java.io.IOException: hudson.plugins.git.GitException: Command "/usr/bin/git ls-remote -h git@thoroughbred:flt/root.git" returned status code 128: stdout:  stderr: ssh_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.  at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:574) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:391) at hudson.scm.SCM.poll(SCM.java:408) at hudson.model.AbstractProject._poll(AbstractProject.java:1460) at hudson.model.AbstractProject.poll(AbstractProject.java:1363) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:528) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:574) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git ls-remote -h git@thoroughbred:flt/root.git" returned status code 128: stdout:  stderr: ssh_exchange_identification: read: Connection reset by peer fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1752) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1495) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1419) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1410) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2463) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:613) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:572) ... 12 more Done. Took 3 sec No changes  
 

  
 
 

[JIRA] (JENKINS-32354) Provide support of Coverity runs from Workflow plugin

2016-10-29 Thread sgard...@sonusnet.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Gardell commented on  JENKINS-32354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide support of Coverity runs from Workflow plugin   
 

  
 
 
 
 

 
 I think the most value would come from focusing on recovery of issues from the Coverity Connect database as the mechanics of getting code scanned and results uploaded to Coverity Connect are quite straight-forward.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials dropdowns empty when configuring external libraries at the global level   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/git/UserRemoteConfig.java src/main/java/jenkins/plugins/git/GitSCMSource.java http://jenkins-ci.org/commit/git-plugin/b52b095c8310c607d28120b3a20137eacc58a64c Log: JENKINS-38048 Permits credentialsId dropdowns to be used from a global configuration screen.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Credentials dropdowns empty when configuring external libraries at the global level   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: src/test/java/hudson/plugins/git/UserRemoteConfigTest.java http://jenkins-ci.org/commit/git-plugin/bf0465f7a8d3f1811c6b458fe1c8f868875b5a6f Log: JENKINS-38048 Proving fix in functional test.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36483) Unable to login with google-login plugin with 401 error

2016-10-29 Thread j...@jwal.me.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Ascroft-Leigh commented on  JENKINS-36483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to login with google-login plugin with 401 error   
 

  
 
 
 
 

 
 I think I fixed this by correcting the client secret. I was lazy before and copied it from an old Jenkins `config.xml` file. When I copied it from the Google API console (console.developers.google.com) it started to work. Oops  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread pt...@roshitech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasad Tadi resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Configuration Error by user  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39236  
 
 
   Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
Change By: 
 Prasad Tadi  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread pt...@roshitech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Prasad Tadi commented on  JENKINS-39236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
 I think it could be my configuration issue, My jobs are copied from a template and template was pointing to the wrong branch in the "Ref Specs". This could be the reason, why the hook was not firing. Once I cleared that Ref Specs, then the JOBs started working fine. As this was a Hidden Property, it took some time to debug this issue. I have made the changes and things seems to work.  We may close this defect now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-31155) Workflow shared library improvements

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-31155  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Workflow shared library improvements   
 

  
 
 
 
 

 
 Code changed in jenkins User: Mark Waite Path: pom.xml src/main/java/hudson/plugins/git/UserRemoteConfig.java src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java src/test/java/jenkins/plugins/git/GitSampleRepoRule.java http://jenkins-ci.org/commit/git-plugin/0c6d93913a70007c8061a5a37438549d72bede9f Log: Merge pull request #433 from jglick/retrieve-revision-JENKINS-31155 JENKINS-31155 Ability to retrieve a single revision Compare: https://github.com/jenkinsci/git-plugin/compare/2025127d7e82...0c6d93913a70  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-31155) Workflow shared library improvements

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-31155  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Workflow shared library improvements   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java src/test/java/jenkins/plugins/git/GitSampleRepoRule.java http://jenkins-ci.org/commit/git-plugin/2b201d825c101b7ff6be71dad11d2d7d59ce1f81 Log: JENKINS-31155 Implement new retrieve(String, TaskListener) overload.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-39236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
 I can't duplicate the problem you're describing. You'll need to provide detailed, step by step instructions to show the problem. You may consider starting with a Jenkins docker instance (like my lts-with-plugins) so that you can then share your duplication steps with others.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39236) Doesn't fire all jobs for a branch, when a git commitNotify hook is called

2016-10-29 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39236  
 
 
   Doesn't fire all jobs for a branch, when a git commitNotify hook is called   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39334) Unable to run script.sh using "Execute shell script on remote host using ssh"

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39334  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to run script.sh using "Execute shell script on remote host using ssh"   
 

  
 
 
 
 

 
 You still do not provide the requested info. The build log is definitely not synced with the "xe" flag, because there is no execution trace of setup.sh. And no script as well  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38022) Create a verbose logging option for Nuget trigger

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Create a verbose logging option for Nuget trigger   
 

  
 
 
 
 

 
 Code changed in jenkins User: Arnaud Path: src/main/java/org/jenkinsci/plugins/nuget/triggers/logs/TriggerLog.java http://jenkins-ci.org/commit/nuget-plugin/60d20a23a2562406cedd07a1e764f341a483f839 Log: [FIXED JENKINS-38022] corrected a serialization issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39246) Windows Node reconnects endlessly after 2.27 update

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39246  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows Node reconnects endlessly after 2.27 update   
 

  
 
 
 
 

 
 Closing as a duplicate of JENKINS-39232  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39246) Windows Node reconnects endlessly after 2.27 update

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39246  
 
 
  Windows Node reconnects endlessly after 2.27 update   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39252) AWS linux master - windows 2012R2 slaves won't start via JNLP

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing as a duplicate of JENKINS-39232. The fix should arrive in 2.28  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39252  
 
 
  AWS linux master - windows 2012R2 slaves won't start via JNLP   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 The fix has been merged towards 2.28 In this fix you may have to set the jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification System Property to true in order to make the instance working (depend). Currently the fix with non-aggressive behavior is under consideration.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39364) Optimize encoding handling in hudson.XmlFile implementation

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39364  
 
 
  Optimize encoding handling in hudson.XmlFile implementation   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/29 11:31 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 It's a follow-up to the comment from James Nord in https://github.com/jenkinsci/jenkins/pull/2518#r76130001  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
   

[JIRA] (JENKINS-39363) [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39363  
 
 
  [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39363) [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-39363  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues   
 

  
 
 
 
 

 
 Merged towards jenkins-2.28  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39363) [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39363  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/XmlFile.java http://jenkins-ci.org/commit/jenkins/fe2b697e145a5d1c2b5cc60fc5f63b18b0aa79f2 Log: [JENKINS-39363,CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues. (#2518) [JENKINS-39363,CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39363) [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues

2016-10-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39363  
 
 
  [CID-1205051] - Prevent resource leak in hudson.XmlFile#readRaw() in the case of encoding issues   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/29 11:27 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 https://scan5.coverity.com/reports.htm#v36021/p10292/fileInstanceId=97573808&defectInstanceId=28155757&mergedDefectId=992726 Follow-up issue for https://github.com/jenkinsci/jenkins/pull/2518  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave

2016-10-29 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-39232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/slaves/DelegatingComputerLauncher.java core/src/main/java/jenkins/slaves/DefaultJnlpSlaveReceiver.java http://jenkins-ci.org/commit/jenkins/1d16ce024c9049c1f05b45b48d5f8438e9303f4e Log: JENKINS-39232 Walk the DelegatingComputerLauncher instances when checking if JNLPComputerLauncher (#2602) 
 
JENKINS-39232 Walk the DelegatingComputerLauncher instances when checking if JNLPComputerLauncher 
 
 
JENKINS-39232 Add a system property to enable legacy plugins to continue to work until they get fixed 
 
 
JENKINS-39232 Be more forgiving of plugins 
 
 
JENKINS-39232 Yet more forgiveness of plugins but define the forward contract 
 
 
JENKINS-39232 Provide diagnostics when this issue is encountered 
 
 
Since the failure of strict verification is an issue, we should log it as a warning always 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 

[JIRA] (JENKINS-10359) Show a summary status on the build view

2016-10-29 Thread lorenz.ste...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lorenz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Already done.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-10359  
 
 
  Show a summary status on the build view   
 

  
 
 
 
 

 
Change By: 
 Stefan Lorenz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-11292) parsing error..when trying to generate selenium report.htmls are being copied

2016-10-29 Thread lorenz.ste...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lorenz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 User template misconfiguration.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-11292  
 
 
  parsing error..when trying to generate selenium report.htmls are being copied   
 

  
 
 
 
 

 
Change By: 
 Stefan Lorenz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-12345) Publishing Selenium report blocks concurrent builds

2016-10-29 Thread lorenz.ste...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lorenz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-12345  
 
 
  Publishing Selenium report blocks concurrent builds   
 

  
 
 
 
 

 
Change By: 
 Stefan Lorenz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-18529) Feedback icons broken in Google Chrome

2016-10-29 Thread lorenz.ste...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lorenz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Won't fix.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-18529  
 
 
  Feedback icons broken in Google Chrome   
 

  
 
 
 
 

 
Change By: 
 Stefan Lorenz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39049) Getting java.io.IOException: org.xml.sax.SAXParseException

2016-10-29 Thread lorenz.ste...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lorenz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 User template misconfiguration.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39049  
 
 
  Getting java.io.IOException: org.xml.sax.SAXParseException
 

  
 
 
 
 

 
Change By: 
 Stefan Lorenz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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