date:20180307

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49751  
 
 
  NPE in workflow-cps on saveOwner   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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-43785) Compatibility for tap plugin with pipeline plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43785  
 
 
  Compatibility for tap plugin with pipeline plugin   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Bruno P. Kinoshita  
 

  
 
 
 
 

 
 
 

 
 
 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-43785) Compatibility for tap plugin with pipeline plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43785  
 
 
  Compatibility for tap plugin with pipeline plugin   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 newbie-friendly 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-50002) Artifactory plugin using entire artifact path for deploying URL

2018-03-07 Thread ey...@jfrog.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Ben Moshe edited a comment on  JENKINS-50002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifactory plugin using entire artifact path for deploying URL   
 

  
 
 
 
 

 
 Please try removing the ${WORKSPACE}/ prefix from you File Spec pattern value, leaving only: {code} "pattern": "App-${App_Version}.zip". {code} This change was the result of a major bug which was fixed a few months ago.The bug prevented the upload of files which are not located inside the workspace.We do our best to avoid behavior changes, but in this case, it was unavoidable.We applogise for the inconvenience caused by this. Please let us know if this resolves the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-50002) Artifactory plugin using entire artifact path for deploying URL

2018-03-07 Thread ey...@jfrog.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Ben Moshe edited a comment on  JENKINS-50002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifactory plugin using entire artifact path for deploying URL   
 

  
 
 
 
 

 
 Please try removing the $ \ {WORKSPACE}  / prefix from you File Spec pattern value, leaving only:{code :java }"pattern": "App-${App_Version}.zip" . {code}This change was the result of a major bug which was fixed a few months ago.The bug prevented the upload of files which are not located inside the workspace.We do our best to avoid behavior changes, but in this case, it was unavoidable.We applogise for the inconvenience caused by this. Please let us know if this resolves the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted

2018-03-07 Thread aa...@splatteredbits.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Jensen commented on  JENKINS-29616  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted   
 

  
 
 
 
 

 
 We were getting this error because our instance of Jenkins is served via HTTPS (no HTTP allowed). For some reason, default Java 1.8 can't connect. We had to download and install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files  and install its .jar files into $JAVA_HOME\lib\security. Once those files were in place, the agent was able to connect.  
 

  
 
 
 
 

 
 
 

 
 
 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-44989) Updating JIRA-issues deadlock

2018-03-07 Thread thomson....@razerzone.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomson Tat commented on  JENKINS-44989  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Updating JIRA-issues deadlock   
 

  
 
 
 
 

 
 We're seeing the same problem as well.  Seems to occur randomly.  Every now and then, it would update 50 to 200 unrelated JIRA tickets.  
 

  
 
 
 
 

 
 
 

 
 
 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-44989) Updating JIRA-issues deadlock

2018-03-07 Thread thomson....@razerzone.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomson Tat commented on  JENKINS-44989  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Updating JIRA-issues deadlock   
 

  
 
 
 
 

 
 We're seeing the same problem as well.  Seems to occur randomly.  Every now and then, it would update 50 to 200 unrelated JIRA tickets.  
 

  
 
 
 
 

 
 
 

 
 
 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-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step

2018-03-07 Thread svano...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I hope you don't mind if I come back and clean up by marking this as released with durable-task v2.20   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49754  
 
 
  Streams other than StdOut getting returned when using returnStdOut on PowerShell Step   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-45575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Will be in next release of workflow-cps - 2.46.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45575  
 
 
  Multiple assignment in pipeline fails with LHS Error   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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

[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-45575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multiple assignment in pipeline fails with LHS Error   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: Jenkinsfile pom.xml src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/78b137d8743ea3cf80ae302ec89f8aeabf3eb944 Log: Merge pull request #206 from abayer/jenkins-45575-jenkins-49679 [JENKINS-45575, JENKINS-49679] Test multiple assignment CPS fixes Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/57bda81325d5...78b137d8743e  
 

  
 
 
 
 

 
 
 

 
 
 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-49679) Return value unpacking in pipelinescript causes function to execute twice.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-49679  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Will be in next release of workflow-cps - 2.46.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49679  
 
 
  Return value unpacking in pipelinescript causes function to execute twice.   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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

[JIRA] (JENKINS-45575) Multiple assignment in pipeline fails with LHS Error

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-45575  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multiple assignment in pipeline fails with LHS Error   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/9a82584c267f84a4dce925a69d45ad6018196a0a Log: [JENKINS-45575, JENKINS-49679] Test multiple assignment CPS fixes Specifically https://github.com/cloudbees/groovy-cps/pull/81 and https://github.com/cloudbees/groovy-cps/pull/82  
 

  
 
 
 
 

 
 
 

 
 
 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-49679) Return value unpacking in pipelinescript causes function to execute twice.

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49679  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Return value unpacking in pipelinescript causes function to execute twice.   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: Jenkinsfile pom.xml src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/78b137d8743ea3cf80ae302ec89f8aeabf3eb944 Log: Merge pull request #206 from abayer/jenkins-45575-jenkins-49679 [JENKINS-45575, JENKINS-49679] Test multiple assignment CPS fixes Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/57bda81325d5...78b137d8743e  
 

  
 
 
 
 

 
 
 

 
 
 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-49679) Return value unpacking in pipelinescript causes function to execute twice.

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49679  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Return value unpacking in pipelinescript causes function to execute twice.   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/9a82584c267f84a4dce925a69d45ad6018196a0a Log: [JENKINS-45575, JENKINS-49679] Test multiple assignment CPS fixes Specifically https://github.com/cloudbees/groovy-cps/pull/81 and https://github.com/cloudbees/groovy-cps/pull/82  
 

  
 
 
 
 

 
 
 

 
 
 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-49826) Incorrect and confusing compilation of sets with custom types

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49826  
 
 
  Incorrect and confusing compilation of sets with custom types   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 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-49995) NotSerializableException with closures in case statements

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49995  
 
 
  NotSerializableException with closures in case statements   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 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-49968) Core 2.110 is unable to select a branch source via the server dropdown

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Core 2.110 is unable to select a branch source via the server dropdown   
 

  
 
 
 
 

 
 Let's give Ulli Hafner some time to review it.  We can always rollback on Friday if it is really needed.   
 

  
 
 
 
 

 
 
 

 
 
 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-50004) No more Oops!!! errors

