[JIRA] (JENKINS-41476) Jenkinsfile fails with BOM

[e...@louvard.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Éric Louvard updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41476  
 
 
  Jenkinsfile fails with BOM   
 

  
 
 
 
 

 
Change By: 
 Éric Louvard  
 
 
Attachment: 
 Jenkinsfile  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41476) Jenkinsfile fails with BOM

[e...@louvard.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Éric Louvard commented on  JENKINS-41476  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile fails with BOM   
 

  
 
 
 
 

 
 I could reproduce this Issue with Jenkins 2.109 and the attached file Jenkinsfile  Regards.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49788) ConcurrentLinkedQueue is missing from whitelisted-classes.txt

[nightwalke...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Carl-Frederik Hallberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49788  
 
 
  ConcurrentLinkedQueue is missing from whitelisted-classes.txt   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-02-28 08:11  
 
 
Environment: 
 Jenkins v 2.109   java version "1.8.0_161"  Java(TM) SE Runtime Environment (build 1.8.0_161-b12)  Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)   
 
 
Labels: 
 JEP-200  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Carl-Frederik Hallberg  
 

  
 
 
 
 

 
 We make use of the ConcurrentLinkedQueue class, and which is not white-listed like other concurrent collections are. The unmarshalling and marshalling of the field fails with the following error: Feb 28, 2018 9:08:22 AM WARNING jenkins.security.ClassFilterImpl lambda$isBlacklisted$1 java.util.concurrent.ConcurrentLinkedQueue in JRE might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ java.lang.UnsupportedOperationException: Refusing to marshal java.util.concurrent.ConcurrentLinkedQueue for security reasons; see https://jenkins.io/redirect/class-filter/     at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543)     at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)     at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)     at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)     at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)     at hudson.util.RobustReflectionCo

[JIRA] (JENKINS-49770) publish-over-ssh not saving settings