2018-03-07 Thread ifernandezca...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50004  
 
 
  No more Oops!!! errors   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Components: 
 saml-plugin  
 
 
Created: 
 2018-03-07 21:09  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ivan Fernandez Calvo  
 

  
 
 
 
 

 
 now when an issue happens with the token, session, user, time, ... Jenkins shows an Ooops exception that it is pretty annoying, so to avoid this kind of stuff that use to be resolved activating the force authentication, I will try to allow users to re-authenticate in case that the session, token, or other weird stuff happens by invalidating the session and redirecting the user to the IdP. Also I will improve the error messages to point admins to the guides and to more specific errors.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-50003) Add logging allowing to track reasons for filtering out files from report

2018-03-07 Thread aquarell...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tatiana Didik created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50003  
 
 
  Add logging allowing to track reasons for filtering out files from report   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Tatiana Didik  
 
 
Components: 
 sonar-gerrit-plugin  
 
 
Created: 
 2018-03-07 19:36  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tatiana Didik  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are

[JIRA] (JENKINS-49968) Core 2.110 is unable to select a branch source via the server dropdown

2018-03-07 Thread rcampb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Campbell commented on  JENKINS-49968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Core 2.110 is unable to select a branch source via the server dropdown   
 

  
 
 
 
 

 
 Ulli Hafner It seems like your upgrade of Prototype 1.7.3 broke Jenkins validation logic.  
 

  
 
 
 
 

 
 
 

 
 
 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-49809) Create the Evergreen Status service data model

2018-03-07 Thread ty...@monkeypox.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy stopped work on  JENKINS-49809  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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-49842) Publish jenkins/evergreen docker image

2018-03-07 Thread ty...@monkeypox.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy stopped work on  JENKINS-49842  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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-49968) Core 2.110 is unable to select a branch source via the server dropdown

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Ulli Hafner  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49968  
 
 
  Core 2.110 is unable to select a branch source via the server dropdown   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Ulli Hafner  
 

  
 
 
 
 

 
 
 

 
 
 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-44992) SamlException after metadata update

2018-03-07 Thread ifernandezca...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-44992  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SamlException after metadata update   
 

  
 
 
 
 

 
 Daniel Watrous Open a new one, please attach the log when the issue is exposed with the loggers activated, also you can take a look at troubleshooting guide in the Azure section you have son setting to activate that resolve the issue, finally I wonder the Entry Id type that you have in your IdP Metadata we are tracking a similar issue with Azure on https://issues.jenkins-ci.org/browse/JENKINS-48030 case see the latest 10 comments.  
 

  
 
 
 
 

 
 
 

 
 
 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-26521) timeout step should support breaking on inactivity, not just a fixed duration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-26521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26521  
 
 
  timeout step should support breaking on inactivity, not just a fixed duration   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-49639) Sonar Gerrit plugin not posting comments when changedLinesOnly == true

2018-03-07 Thread aquarell...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tatiana Didik commented on  JENKINS-49639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sonar Gerrit plugin not posting comments when changedLinesOnly == true   
 

  
 
 
 
 

 
 ByChangedLinesPredicate works incorrectly when specified sub-project path. Needs to be checked and fixed for auto-match functionality 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49573  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Matrix Configuration Parameter Plugin is affected by JEP-200   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/security/ClassFilterImpl.java http://jenkins-ci.org/commit/jenkins/48c95f5aee999a7fbf6d30f3a1e92eabf3723a02 Log: s/JENKINS-49573/JENKINS-49795/g in messages.  
 

  
 
 
 
 

 
 
 

 
 
 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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bad serialization of ParametersAction.parameterDefinitionNames   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/security/ClassFilterImpl.java http://jenkins-ci.org/commit/jenkins/93b951046f95275f1a7d55e2e96392476b5a7a24 Log: Merge pull request #3332 from jglick/message-JENKINS-49795 s/JENKINS-49573/JENKINS-49795/g in messages Compare: https://github.com/jenkinsci/jenkins/compare/c5e96fb6180b...93b951046f95  
 

  
 
 
 
 

 
 
 

 
 
 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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49573  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Matrix Configuration Parameter Plugin is affected by JEP-200   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/security/ClassFilterImpl.java http://jenkins-ci.org/commit/jenkins/93b951046f95275f1a7d55e2e96392476b5a7a24 Log: Merge pull request #3332 from jglick/message-JENKINS-49795 s/JENKINS-49573/JENKINS-49795/g in messages Compare: https://github.com/jenkinsci/jenkins/compare/c5e96fb6180b...93b951046f95  
 

  
 
 
 
 

 
 
 

 
 
 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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bad serialization of ParametersAction.parameterDefinitionNames   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/security/ClassFilterImpl.java http://jenkins-ci.org/commit/jenkins/48c95f5aee999a7fbf6d30f3a1e92eabf3723a02 Log: s/JENKINS-49573/JENKINS-49795/g in messages.  
 

  
 
 
 
 

 
 
 

 
 
 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-49968) Core 2.110 is unable to select a branch source via the server dropdown

2018-03-07 Thread kshu...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-49968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Core 2.110 is unable to select a branch source via the server dropdown   
 

  
 
 
 
 

 
 Oleg Nenashev, I've bisected the changes and come to the following conclusion: 

 

✔ ~/GitHub/jenkins [:f1fc0f02ed|✔] 
14:57 $ git bisect good
5ed43002d7daca06676c565aab18c1842123281f is the first bad commit
commit 5ed43002d7daca06676c565aab18c1842123281f
Author: Ulli Hafner 
Date:   Thu Feb 1 21:17:34 2018 +0100

[FIXED JENKINS-49319] Upgrade to Prototype 1.7.3.

:04 04 8d40973073abf237c86765badafcadc58e1faeb7 64c7df1c2b29ed97b3436229e71369ae8ac95870 M	war
 

 I hope this is helpful!  
 

  
 
 
 
 

 
 
 

 
 
 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-49944) support some handling for skipped stages

2018-03-07 Thread a...@andreas-klemp-it.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Klemp commented on  JENKINS-49944  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support some handling for skipped stages   
 

  
 
 
 
 

 
 A finally post would suffice if I could get the status (e.g. failure, success, skipped). However, the resulting conditions would contradict the descriptive nature, I think. As I understand (in addition to your comment in JENKINS-47577) that you propose it like this? 

 

stage ('foo') {
  when {
...
  }
  steps {
...
  }
  post {
...
# run as usual when the stage is not skipped because of the when condition
  }
  skipped {
...
# run when the stage is skipped because of the when condition
  }
  finally {
...
# run in all cases after post/skipped or only after post when not skipped?
  }
} 

    
 

  
 
 
 
 

 
 
 

 
 
 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-44992) SamlException after metadata update

2018-03-07 Thread daniel.watr...@trinet.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Watrous commented on  JENKINS-44992  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SamlException after metadata update   
 

  
 
 
 
 

 
 I am also running 1.0.5 and provided the IdP URL provided. I also still regularly get this error. Should I submit a new issue, since this one list listed as resolved? When it happens the user has to go to office365, logout and then revisit the Jenkins server and login again.  
 

  
 
 
 
 

 
 
 

 
 
 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-12783) Delete workspace before build starts ignores Exlude patterns (for directories)

2018-03-07 Thread grimn...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Grim Reaper commented on  JENKINS-12783  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Delete workspace before build starts ignores Exlude patterns (for directories)   
 

  
 
 
 
 

 
 For those looking for a work around, I've use the following plugin: https://plugins.jenkins.io/preSCMbuildstep With the following Shell script to do the same thing as WS-cleanup. 

 

echo "Deleting..."
ls ${WORKSPACE}/ | egrep -v '*.build.*|suppressions.xml|reports' 
ls ${WORKSPACE}/ | egrep -v '*.build.*|suppressions.xml|reports' | xargs rm -rf
 

   The above deletes everything except the items in the "egrep" command (excludes).  
 

  
 
 
 
 

 
 
 

 
 
 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-50002) Artifactory plugin using entire artifact path for deploying URL

2018-03-07 Thread ey...@jfrog.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Ben Moshe commented on  JENKINS-50002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifactory plugin using entire artifact path for deploying URL   
 

  
 
 
 
 

 
 Please try removing the $ {WORKSPACE} / prefix from you File Spec pattern value, leaving only: "pattern": "App-$ {App_Version} .zip". This change was the result of a major bug which was fixed a few months ago. The bug prevented the upload of files which are not located inside the workspace. We do our best to avoid behavior changes, but in this case, it was unavoidable. We applogise for the inconvenience caused by this. Please let us know if this resolves the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-49947) unclear usage of input step in declarative pipeline

2018-03-07 Thread a...@andreas-klemp-it.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Klemp commented on  JENKINS-49947  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unclear usage of input step in declarative pipeline   
 

  
 
 
 
 

 
 The nested stage is an interesting hint. As far as I see, this is only possible with parallel, so ... yeah ... not optimal. But I'll give it a try with something like this. The downside is, that still only one (sequential) stage can be created. 

 

stage('Release Approval') {
   when {
 branch 'master'
   }
   parallel {
 stage('Release') {
   input {
 # manual approval of release
   }
   when {
 # the release is approved
   }
   steps {
 # release and deployment
   }
 }
  }
} 

    
 

  
 
 
 
 

 
 
 

 
 
 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-49968) Core 2.110 is unable to select a branch source via the server dropdown

2018-03-07 Thread rcampb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ryan Campbell edited a comment on  JENKINS-49968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Core 2.110 is unable to select a branch source via the server dropdown   
 

  
 
 
 
 

 
 [~drulli] It seems like your upgrade of Prototype 1.7.3 broke Jenkins validation logic. [~danielbeck] Perhaps we should just roll this back?  
 

  
 
 
 
 

 
 
 

 
 
 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-12353) Git command fails on Windows when git installed in default place (C:\Program Files\Git).

2018-03-07 Thread lainosan...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Laino Santos commented on  JENKINS-12353  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git command fails on Windows when git installed in default place (C:\Program Files\Git).   
 

  
 
 
 
 

 
 This happens because default installation configures Path variable to {git_dir}/cmd, where there is no git.exe. Change de Path to {git_dir}/bin. https://itsecureadmin.com/2011/05/jenkins-slave-on-windows-git-clone-failure/  
 

  
 
 
 
 

 
 
 

 
 
 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-45764) Add upload and download attachment steps

2018-03-07 Thread naresh.rayap...@yahoo.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati updated  JENKINS-45764  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45764  
 
 
  Add upload and download attachment steps   
 

  
 
 
 
 

 
Change By: 
 Naresh Rayapati  
 
 
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-28283) Setting up a checkout-script with cvs fails because of "Can't execute /usr/bin/ssh"