[mail_user_tr...@mail.ru (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Al commented on  JENKINS-49770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: publish-over-ssh not saving settings   
 

  
 
 
 
 

 
 this broke all related jobs for me  was forced to downgrade to version 1.18.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49787) Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()   
 

  
 
 
 
 

 
 IIUC it is not and XML 1.1 regression. Even before that Jenkins used to override config.xml when resaving the object on its own. Jenkins does not store information about the original formatting in its data model and does not retain it when saving. So any JobDSL-generated config may have changed anyway. Using plain diffs for such purpose in Jib Config History is questionable. XMLDiff would be preferable though it requires more computations. One of the way to prevent the diff in this case would be to make Jenkins to deserialize object and save it instead of putting the original XML and then loading from it (code is here: https://github.com/jenkinsci/jenkins/blob/a79fdaa4b34b8f7fddb39bed3eabf4763940d11b/core/src/main/java/hudson/model/ItemGroupMixIn.java#L260-L309)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49195) If we run multiple BlazeMeter tests every BlazeMeter Report link point to the first test

[artem.fedo...@blazemeter.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov assigned an issue to Artem Fedorov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49195  
 
 
  If we run multiple BlazeMeter tests every BlazeMeter Report link point to the first test   
 

  
 
 
 
 

 
Change By: 
 Artem Fedorov  
 
 
Assignee: 
 Artem Fedorov  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37313) "Test BlazeMeter API Key" results in NullPointerException when using proxy

[artem.fedo...@blazemeter.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov assigned an issue to Artem Fedorov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37313  
 
 
  "Test BlazeMeter API Key" results in NullPointerException when using proxy   
 

  
 
 
 
 

 
Change By: 
 Artem Fedorov  
 
 
Assignee: 
 Artem Fedorov  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-33404) Blazemeter Plugins issue

[artem.fedo...@blazemeter.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov assigned an issue to Artem Fedorov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33404  
 
 
  Blazemeter Plugins issue   
 

  
 
 
 
 

 
Change By: 
 Artem Fedorov  
 
 
Assignee: 
 Artem Fedorov  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47531) git-lfs: allow specifying separate credentials

[meph...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 mephi42 commented on  JENKINS-47531  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-lfs: allow specifying separate credentials   
 

  
 
 
 
 

 
 Stephen Connolly, could you please take another look at the pull request? I have some time now to work on improving the pull request in case it's still required.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49525) Rare exception sync'ing global pipeline library with new project

[simon.wa...@bgcpartners.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Watts updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49525  
 
 
  Rare exception sync'ing global pipeline library with new project   
 

  
 
 
 
 

 
Change By: 
 Simon Watts  
 
 
Attachment: 
 JENKINS-49525-1.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49525) Rare exception sync'ing global pipeline library with new project

[simon.wa...@bgcpartners.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Watts commented on  JENKINS-49525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rare exception sync'ing global pipeline library with new project   
 

  
 
 
 
 

 
 Just encountered this behaviour in an established project from an overnight build – the console output is attached as JENKINS-49525-1.txt (with names redacted).  In this case there is evidence that 'ANOTHERPROJECT' was built successfully at around the same time and the 'PROJECT' which failed. These projects are using template workspaces defined in Perforce, and are not using light weight checkout.  Other projects where also built at around the same time (successfully or failing due to code errors).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/security/ClassFilterImpl.java http://jenkins-ci.org/commit/jenkins/376c6a0add41e0c2049b64edfdd464bb8717ed1b Log: JENKINS-49543 Old versions of Tomcat also failed to serialize classes from Jenkins modules.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/security/ClassFilterImpl.java http://jenkins-ci.org/commit/jenkins/262a7a1345e6847a7f075eba0bde3a3d31bda6fa Log: Merge pull request #3313 from jglick/Tomcat-redux-JENKINS-49543 JENKINS-49543 Old versions of Tomcat also failed to serialize classes from Jenkins modules Compare: https://github.com/jenkinsci/jenkins/compare/c33f14620425...262a7a1345e6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions   
 

  
 
 
 
 

 
 It has been merged towards 2.110.  Oliver Gondža We do not know how many users run on the old Tomcat versions. Since the fix is narrow-scoped, would it make sense to add it to 2.107.1-rc? Or should we add it to known issues in the upgrade guide and postpone it till .2?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49789) NPE when attempting to parse exception

[ch...@orr.me.uk (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Orr created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49789  
 
 
  NPE when attempting to parse exception   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Christopher Orr  
 
 
Components: 
 google-play-android-publisher-plugin  
 
 
Created: 
 2018-02-28 09:20  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Christopher Orr  
 

  
 
 
 
 

 
 From a comment on the wiki: https://wiki.jenkins.io/display/JENKINS/Google+Play+Android+Publisher+Plugin?focusedCommentId=138450677#comment-138450677 

 

ERROR: Build step failed with exception
java.lang.NullPointerException
at org.jenkinsci.plugins.googleplayandroidpublisher.Util.getPublisherErrorMessage(Util.java:97)
at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.publishApk(ApkPublisher.java:383)
at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:198)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
at hudson.model.Build$BuildExecution.post2(Build.java:186)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
at hudson.model.Run.execute(Run.java:1753)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:405)
Build step 'Upload Android APK to Google Play' marked build as failure 

  
 

  

[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-48050  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Replace Declarative Docker agent directive with new implementation   
 

  
 
 
 
 

 
 Code changed in jenkins User: Nicolas De Loof Path: pom.xml src/main/groovy/io/jenkins/docker/pipeline/DockerAgentScript.groovy src/main/java/io/jenkins/docker/pipeline/DockerAgent.java http://jenkins-ci.org/commit/docker-plugin/2e2c79fc3aba672e6a19d812d47ac55b2c7a418b Log: JENKINS-48050 declarative « container » agent Signed-off-by: Nicolas De Loof   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49381) Need to update github-api on github-plugin

[gentoo.inte...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kanstantsin Shautsou assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49381  
 
 
  Need to update github-api on github-plugin   
 

  
 
 
 
 

 
Change By: 
 Kanstantsin Shautsou  
 
 
Assignee: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49381) Need to update github-api on github-plugin

[gentoo.inte...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kanstantsin Shautsou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49381  
 
 
  Need to update github-api on github-plugin   
 

  
 
 
 
 

 
Change By: 
 Kanstantsin Shautsou  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49381) Need to update github-api on github-plugin

[gentoo.inte...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kanstantsin Shautsou commented on  JENKINS-49381  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need to update github-api on github-plugin   
 

  
 
 
 
 

 
 Github plugin is requiring minimal github-api plugin version. That mean that you can install any newer api-plugin version when issue is in api.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49727) Add optional parameter to specify the number of items the list will display

[klim...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas started work on  JENKINS-49727  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49790) Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.

[pathfinder2104.w...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ayushya Devmurari created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49790  
 
 
  Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-02-28 10:09  
 
 
Environment: 
 Windows 10, Jenkins 2.89.4.  
 
 
Labels: 
 pipeline  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ayushya Devmurari  
 

  
 
 
 
 

 
 I am facing issues while executing a batch file from Jenkins pipeline. I think this is a bug in jenkins because I have another job which runs without pipeline using jenkins.   Here is the detailed script and question on [SO|https://stackoverflow.com/questions/49025062/windows-start-command-not-working-from-jenkins-pipeline.] *Things I have tried* 
 
Failure: 
 I have tried executing it from a batch file too using the same configuration. That is also not working.   
 
Success: 
 
 
However if I run the batch file from command prompt from windows it self, it works fine. 
 
 
Further mo

[JIRA] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud

[eduard.we...@bosch-fs.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eduard Weiss commented on  JENKINS-47254  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for building tags for Bitbucket Server/Cloud   
 

  
 
 
 
 

 
 Hi, I implemented this feature for Bitbucket too. Here is the PR: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/113  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49648) plugin fails with new date/time shift option

[david.gumbr...@ge.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Gumbrell commented on  JENKINS-49648  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: plugin fails with new date/time shift option   
 

  
 
 
 
 

 
 It seems that a very specifically constructed "null" shift patterns will work to allow variables to be exported: 
 
- 0 days 0 hours 0 minutes    – works 
+ 0 days 0 hours 0 minutes  – doesn't work 
0 days 0 hours 0 minutes – doesn't work 
 – doesn't work 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-43654) adding a simple writeFile inside withMaven causes pipeline to hang

[nco...@fgtsa.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa commented on  JENKINS-43654  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: adding a simple writeFile inside withMaven causes pipeline to hang   
 

  
 
 
 
 

 
 Still an issue with Jenkins 2.108 and fully updated plugins as of today.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49788) ConcurrentLinkedQueue is missing from whitelisted-classes.txt

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49788  
 
 
  ConcurrentLinkedQueue is missing from whitelisted-classes.txt   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49790) Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49790  
 
 
  Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49788) ConcurrentLinkedQueue is missing from whitelisted-classes.txt

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-49788  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49788  
 
 
  ConcurrentLinkedQueue is missing from whitelisted-classes.txt   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49790) Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49790  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.   
 

  
 
 
 
 

 
 Which Pipeline plugin versions do you use?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49788) ConcurrentLinkedQueue is missing from whitelisted-classes.txt

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-49788  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-46498) Docker fingerprint not showing image usage in UI.

[nco...@fgtsa.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa commented on  JENKINS-46498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker fingerprint not showing image usage in UI.   
 

  
 
 
 
 

 
 Still an issue with Jenkins 2.108 and fully updated plugins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49788) ConcurrentLinkedQueue is missing from whitelisted-classes.txt

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49788  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ConcurrentLinkedQueue is missing from whitelisted-classes.txt   
 

  
 
 
 
 

 
 Code changed in jenkins User: Carl-Frederik Hallberg Path: core/src/main/resources/jenkins/security/whitelisted-classes.txt http://jenkins-ci.org/commit/jenkins/e5f61e29e260688d7d73339202c22ca199535018 Log: JENKINS-49788 Added ConcurrentLinkedQueue to whitelisted classes. (#3315)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49788) ConcurrentLinkedQueue is missing from whitelisted-classes.txt

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49788  
 
 
  ConcurrentLinkedQueue is missing from whitelisted-classes.txt   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 JEP-200  lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49790) Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.

[pathfinder2104.w...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ayushya Devmurari commented on  JENKINS-49790  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.   
 

  
 
 
 
 

 
 Oleg Nenashev "Pipeline: Multibranch with defaults" plugin version is 1.1.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49788) ConcurrentLinkedQueue is missing from whitelisted-classes.txt

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49788  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ConcurrentLinkedQueue is missing from whitelisted-classes.txt   
 

  
 
 
 
 

 
 Added lts-candidate so that we consider that for 2.107.x. FTR I do not see affected plugins in Jenkins org: https://github.com/search?p=1&q=org%3Ajenkinsci+ConcurrentLinkedQueue&type=Code . But it is still reasonable since other collections are whitelisted, and the issue may potentially impact other plugin not hosted in the Jenkins UC.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49790) Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49790  
 
 
  Jenkins - Pipeline doesn't allow to execute external batch files with "Start" command in it.   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 pipeline-multibranch-defaults-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49525) Rare exception sync'ing global pipeline library with new project

[pal...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-49525  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rare exception sync'ing global pipeline library with new project   
 

  
 
 
 
 

 
 Hi Simon, Please can you raise a support ticket (supp...@perforce.com) and verify the plugin version e.g. 1.8.6, feel free to CC me (pallen) Do you use Global Pipeline Libraries?    Jenkins>Manage Jenkins>Global Configuration>Global Pipeline Libraries I recently added a fix to reduce the chance of this bug, however I have the feeling it may occur in some circumstances.  My concern is around the Perforce client workspace used by Jenkins to sync the Library (pre-build) and what happens if another Job is syncing the same library at the same time.  Jenkins recently added lightweight checkout to Pipeline builds for fetching the Jenkinsfile, this would be perfect for Libraries, but I can't see a way to use it.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49775) envinject overrides some variables

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: envinject overrides some variables   
 

  
 
 
 
 

 
 Somebody needs to verify that, but probably it's not an EnvInject regression. Maybe the core it self consults with other vars when injecting environment  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49775) envinject overrides some variables

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49775  
 
 
  envinject overrides some variables   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-30632) Multijob running specific matrix configuration results in java.null.reference

[developm...@jordi.vilar.cat (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jordi Vilar commented on  JENKINS-30632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multijob running specific matrix configuration results in java.null.reference   
 

  
 
 
 
 

 
 Is there any progress on this issue? Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49791) Sometime I get Temporary failure in name resolution

[vickyrathore1...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikas Rathore created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49791  
 
 
  Sometime I get Temporary failure in name resolution   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 svn-release-mgr-plugin  
 
 
Created: 
 2018-02-28 11:18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vikas Rathore  
 

  
 
 
 
 

 
 Whenever I release the builds it sometimes gets failed and with changing anything if I try again a couple of time. it get resolved automatically. can one facing the same issue?   java.net.UnknownHostException: xyz: Temporary failure in name resolution at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323) at java.net.InetAddress.getAllByName0(InetAddress.java:1276) at java.net.InetAddress.getAllByName(InetAddress.java:1192) at java.net.InetAddress.getAllByName(InetAddress.java:1126) at java.net.InetAddress.getByName(InetAddress.java:1076) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createAddres(SVNSocketFactory.java:205) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:66) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:275) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:454) Caused: org.tmatesoft.svn.core.SVNException: svn: E175002: unknown host svn: E175002: OPTIONS request failed on '/svn/xbec/trunk/XBEC_Dev' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:112) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:96) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:803) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:391) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.perform