2018-03-07 Thread viswajak...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakkam Viswanath commented on  JENKINS-28283  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Setting up a checkout-script with cvs fails because of "Can't execute /usr/bin/ssh"   
 

  
 
 
 
 

 
 Hi, I am new to Jenkins and trying to connect to CVS by executing /bin/sh. It works from shell script though. But from Jenkins /bin/sh it is giving the following error.    [SIStudio] $ /bin/sh -xe /tmp/jenkins5825946314171956800.sh + cvs -d :pserver:JakUser:JakPass@HOST:/repository login Logging in to :pserver:JakUser@HOST:2401/sti cvs [login aborted]: connect to [HOST]:2401 failed: Permission denied Build step 'Execute shell' marked build as failure Any suggestions please? Thanks in advance. Jakkam  
 

  
 
 
 
 

 
 
 

 
 
 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-26521) timeout step should support breaking on inactivity, not just a fixed duration

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-26521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: timeout step should support breaking on inactivity, not just a fixed duration   
 

  
 
 
 
 

 
 I've resurrected ikedam's original PR and tweaked it slightly - it's up at https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/62  
 

  
 
 
 
 

 
 
 

 
 
 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-50001) Files not check in to PTC due to JEP-200 changes

2018-03-07 Thread carsten.sni...@hella.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Carsten Snider updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50001  
 
 
  Files not check in to PTC due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Carsten Snider  
 
 
Labels: 
 JEP-200  
 

  
 
 
 
 

 
 
 

 
 
 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-43785) Compatibility for tap plugin with pipeline plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-43785  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Compatibility for tap plugin with pipeline plugin   
 

  
 
 
 
 

 
 I am not sure what is missing there, we are using TAP plugin with Pipeline on our instance, it works well. One thing is missing though: Descriptor in Pipeline Publisher does not have a @Symbol annotation: https://github.com/jenkinsci/tap-plugin/blob/master/src/main/java/org/tap4j/plugin/TapPublisher.java#L668-L669 If it is implemented, the call pattern could be publishTap(testResults: "test-suite.log"). What needs to be done: 
 
Add a symbol 
Add a unit test, which would confirm that the new feature works correctly 
 It is a newbie-friendly issue IMO  
 

  
 
 
 
 

 
 
 

 
 
 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-49994) Report uses of anonymous classes in outgoing Remoting packets

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49994  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Report uses of anonymous classes in outgoing Remoting packets   
 

  
 
 
 
 

 
 Code changed in jenkins User: R. Tyler Croy Path: content/redirect/serialization-of-anonymous-classes.adoc http://jenkins-ci.org/commit/jenkins.io/30592f98d9aa1a982f39220013e60286e6f7c1b5 Log: Merge pull request #1439 from jglick/anonymous-warning-JENKINS-49994 JENKINS-49994 Set up a redirect for messages about serialization of anonymous classes Compare: https://github.com/jenkins-infra/jenkins.io/compare/a178b2b2c2b4...30592f98d9aa  
 

  
 
 
 
 

 
 
 

 
 
 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-49994) Report uses of anonymous classes in outgoing Remoting packets

2018-03-07 Thread syaramad...@scrippsnetworks.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49994  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Report uses of anonymous classes in outgoing Remoting packets   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: content/redirect/serialization-of-anonymous-classes.adoc http://jenkins-ci.org/commit/jenkins.io/11e02be65d669320d023a97bbefd3eb7f3ecbef9 Log: JENKINS-49994 Getting a redirect in place.  
 

  
 
 
 
 

 
 
 

 
 
 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-16285) exception during uploading big files to a CIFS share

2018-03-07 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 0.10  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-16285  
 
 
  exception during uploading big files to a CIFS share
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open 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-50005) WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information

Title: Message Title


 
 
 
 

 
 
 

 
   
 suryatej yaramada created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50005  
 
 
  WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-03-07 21:17  
 
 
Environment: 
 Jenkins - 2.89.3 running in AMAZONLINUX  We use SAML Plugin for oklta SSO login  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 suryatej yaramada  
 

  
 
 
 
 

 
 we frequently facing this issue . pelase let me know what needs to be done. Mar 07, 2018 7:03:18 PM hudson.Proc$LocalProc join WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information java.lang.Exception at hudson.Proc$LocalProc.join(Proc.java:334) at hudson.Proc.joinWithTimeout(Proc.java:170) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1986) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1709) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1620) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1611) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2772) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:672) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:631) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:391) at hudson.scm.SCM.poll(SCM.java:408) at hudson.model.AbstractProject._poll(AbstractProject.java:1384) at hudson.model.AbstractProject.poll(AbstractProject.java:1287) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:594) at

[JIRA] (JENKINS-49536) java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory

2018-03-07 Thread mirko.streckenb...@t-online.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mirko Streckenbach commented on  JENKINS-49536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory   
 

  
 
 
 
 

 
 Cyrille Le Clerc First of all: thanks for the information. This is a serious limitation, I wasn't expecting that. In most cases using "--file" will work, but I've seen a lot of maven builds that are sensitive to the current directory and/or have problems if --file is used (I remember the last case for some plugin that was support to update dependencies or versions in pom.xml and failed to find id). But I'm confident I'll find a solution for my project. Again, many thanks for you effort.  
 

  
 
 
 
 

 
 
 

 
 
 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-50002) Artifactory plugin using entire artifact path for deploying URL

Title: Message Title

Andrew Grether created an issue

Jenkins / JENKINS-50002

Artifactory plugin using entire artifact path for deploying URL

Issue Type:
Bug

Assignee:
Eyal Ben Moshe

Components:
artifactory-plugin

Created:
2018-03-07 18:57

Environment:
Jenkins 2.89.4 on Windows Server 2012 R2. Artifactory plugin 2.14.0.

Priority:
Major

Reporter:
Andrew Grether

Artifactory plugin is using the entire artifact file system path when attempting to deploy the artifact from a freestyle job using Job configuration File Spec. I believe the cause of the issue was upgrading Jenkins to 2.89.4 from 2.73.3, as this job has been working successfully before the upgrade (but I also upgraded plugins, not sure Artifactory plugin's dependencies). File spec looks like so: { "files": [ { "pattern": "${WORKSPACE}/App-${App_Version}.zip", "target": "my-repo/App/${App_Version}/", "recursive": "true", "flat" : "false" } ] } The artifact is properly identified in the job when run, but when it goes to deploy it uses the entire C:\ file system path in the URL. Log output looks like: For pattern: C:/Jenkins/jobs/app/workspace/app-version-1.6.11.zip 1 artifacts were found. Deploying artifact: https://server.com/artifactory/repos/app/1.6.11/C%3A/Jenkins/jobs/app/workspace/app-version-1.6.11.zip ERROR: Failed to deploy file. Status code: 500 Response message: Artifactory returned the following errors: Invalid path. ':' is not a valid name character: repos/app/1.6.11/C:/ Status code: 500 java.io.IOException: Failed to deploy file. Status code: 500 Response message: Artifactory returned the following errors: Invalid path. ':' is not a valid name character: repos/app/1.6.11/C:/ Status code: 500 at

[JIRA] (JENKINS-49826) Incorrect and confusing compilation of sets with custom types

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-49826  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Incorrect and confusing compilation of sets with custom types   
 

  
 
 
 
 

 
 Interesting - will investigate.  
 

  
 
 
 
 

 
 
 

 
 
 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-49994) Report uses of anonymous classes in outgoing Remoting packets

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-49994  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49994  
 
 
  Report uses of anonymous classes in outgoing Remoting packets   
 

  
 
 
 
 

 
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-49536) java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory

2018-03-07 Thread clecl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc commented on  JENKINS-49536  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.IllegalArgumentException: Cannot relativize ... relatively to ... when building a subdirectory with a module in a sibling directory   
 

  
 
 
 
 

 
 Mirko Streckenbach if "--file" is a problem, I also had in mind an alternative with "cd path/to && mvn ..." that Jesse Glick says may have unexpected behaviors: 

 

node {
   dir("my-maven-reactor-root-folder") {
  withMaven() {
 // less recommended than "mvn -f path/to/pom.xml clean verify"
 sh "cd path/to && mvn clean verify"
  }
   }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 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-49925) Sonar-Gerrit plugin not filtering issues

2018-03-07 Thread aquarell...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tatiana Didik commented on  JENKINS-49925  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sonar-Gerrit plugin not filtering issues   
 

  
 
 
 
 

 
 Please check if it is the same case as JENKINS-49639 If you believe the problem is different, you can e-mail developers (me) directly using the e-mail provided on the plugin wiki page. To help you with troubleshooting I need 1) your pipeline code or screenshot of your plugin settings; 2) name of the file with an issue ignored; 3) lines from your sonar-report file regarding this issue.   
 

  
 
 
 
 

 
 
 

 
 
 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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-49794  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BooleanParam default value is always true   
 

  
 
 
 
 

 
 Hrm, I can't reproduce this running the following: ``` pipeline { agent any parameters  { booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?') }  stages { stage('foo') { steps { script { if (params.RUN_TESTS) { echo "true: $ {params.RUN_TESTS}" } else echo "false: ${params.RUN_TESTS} " }  } } } } ```  
 

  
 
 
 
 

 
 
 

 
 
 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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer edited a comment on  JENKINS-49794  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BooleanParam default value is always true   
 

  
 
 
 
 

 
 Hrm, I can't reproduce this running the following: ``` {code} pipeline {agent anyparameters {booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?')}stages {stage('foo') {steps {script {if (params.RUN_TESTS) { echo "true: ${params.RUN_TESTS}"}else echo "false: ${params.RUN_TESTS}"}}}}} ``` {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-49763) Duration time is incorrect in a parallel pipeline step.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49763  
 
 
  Duration time is incorrect in a parallel pipeline step.   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 pipeline-graph-analysis-plugin  
 
 
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-48879) User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Meredith assigned an issue to Vivek Panday  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48879  
 
 
  User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.   
 

  
 
 
 
 

 
Change By: 
 Ivan Meredith  
 
 
Assignee: 
 Ivan Meredith Vivek Panday  
 

  
 
 
 
 

 
 
 

 
 
 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-47681) Pipeline with parallel jobs hang with EC2 plugin

2018-03-07 Thread marc...@marcmac.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 marc macintyre commented on  JENKINS-47681  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline with parallel jobs hang with EC2 plugin   
 

  
 
 
 
 

 
 I'm pretty sure the issue here is that when provisioning multiple instances in one batch, we attempt to reuse existing instances.  The first one launches, and all subsequent calls in that batch find the same (just launched) instance, and return that.     I've submitted a pull request that tracks the list of provisioned slaves in a batch, and prevents the provisioning logic from returning the same instance multiple times.  
 

  
 
 
 
 

 
 
 

 
 
 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-49715) Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject   
 

  
 
 
 
 

 
 Code changed in jenkins User: jdamick Path: Jenkinsfile pom.xml src/main/java/biz/neustar/jenkins/plugins/packer/PackerInstallation.java src/main/resources/biz/neustar/jenkins/plugins/packer/PackerFileEntry/config.jelly src/main/resources/biz/neustar/jenkins/plugins/packer/PackerInstallation/config.jelly src/main/resources/biz/neustar/jenkins/plugins/packer/PackerPublisher/config.jelly src/main/resources/index.jelly src/test/java/biz/neustar/jenkins/plugins/packer/PackerInstallationTest.java src/test/java/biz/neustar/jenkins/plugins/packer/PackerJenkinsPluginTest.java http://jenkins-ci.org/commit/packer-plugin/f318a252cdf15b9d0e09e25e925853e1e6a1d538 Log: Merge pull request #22 from jglick/updates-JENKINS-49715 JENKINS-49715 Facelift & JEP-200 fix Compare: https://github.com/jenkinsci/packer-plugin/compare/f8e4347d6530...f318a252cdf1  
 

  
 
 
 
 

 
 
 

 
 
 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-44334) Pipeline: Job v2.11 breaks build with bat() command