[JIRA] (JENKINS-47313) Call microsoft batch trigger "\Java\jre1.8.0_141\bin" was unexpected

[ttamal...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Estrada Matthieu edited a comment on  JENKINS-47313  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Call microsoft batch trigger "\Java\jre1.8.0_141\bin" was unexpected   
 

  
 
 
 
 

 
 [~oleg_nenashev] Yes I've solved this problem by using:{code: groovy java }bat '''call "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\VC\\Auxiliary\\Build\\vcvars64.bat"...'''{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47313) Call microsoft batch trigger "\Java\jre1.8.0_141\bin" was unexpected

[ttamal...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Estrada Matthieu commented on  JENKINS-47313  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Call microsoft batch trigger "\Java\jre1.8.0_141\bin" was unexpected   
 

  
 
 
 
 

 
 Oleg Nenashev Yes I've solved this problem by using: 

 

Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


bat '''
call "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\VC\\Auxiliary\\Build\\vcvars64.bat"
...
'''
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49791) Sometime I get Temporary failure in name resolution

[vickyrathore1...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikas Rathore updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49791  
 
 
  Sometime I get Temporary failure in name resolution   
 

  
 
 
 
 

 
Change By: 
 Vikas Rathore  
 
 
Component/s: 
 subversion-plugin  
 
 
Component/s: 
 svn-release-mgr-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49791) Sometime I get Temporary failure in name resolution

[vickyrathore1...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikas Rathore updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49791  
 
 
  Sometime I get Temporary failure in name resolution   
 

  
 
 
 
 

 
Change By: 
 Vikas Rathore  
 

  
 
 
 
 

 
 Whenever I release the builds it sometimes gets failed and  with  without  changing anything if I try again a couple of time. it get resolved automatically. can one facing the same issue? java.net.UnknownHostException: xyz: Temporary failure in name resolution at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323) at java.net.InetAddress.getAllByName0(InetAddress.java:1276) at java.net.InetAddress.getAllByName(InetAddress.java:1192) at java.net.InetAddress.getAllByName(InetAddress.java:1126) at java.net.InetAddress.getByName(InetAddress.java:1076) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createAddres(SVNSocketFactory.java:205) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:66) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:275) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:454)Caused: org.tmatesoft.svn.core.SVNException: svn: E175002: unknown hostsvn: E175002: OPTIONS request failed on '/svn/xbec/trunk/XBEC_Dev' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:112) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:96) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:803) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:391) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:862) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:698) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:195) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOpera

[JIRA] (JENKINS-49792) All branches being queried for each single build

[lpie...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Piedra-Márquez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49792  
 
 
  All branches being queried for each single build   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 bitbucket-branch-source-plugin  
 
 
Created: 
 2018-02-28 11:42  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Luis Piedra-Márquez  
 

  
 
 
 
 

 
 In order to retrieve revrision from a Head, a query for all existinng branches is done 

 

@Override
protected SCMRevision retrieve(SCMHead head, TaskListener listener) throws IOException, InterruptedException {
    final BitbucketApi bitbucket = buildBitbucketClient();
    Listextends BitbucketBranch> branches = bitbucket.getBranches();
 

 This is causing heavy delays when starting builds, specially in Mercurial where branches cannot be deleted, they are just closed. Branches in API v2 is a paginated response, and in our case it is also hitting Bitbucket API rate limit. With Bitbucket Cloud API v1 this was not a problem becasue closed branches where not included in the response for all branches.    
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud

[lpie...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Piedra-Márquez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47254  
 
 
  Support for building tags for Bitbucket Server/Cloud   
 

  
 
 
 
 

 
Change By: 
 Luis Piedra-Márquez  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49791) Sometime I get Temporary failure in name resolution

[vickyrathore1...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikas Rathore updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49791  
 
 
  Sometime I get Temporary failure in name resolution   
 

  
 
 
 
 

 
Change By: 
 Vikas Rathore  
 

  
 
 
 
 

 
 Whenever I release the builds it sometimes gets failed and without changing anything if I try again a couple of time. it  get  gets  resolved automatically.  can one  Is anyone  facing the same issue? java.net.UnknownHostException: xyz: Temporary failure in name resolutionat java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)at java.net.InetAddress.getAllByName0(InetAddress.java:1276)at java.net.InetAddress.getAllByName(InetAddress.java:1192)at java.net.InetAddress.getAllByName(InetAddress.java:1126)at java.net.InetAddress.getByName(InetAddress.java:1076)at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createAddres(SVNSocketFactory.java:205)at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:66)at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:275)at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:454)Caused: org.tmatesoft.svn.core.SVNException: svn: E175002: unknown hostsvn: E175002: OPTIONS request failed on '/svn/xbec/trunk/XBEC_Dev'at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:112)at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:96)at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:803)at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:391)at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379)at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:862)at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:698)at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118)at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049)at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189)at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119)at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:195)at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:46)at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160)at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)at

[JIRA] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud

[lpie...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Piedra-Márquez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47254  
 
 
  Support for building tags for Bitbucket Server/Cloud   
 

  
 
 
 
 

 
Change By: 
 Luis Piedra-Márquez  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49792) All branches being queried for each single build

[lpie...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Piedra-Márquez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49792  
 
 
  All branches being queried for each single build   
 

  
 
 
 
 

 
Change By: 
 Luis Piedra-Márquez  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49792) All branches being queried for each single build

[lpie...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Piedra-Márquez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49792  
 
 
  All branches being queried for each single build   
 

  
 
 
 
 

 
Change By: 
 Luis Piedra-Márquez  
 

  
 
 
 
 

 
 In order to retrieve revrision from a Head, a query for all existinng branches is done{code:java}@Overrideprotected SCMRevision retrieve(SCMHead head, TaskListener listener) throws IOException, InterruptedException {    final BitbucketApi bitbucket = buildBitbucketClient();    List branches = bitbucket.getBranches();{code} I think it is possible to obtain the revision from the API with a query for the specific Head  This is causing heavy delays when starting builds, specially in Mercurial where branches cannot be deleted, they are just closed. Branches in API v2 is a paginated response, and in our case it is also hitting Bitbucket API rate limit.With Bitbucket Cloud API v1 this was not a problem becasue closed branches where not included in the response for all branches.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   

[JIRA] (JENKINS-47313) Call microsoft batch trigger "\Java\jre1.8.0_141\bin" was unexpected

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Not a defect then. The installation path has changed from Enterprise to Professional die to the change of Visual Studio version. There is nothing we can do on the Jenkins project side  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47313  
 
 
  Call microsoft batch trigger "\Java\jre1.8.0_141\bin" was unexpected   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49791) Sometime I get Temporary failure in name resolution

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49791  
 
 
  Sometime I get Temporary failure in name resolution   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 _unsorted  
 
 
Component/s: 
 subversion-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49791) Sometime I get Temporary failure in name resolution

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sometime I get Temporary failure in name resolution   
 

  
 
 
 
 

 
 AFAICT it is an issue with name servers or your network configuration. E.g. see https://serverfault.com/questions/266042/temporary-failure-in-name-resolution  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49770) publish-over-ssh not saving settings

[strajan.sebast...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Strajan Sebastian commented on  JENKINS-49770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: publish-over-ssh not saving settings   
 

  
 
 
 
 

 
 Same here, just completed the bug report and found this bug report  In case more info is needed you can find it below.    Environment  user@sname:~# cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS" NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial user@sname:~# uname -a Linux sname 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux user@sname:~# dpkg --list | grep -i java ii  ca-certificates-java 20160321ubuntu1    all  Common CA certificates (JKS keystore) ii  default-jre-headless 2:1.8-56ubuntu2    amd64    Standard Java or Java compatible Runtime (headless) ii  java-common  0.56ubuntu2    all  Base package for Java runtimes ii  _javascript_-common    11 all  Base support for _javascript_ library packages ii  libjs-openlayers 2.13.1+ds2-2   all  _javascript_ library for displaying map data in web browsers ii  openjdk-8-jre:amd64  8u151-b12-0ubuntu0.16.04.2 amd64    OpenJDK Java runtime, using Hotspot JIT ii  openjdk-8-jre-headless:amd64 8u151-b12-0ubuntu0.16.04.2 amd64    OpenJDK Java runtime, using Hotspot JIT (headless) user@sname:~# dpkg --list | grep -i openj ii  openjdk-8-jdk:amd64  8u151-b12-0ubuntu0.16.04.2 amd64    OpenJDK Development Kit (JDK) ii  openjdk-8-jdk-headless:amd64 8u151-b12-0ubuntu0.16.04.2 amd64    OpenJDK Development Kit (JDK) (headless) ii  openjdk-8-jre:amd64  8u151-b12-0ubuntu0.16.04.2 amd64    OpenJDK Java runtime, using Hotspot JIT ii  openjdk-8-jre-headless:amd64 8u151-b12-0ubuntu0.16.04.2 amd64    OpenJDK Java runtime, using Hotspot JIT (headless) user@sname:~# dpkg --list | grep -i jenkins ii  jenkins  2.89.4 all  Jenkins is an open source automation server which enables developers around the world to reliably automate  their development lifecycle processes of all kinds, including build, document, test, package, stage, deployment, static analysis and many more. Jenkins version 2.89.4 Plugin Name: Publish Over SSH Plugin version: 1.19    Description  In a job (Send build artifacts over SSH -> SSH Publishers) In the Transfers section: 'Remove prefix' or 'Remote directory' are not saved when apply or saved button is pressed. Tried from multiple browsers and it seems that that is not the problem. After downgrading the plug-in to version 1.

[JIRA] (JENKINS-49792) All branches being queried for each single build

[lpie...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Piedra-Márquez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49792  
 
 
  All branches being queried for each single build   
 

  
 
 
 
 

 
Change By: 
 Luis Piedra-Márquez  
 

  
 
 
 
 

 
 In order to retrieve revrision from a Head, a query for all existinng branches is done{code:java}@Overrideprotected SCMRevision retrieve(SCMHead head, TaskListener listener) throws IOException, InterruptedException {    final BitbucketApi bitbucket = buildBitbucketClient();    List branches = bitbucket.getBranches();{code}I think it is possible to obtain the revision from the API with a query for the specific Head .     This is causing heavy delays when starting builds, specially in Mercurial where branches cannot be deleted, they are just closed. Branches in API v2 is a paginated response, and in our case it is also hitting Bitbucket API rate limit.With Bitbucket Cloud API v1 this was not a problem becasue closed branches where not included in the response for all branches.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   

[JIRA] (JENKINS-49793) setGerritReview can only set a message on an unsuccesfull build

[postelmansr...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 roel postelmans created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49793  
 
 
  setGerritReview can only set a message on an unsuccesfull build   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 rsandell  
 
 
Components: 
 gerrit-trigger-plugin  
 
 
Created: 
 2018-02-28 12:08  
 
 
Labels: 
 gerrit  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 roel postelmans  
 

  
 
 
 
 

 
 setGerritReview can only set a message on an unsuccesfull build. We also want to set a message on a succesfull build. For example what the actual code coverage was, the size growth of the applications,..  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
 

[JIRA] (JENKINS-49363) How to streaming mp4 artifact on Jenkins build page

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 No response from the requester  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49363  
 
 
  How to streaming mp4 artifact on Jenkins build page   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-19465) Slave hangs while being launched

[ovidiu....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ovidiu-Florin Bogdan commented on  JENKINS-19465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slave hangs while being launched   
 

  
 
 
 
 

 
 The Support Core plugin gives empty logs for the slave in discussion. The slave node get's no connection attempt via ssh from the master. Getting the slave stack trace is not possible since the slave.jar is not being executed. I'm having no luck with the nsenter utility to enter and obtain the master stack trace. I need to restart the container holding master with --privileged to be able to get the stack trace. THis would be rather tricky. P.S. Symlinking /dev/urandom to /dev/random on the slave has no affect. I realize now that I should've done this on the master.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-19465) Slave hangs while being launched

[ovidiu....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ovidiu-Florin Bogdan edited a comment on  JENKINS-19465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slave hangs while being launched   
 

  
 
 
 
 

 
 The Support Core plugin gives empty logs for the slave in discussion.The slave node get's no connection attempt via ssh from the master. Getting the slave stack trace is not possible since the slave.jar is not being executed.I'm having no luck with the *nsenter* utility to enter and obtain the master stack trace. I need to restart the container holding master with --privileged to be able to get the stack trace. THis would be rather tricky. - P.S. Symlinking  *  /dev/urandom *  to  *  /dev/random *  on the slave has no affect. I realize now that I should've done this on the master. -*/dev/random* on master has enough entropy, it works just fine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47978) Lightweight checkout not working for branches that contain forward slash '/'

[bjorn.roh...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 bjorn rohlen commented on  JENKINS-47978  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lightweight checkout not working for branches that contain forward slash '/'   
 

  
 
 
 
 

 
 Well, unfortunately it does not, as confirmed by Vivek and myself. This is still an issue and breaking projects.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins

[serg.berezh...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergey Berezhnoy commented on  JENKINS-49396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins   
 

  
 
 
 
 

 
 Job Configuration History Plugin is completely unusable due to this bug.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37220) Job DSL analogue of multibranch projects & organization folders

[costincarai...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Costin Caraivan edited a comment on  JENKINS-37220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job DSL analogue of multibranch projects & organization folders   
 

  
 
 
 
 

 
 I don't know if the aim here is to "kill job DSL", but it should be .  :)  There's a brand new code-oriented approach to Jenkins, the Jenkins Pipeline. There's a brand spanking new UI for it, Blue Ocean. But we can't really use it. Why? Because some things  are  not quite pipelines, they're more like Jenkins being used as a fancy cron.  I want  We would like  to store all those in version control.  I don't want to  We would rather not  make a new repo for each  one  Jenkinsfile .  I don't want to  We would rather not  make a new branch for each  one  Jenkinsfile . I just want We would prefer  to plonk  them  the Jenkinsfiles  somewhere in git and have new pipelines be generated for them.  I want me and my Ideally a  team  wanting  to  script Jenkins would  use only 1.5 Groovy DSLs instead of the 3 (! !!  :( ) Groovy DSLs we have to use right now: declarative (+scripting only when needed) vs declarative + scripting + Job DSL... The way I see it, just make it so the multibranch pipeline accepts multiple Jenkinsfiles, including the possibility of wildcards. That way every job configured just goes *.jenkinsfile and everything automagically works from end-to-end.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-37220) Job DSL analogue of multibranch projects & organization folders

[costincarai...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Costin Caraivan edited a comment on  JENKINS-37220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job DSL analogue of multibranch projects & organization folders   
 

  
 
 
 
 

 
 I don't know if the aim here is to "kill job DSL", but it should be :) There's a brand new code-oriented approach to Jenkins, the Jenkins Pipeline. There's a brand spanking new UI for it, Blue Ocean. But we can't really use it. Why? Because some things are not quite pipelines, they're more like Jenkins being used as a fancy cron. We would like to store all those in version control. We would rather not make a new repo for each Jenkinsfile. We would rather not make a new branch for each Jenkinsfile.We would prefer to plonk the Jenkinsfiles somewhere in git and have new pipelines be generated for them. Ideally a team wanting to script Jenkins would use only 1.5 Groovy DSLs instead of the 3  Groovy DSLs  (! :()  Groovy DSLs  we have to use right now: declarative (+scripting only when needed) vs declarative + scripting + Job DSL...  The way I see it As a simple solution ,  just make  maybe  it  so 's possible to make  the multibranch pipeline  accepts  accept  multiple Jenkinsfiles , including . Ideally  the  possibility of  inclusion would be done with  wildcards. That way every job configured just goes *.jenkinsfile and everything automagically works from end-to-end.  I have no idea about the full UX impact, though.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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...@google

[JIRA] (JENKINS-49748) support migrating implementation for same Pipeline keyword

[nicolas.del...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas De Loof commented on  JENKINS-49748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support migrating implementation for same Pipeline keyword   
 

  
 
 
 
 

 
 I expected we could switch to a complete distinct implementation for "agent:docker" implementation but would require SymbolLookup#findDescriptor to return a list of candidates, not just a single matching instance, then check which one offer best match for configured options. Andrew Bayer do you think it would make sense to follow up in this direction and prepare a PR for structs-plugin ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49745) Too many CrumbFilter log entries per second

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-49745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Too many CrumbFilter log entries per second   
 

  
 
 
 
 

 
 I'm glad my extra research helped identify the culprit (dashboard-view). I'm not familiar enough with Jelly to know exactly what's going on but it looks like some of the problems are: 
 
It doesn't check the return value (or try/catch if done that way) in case there is an error (e.g. a 403). 
It fetches everything, even if only some items are needed. 
This stuff, if everything is needed, could be returned as a single struct. 
 It also seems wrong that if the permission for Jenkins are such that anyone (anonymous) can view a URL, then GET requests for that URL shouldn't need a CSRF token and should never raise a 403.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49745) Too many CrumbFilter log entries per second

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje edited a comment on  JENKINS-49745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Too many CrumbFilter log entries per second   
 

  
 
 
 
 

 
 I'm glad my extra research helped identify the culprit (dashboard-view).I'm not familiar enough with Jelly to know exactly what's going on but it looks like some of the problems are:* It doesn't check the return value (or {{try}}/{{catch}} if done that way) in case there is an error (e.g. a 403).   This means there is nothing to bounce the page to the login page (if it requires auth) or refetch a CSRF token. * It fetches everything, even if only some items are needed.* This stuff, if everything is needed, could be returned as a single struct. * Did I miss anything?  I'm not familiar with how the CSRF stuff is implemented in Jenkins.   It also seems wrong that if the permission for Jenkins are such that anyone (anonymous) can view a URL, then {{GET}} requests for that URL shouldn't need a CSRF token and should never raise a 403.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49794) BooleanParam default value is always true

[valentina.armen...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 valentina armenise created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49794  
 
 
  BooleanParam default value is always true   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-02-28 14:09  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 valentina armenise  
 

  
 
 
 
 

 
 My pipeline defines a parameter with sth like:     

 
parameters {
 booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?')
 } 

     Printing the param value with 

 

script {
 if (params.RUN_TESTS) {
 echo "true: $RUN_TESTS"
 }
 else echo "false: $RUN_TESTS"
 } 

 shows that the value is always TRUE and the tests are always executed.   I think this is somewhat related to  I think this is somewhat related to https://issues.jenkins-ci.org/browse/JENKINS-36543       
 

  
 
 
 
 

 
 
 

 
  

[JIRA] (JENKINS-49794) BooleanParam default value is always true

[valentina.armen...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 valentina armenise updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49794  
 
 
  BooleanParam default value is always true   
 

  
 
 
 
 

 
Change By: 
 valentina armenise  
 

  
 
 
 
 

 
 My pipeline defines a parameter with sth like:    {noformat}parameters { booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?') }{noformat}    Printing the param value with{code:java}script { if (params.RUN_TESTS) { echo "true: $RUN_TESTS" } else echo "false: $RUN_TESTS" }{code}shows that the value is always TRUE and the tests are always executed.   I think this is somewhat related to  I think this is somewhat related to  https://issues.jenkins-ci.org/browse/JENKINS-36543     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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 http

[JIRA] (JENKINS-49794) BooleanParam default value is always true

[valentina.armen...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 valentina armenise updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49794  
 
 
  BooleanParam default value is always true   
 

  
 
 
 
 

 
Change By: 
 valentina armenise  
 
 
Component/s: 
 workflow-job-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49795) Bad serialization of ParametersAction.parameterDefinitionNames

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49795  
 
 
  Bad serialization of ParametersAction.parameterDefinitionNames   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 core  
 
 
Created: 
 2018-02-28 14:12  
 
 
Labels: 
 lts-candidate  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 Splitting out of JENKINS-49573 at Oleg Nenashev's request. See that issue for discussion.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
   

[JIRA] (JENKINS-18741) Add support of user groups as owners and co-owners

[jdav...@yahoo.ca (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan David commented on  JENKINS-18741  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support of user groups as owners and co-owners   
 

  
 
 
 
 

 
 This feature would be great to have, specially for those using AD / LDAP.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49794) BooleanParam default value is always true

[valentina.armen...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 valentina armenise updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49794  
 
 
  BooleanParam default value is always true   
 

  
 
 
 
 

 
Change By: 
 valentina armenise  
 
 
Attachment: 
 Screen Shot 2018-02-28 at 15.12.16.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49795) Bad serialization of ParametersAction.parameterDefinitionNames

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-49795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49794) BooleanParam default value is always true

[valentina.armen...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 valentina armenise commented on  JENKINS-49794  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BooleanParam default value is always true   
 

  
 
 
 
 

 
 plugin versions are attached as screenshot  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49795) Bad serialization of ParametersAction.parameterDefinitionNames

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-49795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49795  
 
 
  Bad serialization of ParametersAction.parameterDefinitionNames   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49795) Bad serialization of ParametersAction.parameterDefinitionNames

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49795  
 
 
  Bad serialization of ParametersAction.parameterDefinitionNames   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 lts-candidate  serialization xstream  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49573  
 
 
  Matrix Configuration Parameter Plugin is affected by JEP-200   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 core  
 
 
Labels: 
 JEP-200  lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49749) progress-bar isn't showing an estimate

[docw...@gerf.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Höltje commented on  JENKINS-49749  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: progress-bar isn't showing an estimate   
 

  
 
 
 
 

 
 I figured it was a duplicate, but I couldn't find any. Probably because I didn't use the right term(s).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49750) Promoted Builds plugin fails to trigger a downstream job

[john.mel...@esentire.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Mellor closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The update to 3.0.0 corrects the issue. Thanks Oleg!!!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49750  
 
 
  Promoted Builds plugin fails to trigger a downstream job   
 

  
 
 
 
 

 
Change By: 
 John Mellor  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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

[JIRA] (JENKINS-49750) Promoted Builds plugin fails to trigger a downstream job

[john.mel...@esentire.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Mellor edited a comment on  JENKINS-49750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Promoted Builds plugin fails to trigger a downstream job   
 

  
 
 
 
 

 
 The update to 3.0 .0  corrects the issue.  Thanks Oleg!!!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-35988) Equivalent to polling commit exclusions for branch indexing

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-35988  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Equivalent to polling commit exclusions for branch indexing   
 

  
 
 
 
 

 
 Some more discussion in git PR 573.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-35988) Equivalent to polling commit exclusions for branch indexing

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-35988  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Equivalent to polling commit exclusions for branch indexing   
 

  
 
 
 
 

 
 The currently best workaround I know of is to inspect currentBuild.changeSets from your Jenkinsfile and exit early. JENKINS-27092 would make that a bit easier, as well as allowing visualizations such as Blue Ocean to automatically hide the build or fold it into an adjoining build with a normal completion status.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49796) git fetch timeout

[da...@raison.lu (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Raison created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49796  
 
 
  git fetch timeout
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2018-02-28 14:39  
 
 
Environment: 
 Jenkins 2.108, git-plugin 3.8.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 David Raison  
 

  
 
 
 
 

 
 This issue is similar to JENKINS-20750 and JENKINS-36269 but I'd like to reopen this since in our case it is not related to authentication and I can not reproduce these timeouts when manually running the git fetch command. Here's the output inside jenkins: 
 
Cloning the remote Git repository Cloning repository ssh://git@server/diffusion/project.git > git init  # timeout=10 Fetching upstream changes from ssh://git@server/diffusion/project.git > git --version # timeout=10 using GIT_SSH to set credentials Deprecated RSA key > git fetch --tags --progress ssh://git@server/diffusion/project.git +refs/heads/:refs/remotes/origin/ ERROR: Timeout after 10 minutes ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://git@server/diffusion/project.git +refs/heads/:refs/remotes/origin/" returned status code 143: stdout: 
 And here's running a timed manual execution: 
 
jenkins@fyrine:/tmp/foo$ git init Initialized empty Git repository in /tmp/foo/.git/ jenkins@fyrine:/tmp/foo$ time git fetch --tags --progress ssh://git@server/diffusion/project.git +refs/heads/:refs/remotes/origin/ remote: Counting objects: 40991, done. remote: Compress

[JIRA] (JENKINS-49796) git fetch timeout

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49796  
 
 
  git fetch timeout
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49796) git fetch timeout

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-49796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git fetch timeout
 

  
 
 
 
 

 
 If you set the timeout to a large value, does the fetch complete in Jenkins? If the fetch never completes in Jenkins (no matter the value of timeout), then if you have access to the process listing on the agent, check to see if the git process is getting any CPU time. If it is not, then the problem is likely related to credentials. If it is getting CPU time, then there should have been output during the 10 minute wait period as generated by the  

 
--progress 

  argument to the git command. Since you show no output from the  

 
--progress 

  argument, I suspect this is due to incorrect or missing credentials for that job. If that is the case, please close this bug report as "Not a defect" and ask the question in IRC or the mailing list.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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,

[JIRA] (JENKINS-44132) Random JNLP Agent disconnect

[funee...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 marlene cote commented on  JENKINS-44132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Random JNLP Agent disconnect   
 

  
 
 
 
 

 
 Seeing the same thing. When will this be fixed please? WARNING: LinkageError while performing UserRequest:RPCRequest(9,join) java.lang.NoClassDefFoundError: hudson/util/ProcessKillingVeto  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49796) git fetch timeout

[da...@raison.lu (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Raison commented on  JENKINS-49796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git fetch timeout
 

  
 
 
 
 

 
 Thanks Mark Waite for your reply. There's actually output, so maybe I shouldn't have cut of the output just there and it would have been useful to include the Java Stacktrace maybe, sorry for that. It goes till 88% at which time the timeout occurs. 
 
stderr: remote: Counting objects: 4976 remote: Counting objects: 5121 remote: Counting objects: 5267 remote: Counting objects: 5358 remote: Counting objects: 5392 remote: Counting objects: 5402 remote: Counting objects: 5470 remote: Counting objects: 5504 remote: Counting objects: 5522 remote: Counting objects: 5569 remote: Counting objects: 5596 remote: Counting objects: 5644 remote: Counting objects: 5714 remote: Counting objects: 5739 remote: Counting objects: 5794 remote: Counting objects: 5851 remote: Counting objects: 5933 remote: Counting objects: 5985 remote: Counting objects: 6049 remote: Counting objects: 6125 remote: Counting objects: 6195 remote: Counting objects: 6279 remote: Counting objects: 6378 remote: Counting objects: 9509 remote: Counting objects: 10820 remote: Counting objects: 10942 remote: Counting objects: 10959 remote: Counting objects: 11044 remote: Counting objects: 18770 remote: Counting objects: 36075 remote: Counting objects: 40357 remote: Counting objects: 40361 remote: Counting objects: 40396 remote: Counting objects: 40433 remote: Counting objects: 40497 remote: Counting objects: 40638 remote: Counting objects: 40731 remote: Counting objects: 40991, done.  […] Receiving objects: 88% (36112/40991), 80.83 MiB | 174.00 KiB/s Receiving objects: 88% (36112/40991), 80.89 MiB | 168.00 KiB/s Receiving objects: 88% (36112/40991), 81.14 MiB | 176.00 KiB/s Receiving objects: 88% (36112/40991), 81.30 MiB | 168.00 KiB/s Receiving objects: 88% (36112/40991), 81.58 MiB | 189.00 KiB/s Receiving objects: 88% (36112/40991), 81.71 MiB | 193.00 KiB/s Receiving objects: 88% (36112/40991), 81.80 MiB | 181.00 KiB/s Receiving objects: 88% (36112/40991), 81.96 MiB | 177.00 KiB/s Receiving objects: 88% (36112/40991), 82.18 MiB | 175.00 KiB/s  at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1120) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1203) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) ERROR: Error cloning remote repo 'origin'
 I will retry with the timeout set higher and attempt to observe CPU time on the git process.  
 

[JIRA] (JENKINS-44132) Random JNLP Agent disconnect

[funee...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 marlene cote edited a comment on  JENKINS-44132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Random JNLP Agent disconnect   
 

  
 
 
 
 

 
 Seeing the same thing.  When will this be fixed please?WARNING: LinkageError while performing UserRequest:RPCRequest(9,join)java.lang.NoClassDefFoundError: hudson/util/ProcessKillingVeto From the slave log:Feb 27, 2018 9:28:49 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedFeb 27, 2018 9:28:49 PM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:RPCRequest(9,join)java.lang.NoClassDefFoundError: hudson/util/ProcessKillingVeto at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:242) at hudson.util.ProcessTree$WindowsOSProcess.killRecursively(ProcessTree.java:429) at hudson.util.ProcessTree.killAll(ProcessTree.java:146) at hudson.Proc$LocalProc.destroy(Proc.java:384) at hudson.Proc$LocalProc.join(Proc.java:357) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1304) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:896) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:870) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:829) at hudson.remoting.UserRequest.perform(UserRequest.java:208) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:360) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Unknown Source)Caused by: java.lang.ClassNotFoundException: hudson.util.ProcessKillingVeto at java.net.URLClassLoader.findClass(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 22 moreFeb 27, 2018 9:28:50 PM hudson.remoting.Request$2 runWARNING: Failed to send back a reply to the request hudson.remoting.Request$2@1d3c6b1hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:667) at hudson.remoting.Request$2.run(Request.java:372) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Unknown Source)Caused by: java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1800(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:264) ... 4 moreFeb 27, 2018 9:28:59 PM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$2$1 onReconnectINFO: Restarting agent via jenkins.slaves.restarter.WinswSlaveRestarter@1c0296c  
 

  
   

[JIRA] (JENKINS-44132) Random JNLP Agent disconnect

[funee...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 marlene cote edited a comment on  JENKINS-44132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Random JNLP Agent disconnect   
 

  
 
 
 
 

 
 Seeing the same thing.   Tried setting the display and power settings with no effect.   When will this be fixed please?WARNING: LinkageError while performing UserRequest:RPCRequest(9,join)java.lang.NoClassDefFoundError: hudson/util/ProcessKillingVetoFrom the slave log:Feb 27, 2018 9:28:49 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedFeb 27, 2018 9:28:49 PM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:RPCRequest(9,join)java.lang.NoClassDefFoundError: hudson/util/ProcessKillingVeto at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:242) at hudson.util.ProcessTree$WindowsOSProcess.killRecursively(ProcessTree.java:429) at hudson.util.ProcessTree.killAll(ProcessTree.java:146) at hudson.Proc$LocalProc.destroy(Proc.java:384) at hudson.Proc$LocalProc.join(Proc.java:357) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1304) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:896) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:870) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:829) at hudson.remoting.UserRequest.perform(UserRequest.java:208) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:360) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Unknown Source)Caused by: java.lang.ClassNotFoundException: hudson.util.ProcessKillingVeto at java.net.URLClassLoader.findClass(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:157) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 22 moreFeb 27, 2018 9:28:50 PM hudson.remoting.Request$2 runWARNING: Failed to send back a reply to the request hudson.remoting.Request$2@1d3c6b1hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:667) at hudson.remoting.Request$2.run(Request.java:372) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Unknown Source)Caused by: java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1800(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:264) ... 4 moreFeb 27, 2018 9:28:59 PM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$2$1 onReconnectINFO: Restarting agent via jenkins.slaves.restarter.WinswSlaveRestarter@1c0296c  
 

   

[JIRA] (JENKINS-49796) git fetch timeout

[da...@raison.lu (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Raison commented on  JENKINS-49796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git fetch timeout
 

  
 
 
 
 

 
 Yes, I can confirm it gets CPU time.  This time around it completed the checkout after only 15 secs, so it's not a consistent behavior.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-45901) Allow common groovy annotation in Pipeline Shared Library Classes

[mko...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Kobit commented on  JENKINS-45901  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow common groovy annotation in Pipeline Shared Library Classes   
 

  
 
 
 
 

 
 The issue description looks to me like it is only for shared libraries, but I would like to just clarify that these transformations would be very useful for pipeline definitions as well.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49796) git fetch timeout

[da...@raison.lu (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Raison commented on  JENKINS-49796  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git fetch timeout
 

  
 
 
 
 

 
 OK, on the third run, it gets only very little CPU time. After about 1 minute, we're at barely 1 second of CPU time for git and I'm sure it's going to time out. This is a 6 core server with a load of 0.95, so it's not waiting for IO or anything. Does this help you, what can we check from here?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM

[saad.a...@magna.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Saad Azam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49797  
 
 
  IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2018-02-28 15:04  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Saad Azam  
 

  
 
 
 
 

 
 Hi I am getting the following exception while trying to generate a pipeline job using JobDSL and loading my Jenkinsfile from Integrity SCM. Processing DSL script seed_job_component.groovy java.lang.IllegalArgumentException: Could not instantiate {configurationName=Pipeline_Definition, configPath=/Projects/xxx/xxx/xxx/xxx/xxx/project.pj, serverConfig=s...@xxx.com:} for IntegritySCM(serverConfig: String, configPath: String, configurationName: String, CPBasedMode?: boolean, alternateWorkspace?: String, browser?: IntegrityRepositoryBrowser{IntegrityWebUI(url: String)}, checkoutThreadPoolSize?: int, checkoutThreadTimeout?: int, checkpointBeforeBuild?: boolean, checkpointLabel?: String, cleanCopy?: boolean, deleteNonMembers?: boolean, excludeList?: String, fetchChangedWorkspaceFiles?: boolean, includeList?: String, lineTerminator?: String, localClient?: boolean, password?: String, restoreTimestamp?: boolean, skipAuthorInfo?: boolean, userName?: String): java.lang.reflect.InvocationTargetException at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:264) at org.jenkinsci.plugins.structs.describable.DescribableModel$instantiate$0.call(Unknown Source) at javaposse.jobdsl.plugin.structs.DescribableContext.createInstance(DescribableContext.groovy:50) at javaposse.jobdsl.plugin.structs.DescribableContext$createInstance.call(Unknown Source) at javaposse.jobdsl.plugin.ExtensionPointHelper$DescribableExtension.call(ExtensionPointHelper.groovy:117) at javaposse.jobdsl.plugin.JenkinsJobManagement.callExtension(JenkinsJobManagement.java:385) at javaposse.jobdsl.dsl.JobManagement$callExtension$1.call(Unknown Source) at javaposse.jobdsl.plugin.Interr

[JIRA] (JENKINS-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-49543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49543  
 
 
  Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-49543  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions   
 

  
 
 
 
 

 
 Though it certainly does not meet the usual “soak period” criteria, I would advocate backporting this to 2.107.1 since the fix seems pretty safe and demonstrably fixes a serious regression (compared to the previous LTS) for users in this environment. But waiting for 2.107.2 is probably acceptable as well if the issue is noted in the upgrade guide—the workaround after all is to just upgrade Tomcat (or stop using it altogether).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49798) Scan Organization Folder not detecting code changes

[kevin.f...@cookmedical.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Ford created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49798  
 
 
  Scan Organization Folder not detecting code changes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2018-02-28 15:22  
 
 
Environment: 
 Jenkins 2.109  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Kevin Ford  
 

  
 
 
 
 

 
 My scan organization folder is set to execute every 1 minutes.  It runs fine but is not detecting code changes and building my changes.  If i access the configure option and make a change to the configuration, that forces a scan, and my programs build.  Worked fine in 2.79  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[JIRA] (JENKINS-49798) Scan Organization Folder not detecting code changes

[kevin.f...@cookmedical.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Ford updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49798  
 
 
  Scan Organization Folder not detecting code changes   
 

  
 
 
 
 

 
Change By: 
 Kevin Ford  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47427) Poll per change with pipeline jobs

[dan...@resolutiongames.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Hagström commented on  JENKINS-47427  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Poll per change with pipeline jobs   
 

  
 
 
 
 

 
 +1 on this. I don't get why this is an option when it does nothing: the plugin pulls in all changelists since last in the build, rather than just the next one, right?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49062) Warning graph(s) are not drawn on dashboard

[jenk...@spoor.cc (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Spoor commented on  JENKINS-49062  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning graph(s) are not drawn on dashboard   
 

  
 
 
 
 

 
 We are experiencing exactly the same issue with the Parasoft plugin "warnings trend graph (new vs. fixed)" not being displayed anymore after upgrading the Static Analysis Utilities plugin from 1.92 --> 1.94. Jenkins err.log showed same errors. Downgrading Static Analysis Utilities plugin resolved our issue (for now).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47427) Poll per change with pipeline jobs

[dan...@resolutiongames.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Hagström updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47427  
 
 
  Poll per change with pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Daniel Hagström  
 
 
Comment: 
 +1 on this. I don't get why this is an option when it does nothing: the plugin pulls in all changelists since last in the build, rather than just the next one, right?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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.