2018-03-07 Thread aherit...@apache.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-44334  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline: Job v2.11 breaks build with bat() command   
 

  
 
 
 
 

 
 My 2 cents Andrew Bayer: 
 
I agree with Jesse Glick, we should change the behavior if possible, but for this we should need to have a test/documentation explaining the existing (or expected) behavior. 
Environment variables can be set at many levels and I think that the most general one should be overridable by the most local one (but maybe not ). 
 
Thus the var defined at the master level could be redefined at the folder level and at the job level. 
But it could also be defined at the agent config level (in that case it overrides the master value but the folder/job can override it). 
There is also the operating system / shell level from which we launch the JVM or a command/shell. 
  
I'm not talking about the envinject plugin which can reset or redefine them at various levels (let's focus on core behaviors) 
I'm not talking about all others plugins which are just contributing by adding some entries in the PATH or by adding some others environment variables. 
We have to take care that PATH (and perhaps few others env var like HOME, USER...) is probably a specific case where the expected behavior could be different than for some others vars because it is has a huge impact at the system level, is often OS dependent and might need a different approach (for PATH maybe you would prefer append than override - or not again ) 
With a real environment (I'm not able to judge about the unit test) I was easily breaking a sh() step with a master/agent on linux by adding a crappy PATH entry (d:) as global env on the master 2.89.x with pipeline job 2.17 
 HTH   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json

2018-03-07 Thread imes...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 K C commented on  JENKINS-28877  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Plugin unable to parse Bitbucket webhook response json   
 

  
 
 
 
 

 
 I just added the On Push event, then merged a pull request. While I saw more logs on Jenkins, it failed to match the git url: https:///~/.git<-->https:///users//repos//browse   But what we are trying to do is trigger a build on Jenkins when someone creates, not merges, a pull request on Bitbucket. Is this use case supported? Can it be supported? Thank you  
 

  
 
 
 
 

 
 
 

 
 
 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-50005) WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information

2018-03-07 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50005  
 
 
  WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information   
 

  
 
 
 
 

 
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-48027) Blue Ocean dashboard showing no Pipelines

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Meredith updated  JENKINS-48027  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48027  
 
 
  Blue Ocean dashboard showing no Pipelines   
 

  
 
 
 
 

 
Change By: 
 Ivan Meredith  
 
 
Status: 
 In Review 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.com/d/optout.

[JIRA] (JENKINS-49968) Core 2.110 is unable to select a branch source via the server dropdown

2018-03-07 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-49968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Core 2.110 is unable to select a branch source via the server dropdown   
 

  
 
 
 
 

 
 The specific error in the console appears to have been reported as https://github.com/sstephenson/prototype/issues/329. I will try a similar patch to see if it fixes the issue.  
 

  
 
 
 
 

 
 
 

 
 
 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-48478) Nunit: Display output from testcase in generated report

2018-03-07 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-48478  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Nunit: Display output from testcase in generated report   
 

  
 
 
 
 

 
 I'm trying to do a release now, but running into some issues.  
 

  
 
 
 
 

 
 
 

 
 
 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-50002) Artifactory plugin using entire artifact path for deploying URL

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Grether resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed with config change  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50002  
 
 
  Artifactory plugin using entire artifact path for deploying URL   
 

  
 
 
 
 

 
Change By: 
 Andrew Grether  
 
 
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 this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit

[JIRA] (JENKINS-50001) Files not check in to PTC due to JEP-200 changes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50001  
 
 
  Files not check in to PTC due to JEP-200 changes   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 PTC ALM Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 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-50001) Files not check in to PTC due to JEP-200 changes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-50001  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
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-29387) Cannot sync into workspaces with '@' in their path

2018-03-07 Thread jbr...@perforce.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Brown commented on  JENKINS-29387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot sync into workspaces with '@' in their path   
 

  
 
 
 
 

 
 Jay Spang you wrote "Jenkins appends '@2'  to the workspace" Does the above -Dhudson.slaves.WorkspaceList=_ help out as an alternative char to the "@"?  That should obviate the need for the escaping Paul did.  
 

  
 
 
 
 

 
 
 

 
 
 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-50005) WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Mark Waite  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50005  
 
 
  WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-50006) Kubernetes agent max number of instances no longer working

2018-03-07 Thread shenron...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rong Shen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50006  
 
 
  Kubernetes agent max number of instances no longer working   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2018-03-08 00:12  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Rong Shen  
 

  
 
 
 
 

 
 I noticed that I set one slave template max number of instances to be 10, set container cap to 20. However slaves from that template did not get restricted, it launched more than 20 instances in k8s cluster, causing unexpected heavy load.   We've been using this number before, and it was working quite well until recently. Is this a regression?   Thanks   Kubernetes-plugin version: 1.1 Jenkins version: 2.89 Kubernetes version: 1.9  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-46379) withEnv mess with Job parameter (not case sensitive)

2018-03-07 Thread zxj...@126.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi commented on  JENKINS-46379  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withEnv mess with Job parameter (not case sensitive)   
 

  
 
 
 
 

 
 You just use the case that your last post? I can retry it. Kevin Raymond  
 

  
 
 
 
 

 
 
 

 
 
 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-49370) Environment variables cannot be set within the container step

2018-03-07 Thread dszobosz...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dániel Szoboszlay commented on  JENKINS-49370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment variables cannot be set within the container step   
 

  
 
 
 
 

 
 Yes, all my examples are now working as expected with version 1.3.2 of the 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-50001) Files not check in to PTC due to JEP-200 changes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-50001  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50001  
 
 
  Files not check in to PTC due to JEP-200 changes   
 

  
 
 
 
 

 
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-29387) Cannot sync into workspaces with '@' in their path

2018-03-07 Thread jaysp...@amazon.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang commented on  JENKINS-29387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot sync into workspaces with '@' in their path   
 

  
 
 
 
 

 
 Paul Allen sorry to bump a very old issue, but how can I use your fix when I'm using raw p4groovy to do more advanced stuff? I have a function called get_synced_changelist() that does exactly what the name implies. This code works fine except if the job runs on an executor other than 0. If that happens, Jenkins appends '@2'  to the workspace and p4groovy crashes when it tries to use that as the workspace root. Unless I'm missing something, I don't see any way to specify the client's root at the time of instantiation, so I don't know how to avoid this bug. Here's the code. The best way to repro this is to pin your job to a certain node, then Build it rapidly a few times (ensuring concurrent builds). Any build NOT on the first executor will fail.   def get_synced_changelist(String p4_credential_name, String client_name, String p4_stream) {     def ws = [$class: 'StreamWorkspaceImpl', charset: 'none', format: client_name, pinHost: false, streamName: p4_stream]     def p4 = p4(credential: p4_credential_name, workspace: ws) changelist = p4.run( 'changes', '-m1', "@"+ p4.getClientName() )     return changelist[0].change }   get_synced_changelist('p4tools', 'jenkins-${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}', '//depot/stream_name')          
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-20176) Disk usage plugin write job config.xml after every build

2018-03-07 Thread rhow...@control4.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rusty Howell commented on  JENKINS-20176  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Disk usage plugin write job config.xml after every build   
 

  
 
 
 
 

 
 This is still occurring with version 0.28 on Jenkins 2.89.4. All my DSL generated jobs constantly show the warning message about job being changed.  
 

  
 
 
 
 

 
 
 

 
 
 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-41074) UX Issue with Polling in Multibranch Pipeline

2018-03-07 Thread jvall...@bloomberg.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Justin Vallon commented on  JENKINS-41074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: UX Issue with Polling in Multibranch Pipeline   
 

  
 
 
 
 

 
 So, got it working.  On (enterprise) github, installed the "Jenkins (git plugin)" integration service which started calling the git-hook.  
 

  
 
 
 
 

 
 
 

 
 
 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-50002) Artifactory plugin using entire artifact path for deploying URL

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Grether edited a comment on  JENKINS-50002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifactory plugin using entire artifact path for deploying URL   
 

  
 
 
 
 

 
 Fixed with config change , feel free to close  
 

  
 
 
 
 

 
 
 

 
 
 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-50005) WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50005  
 
 
  WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 git-client-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-50005) WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information

2018-03-07 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title

Mark Waite commented on JENKINS-50005

Re: WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information

Please explain the conditions which cause that message to appear in your logs and why you believe that is critical. The stack trace shows that the git plugin is requesting the head revision of the remote repository. It calls git ls-remote to request the head revision. That is an authenticated call. Are the correct credentials provided to the Jenkins job? If not, does the problem resolve itself when correct credentials are provided? Is the Jenkins server reporting that so frequently that it is exhausting file descriptors and causing the Jenkins process to crash? What version of command line git are you using? What operating system and version is hosting the Jenkins instance? Is the hosting operating system current with most recent patches? Refer to "How to report an issue" for more details of the type of information needed in a bug report.

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-49639) Sonar Gerrit plugin not posting comments when changedLinesOnly == true

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sonar Gerrit plugin not posting comments when changedLinesOnly == true   
 

  
 
 
 
 

 
 Code changed in jenkins User: Tatiana Didik Path: src/main/java/org/jenkinsci/plugins/sonargerrit/config/AuthenticationConfig.java src/main/java/org/jenkinsci/plugins/sonargerrit/filter/predicates/ByChangedLinesPredicate.java src/test/java/org/jenkinsci/plugins/sonargerrit/config/NullValuesTest.java src/test/java/org/jenkinsci/plugins/sonargerrit/inspection/sonarqube/ChangedFilesTest.java src/test/java/org/jenkinsci/plugins/sonargerrit/inspection/sonarqube/CustomProjectPathAndFilePredicateMatchTest.java src/test/java/org/jenkinsci/plugins/sonargerrit/inspection/sonarqube/ProjectPathToGerritChangedLinesMatchTest.java src/test/java/org/jenkinsci/plugins/sonargerrit/inspection/sonarqube/ProjectPathToGerritFilenameMatchTest.java http://jenkins-ci.org/commit/sonar-gerrit-plugin/be36d7871d41dfdaea987d5218aaa662a0fb1f06 Log: JENKINS-49639 No issues remain in case when specified a project path and only changed lines are expected to be commented  
 

  
 
 
 
 

 
 
 

 
 
 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-50002) Artifactory plugin using entire artifact path for deploying URL

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Grether commented on  JENKINS-50002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifactory plugin using entire artifact path for deploying URL   
 

  
 
 
 
 

 
 Eyal Ben Moshe thanks, that did the trick. No need to apologize with that fast of a response.  
 

  
 
 
 
 

 
 
 

 
 
 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-50000) Finish user and consumer guide for branch-api

2018-03-07 Thread svano...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-5  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Finish user and consumer guide for branch-api   
 

  
 
 
 
 

 
 I feel like this JIRA needs a little more to it so we can celebrate the 50k milestone.   
 

  
 
 
 
 

 
 
 

 
 
 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-45280) duplicate build triggered by same github push notification when there is long scm polling

2018-03-07 Thread mkig...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hicks commented on  JENKINS-45280  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: duplicate build triggered by same github push notification when there is long scm polling   
 

  
 
 
 
 

 
 I am also seeing this behavior. We are using jenkins for feature branch build with 8 workers. Whenever resources get free, up to 4 of the same branch will start building.  
 

  
 
 
 
 

 
 
 

 
 
 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-42582) ssh-agent not applied in kubernetes container

2018-03-07 Thread dszobosz...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dániel Szoboszlay commented on  JENKINS-42582  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ssh-agent not applied in kubernetes container   
 

  
 
 
 
 

 
 Thank you Matthew Ludlum, this is awesome! Everything is working fine now with version 1.3.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-49110) withSonarQubeEnv in Jenkins pipeline not setting SonarQube env whe using Kubernetes

2018-03-07 Thread jenkins...@carlossanchez.eu (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49110  
 
 
  withSonarQubeEnv in Jenkins pipeline not setting SonarQube env whe using Kubernetes   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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-49370) Environment variables cannot be set within the container step

2018-03-07 Thread jenkins...@carlossanchez.eu (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49370  
 
 
  Environment variables cannot be set within the container step   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Status: 
 Open 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-49968) Core 2.110 is unable to select a branch source via the server dropdown

2018-03-07 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum edited a comment on  JENKINS-49968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Core 2.110 is unable to select a branch source via the server dropdown   
 

  
 
 
 
 

 
 The specific error in the console appears to have been reported as https://github.com/sstephenson/prototype/issues/329. I will try a similar patch to see if it fixes the issue. EDIT: With that patch I get a different error (in lib.form.select/select.js), so I'm not sure if it's worth the work to fix the issue vs reverting.  
 

  
 
 
 
 

 
 
 

 
 
 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-29387) Cannot sync into workspaces with '@' in their path

2018-03-07 Thread jaysp...@amazon.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang commented on  JENKINS-29387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot sync into workspaces with '@' in their path   
 

  
 
 
 
 

 
 Joel Brown I'm a bit reluctant to change a whole system property to fix this issue, but if Paul Allen says there's no easy way to do this with p4groovy, I'll definitely give that a try!  
 

  
 
 
 
 

 
 
 

 
 
 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-45387) Setup wizard hangs when email not entered

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-45387  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Setup wizard hangs when email not entered   
 

  
 
 
 
 

 
 Code changed in jenkins User: Literallie Path: core/src/main/java/hudson/security/AccountCreationFailedException.java core/src/main/java/hudson/security/HudsonPrivateSecurityRealm.java core/src/main/java/jenkins/install/SetupWizard.java war/src/main/js/pluginSetupWizardGui.js war/src/main/js/templates/firstUserPanel.hbs http://jenkins-ci.org/commit/jenkins/12031d7d59409186c8c36ac791736e475a883dc2 Log: JENKINS-45387 Fix validation error displaying in setup wizard's "create first admin" form (#3116) 
 
JENKINS-45387 Improve setup wizard account creation in security realm 
 This commit adds an additional account creation method to the security realm, that allows to create a new user account (as the system) and is intended to be used by the setup wizard. The main difference to the existing method is that the new method does not force the Stapler to send a response, but instead throws an exception if invalid data is submitted. This allows to call this from the setup wizard, and send the response there. (This is necessary because the setup wizard method has a response return type and there is no way to access the response already send in the realm) Further, it splits the private createAccount() method for clarity as well as to allow code reuse from the new method. 
 
JENKINS-45387 Fix SetupWizard sending responses twice on create admin 
 This commit fixes an issue where the SetupWizard class would send two responses (indirectly) when invalid form data was provided for creating the first admin account. 
 
[Fix JENKINS-45387] Setup wizard not displaying first account errors 
 This commit fixes the setup wizard not displaying HTML error responses upon first account creation. Previously, it just froze (buttons were not re-enabled) and didn't display responses. (Probably caused by XSS policies on the iframe) 
 
JENKINS-45387 Add some @Restricted annotations 
 As per https://github.com/jenkinsci/jenkins/pull/3116#discussion_r172031063 https://github.com/jenkinsci/jenkins/pull/3116#discussion_r172051979  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-49931) Heap Histogram Collection Destabilizes Masters

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-49931  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49931  
 
 
  Heap Histogram Collection Destabilizes Masters   
 

  
 
 
 
 

 
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-48879) User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Meredith assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48879  
 
 
  User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.   
 

  
 
 
 
 

 
Change By: 
 Ivan Meredith  
 
 
Assignee: 
 Ivan Meredith Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 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-48879) User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Meredith assigned an issue to Ivan Meredith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48879  
 
 
  User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.   
 

  
 
 
 
 

 
Change By: 
 Ivan Meredith  
 
 
Assignee: 
 Vivek Panday Ivan Meredith  
 

  
 
 
 
 

 
 
 

 
 
 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")

2018-03-07 Thread dant...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran commented on  JENKINS-49632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")   
 

  
 
 
 
 

 
 it works. Looking forward with RegEx filtering. I have too many in the build .  Thank you!!!  
 

  
 
 
 
 

 
 
 

 
 
 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")

2018-03-07 Thread dant...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran edited a comment on  JENKINS-49632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")   
 

  
 
 
 
 

 
 it works . Looking forward with RegEx filtering. I have too many in the build :).  for single simple maven    Thank you!!!  project, but for complex multi-modules still facing missing files  
 

  
 
 
 
 

 
 
 

 
 
 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-46571) Update URL scheme to remove URL encoding issues

2018-03-07 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-46571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update URL scheme to remove URL encoding issues   
 

  
 
 
 
 

 
 Ivan Meredith keep in mind the pipeline name itself may require some encoding (not sure if that changes things).   
 

  
 
 
 
 

 
 
 

 
 
 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-46571) Update URL scheme to remove URL encoding issues

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Meredith assigned an issue to Ivan Meredith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46571  
 
 
  Update URL scheme to remove URL encoding issues   
 

  
 
 
 
 

 
Change By: 
 Ivan Meredith  
 
 
Assignee: 
 Ivan Meredith  
 

  
 
 
 
 

 
 
 

 
 
 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-46571) Update URL scheme to remove URL encoding issues