date:20180502

Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 

  
 
 
 
 

 
 As a Jenkins user, I would like to be able to set up a Pipeline or Multibranch Pipeline job such that when a Github/(Enterprise) Pull Request is Approved, the job is triggered.A similar capability exists in the Github Pull Request Builder Plugin, where it communicates with the Github API and is able to trigger builds based off of specific text inside a Github comment. Screen shot attached. The screen shot illustrates a job which uses the GHPRB to trigger a build if a comment "Jenkins build this" is made in the PR, or skip the build if "Jenkins skip this" is found in the comment. In my use case, I don't want to scan the comment text, I want to trigger based on the state of the PR (i.e. "Approved " ).  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 
 
Attachment: 
 GHPRB Advanced options.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 
 
Summary: 
 Ability to trigger Pipelines on Github /  (Enterprise) Pull Request Acceptance  
 

  
 
 
 
 

 
 
 

 
 
 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-51097) Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance

Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github/(Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Change By: 
 M Chon  
 

  
 
 
 
 

 
 As a Jenkins user, I would like to be able to set up a Pipeline or Multibranch Pipeline job such that when a Github /  (Enterprise) Pull Request is Approved, the job is triggered.A similar capability exists in the Github Pull Request Builder Plugin, where it communicates with the Github API and is able to trigger builds based off of specific text inside a Github comment. Screen shot attached. The screen shot illustrates a job which uses the GHPRB to trigger a build if a comment "Jenkins build this" is made in the PR, or skip the build if "Jenkins skip this" is found in the comment. In my use case, I don't want to scan the comment text, I want to trigger based on the state of the PR (i.e. "Approved).  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-51097) Ability to trigger Pipelines on Github (Enterprise) Pull Request Acceptance

Title: Message Title


 
 
 
 

 
 
 

 
   
 M Chon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51097  
 
 
  Ability to trigger Pipelines on Github (Enterprise) Pull Request Acceptance   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-05-03 03:18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 M Chon  
 

  
 
 
 
 

 
 As a Jenkins user, I would like to be able to set up a Pipeline or Multibranch Pipeline job such that when a Github (Enterprise) Pull Request is Approved, the job is triggered. A similar capability exists in the Github Pull Request Builder Plugin, where it communicates with the Github API and is able to trigger builds based off of specific text inside a Github comment. Screen shot attached. The screen shot illustrates a job which uses the GHPRB to trigger a build if a comment "Jenkins build this" is made in the PR, or skip the build if "Jenkins skip this" is found in the comment. In my use case, I don't want to scan the comment text, I want to trigger based on the state of the PR (i.e. "Approved).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-46144) Update vault-java-driver version

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Tierno edited a comment on  JENKINS-46144  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update vault-java-driver version   
 

  
 
 
 
 

 
 From the README.md of the vault-java- driverL driver -  "*3.0.0*: This is a breaking-change release, with several updates."Tests hang during `com.datapipe.jenkins.vault.it.folder.FolderIT` , not sure why yet. will look into it. Is there a need to update to 3.0.0+ right now?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46144) Update vault-java-driver version

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Tierno commented on  JENKINS-46144  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update vault-java-driver version   
 

  
 
 
 
 

 
 From the README.md of the vault-java-driverL "3.0.0: This is a breaking-change release, with several updates." Tests hang during `com.datapipe.jenkins.vault.it.folder.FolderIT` , not sure why yet. will look into it. Is there a need to update to 3.0.0+ right now?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51096) Support external H2 database

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51096  
 
 
  Support external H2 database   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Cyrille Le Clerc  
 
 
Components: 
 pipeline-maven-plugin  
 
 
Created: 
 2018-05-03 02:54  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Cyrille Le Clerc  
 

  
 
 
 
 

 
 In addition to the embedded H2 database, support connection to external H2 databases.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-50328) Pipeline editor not working if Script Path is set

2018-05-02 Thread zhaos...@shanghai-electric.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Zhao commented on  JENKINS-50328  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline editor not working if Script Path is set   
 

  
 
 
 
 

 
 Have the same problem. Only can build with a different Jankinsfile name. Can't modify pipeline by pipeline-editor.  
 

  
 
 
 
 

 
 
 

 
 
 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-50199) Failed pipeline jobs stuck running after incorrect resume

2018-05-02 Thread mkoz...@magento.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Kozell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50199  
 
 
  Failed pipeline jobs stuck running after incorrect resume   
 

  
 
 
 
 

 
Change By: 
 Mike Kozell  
 
 
Attachment: 
 flownode-84.xml  
 

  
 
 
 
 

 
 
 

 
 
 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-35660) QTestLib time information is lost

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-35660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: QTestLib time information is lost   
 

  
 
 
 
 

 
 Code changed in jenkins User: kpop Path: src/main/resources/org/jenkinsci/plugins/xunit/types/qtestlib-to-junit-5.xsl src/test/java/org/jenkinsci/plugins/xunit/types/QTestlibTypeTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/qtestlib/testcase3/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/qtestlib/testcase3/result.xml http://jenkins-ci.org/commit/xunit-plugin/9c9d03aa8333f81b2b9f428f4b9ade8bb5820313 Log: JENKINS-35660 QTestLib time information is lost Use a converter function in XSLT to convert msec attribute of duration element for QtTest  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-35660) QTestLib time information is lost

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco started work on  JENKINS-35660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
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-35660) QTestLib time information is lost

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35660  
 
 
  QTestLib time information is lost   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 In Progress 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-35660) QTestLib time information is lost

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-35660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: QTestLib time information is lost   
 

  
 
 
 
 

 
 Code changed in jenkins User: kpop Path: src/main/resources/org/jenkinsci/plugins/xunit/types/qtestlib-to-junit-5.xsl src/test/java/org/jenkinsci/plugins/xunit/types/QTestlibTypeTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/qtestlib/testcase3/input.xml src/test/resources/org/jenkinsci/plugins/xunit/types/qtestlib/testcase3/result.xml http://jenkins-ci.org/commit/xunit-plugin/5d79a70b8c7fa3ea08fd087da056312eb22d258f Log: JENKINS-35660 QTestLib time information is lost Use a converter function in XSLT to convert msec attribute of duration element for QtTest  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-35660) QTestLib time information is lost

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco assigned an issue to Nikolas Falco  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35660  
 
 
  QTestLib time information is lost   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Assignee: 
 Nikolas Falco  
 

  
 
 
 
 

 
 
 

 
 
 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-36182) junit - what is correct for testsuites?

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 testsuites is normally used by junitreport ant task that aggregates multiple testsuite report. Normally the surefire XML report (generated by maven) has the testsuite root element. This is the XSD used by ant task and seems skipped is not valid attribute for testsuites element.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36182  
 
 
  junit - what is correct for testsuites?   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open Closed  
 
 
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

[JIRA] (JENKINS-51095) after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit

2018-05-02 Thread gurce.isikyil...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gurce Isikyildiz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51095  
 
 
  after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2018-05-03-11-06-13-676.png  
 
 
Components: 
 job-import-plugin  
 
 
Created: 
 2018-05-03 01:09  
 
 
Environment: 
 windows  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gurce Isikyildiz  
 

  
 
 
 
 

 
 In relation to JENKINS-23809 and the additional mechanism of specifying a destination folder to import to:   I recently made use of the job-import-plugin. It successfully imported my job to my desired destination folder, which I can attest to by visiting that destination folder manually.   However, just a minor issue that I noticed was that the SUCCESS notification given provided an incorrect url path that didn't take into account the destination path I provided. I'm guessing this was just a small oversight?

[JIRA] (JENKINS-36182) junit - what is correct for testsuites?

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco assigned an issue to Nikolas Falco  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36182  
 
 
  junit - what is correct for testsuites?   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Assignee: 
 Gregory Boissinot Nikolas Falco  
 

  
 
 
 
 

 
 
 

 
 
 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-37611) Add "@Symbol" annotation to xunit and parameters

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add "@Symbol" annotation to xunit and parameters   
 

  
 
 
 
 

 
 Code changed in jenkins User: Nikolas Falco Path: pom.xml src/main/java/org/jenkinsci/plugins/xunit/XUnitBuilder.java src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java src/main/java/org/jenkinsci/plugins/xunit/threshold/FailedThresholdDescriptor.java src/main/java/org/jenkinsci/plugins/xunit/threshold/SkippedThresholdDescriptor.java src/main/java/org/jenkinsci/plugins/xunit/types/AUnitJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/BoostTestJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/CTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/CUnitJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/CheckType.java src/main/java/org/jenkinsci/plugins/xunit/types/CppTestJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/CppUnitJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/CustomType.java src/main/java/org/jenkinsci/plugins/xunit/types/EmbUnitType.java src/main/java/org/jenkinsci/plugins/xunit/types/FPCUnitJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/GTesterJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/GoogleTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/JUnitType.java src/main/java/org/jenkinsci/plugins/xunit/types/MSTestJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/MbUnitType.java src/main/java/org/jenkinsci/plugins/xunit/types/NUnit3TestType.java src/main/java/org/jenkinsci/plugins/xunit/types/NUnitJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/PHPUnitJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/QTestLibInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/QTestLibType.java src/main/java/org/jenkinsci/plugins/xunit/types/UnitTestJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/ValgrindJunitHudsonTestType.java src/main/java/org/jenkinsci/plugins/xunit/types/XUnitDotNetTestType.java src/test/java/org/jenkinsci/plugins/xunit/XUnitWorkflowTest.java http://jenkins-ci.org/commit/xunit-plugin/f8af22b430b869497c792d8edaafd31ae9a84950 Log: JENKINS-37611 Add "@Symbol" annotation to xunit and parameters Add @Symbol annotation to publisher, thresholds and test type to make pipeline readable. Add pipeline unit test that works with Jenkins 1.x Update parent pom to latest 3.9  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37611) Add "@Symbol" annotation to xunit and parameters

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add "@Symbol" annotation to xunit and parameters   
 

  
 
 
 
 

 
 Code changed in jenkins User: Nikolas Falco Path: src/main/java/org/jenkinsci/plugins/xunit/AliasInitializer.java src/main/java/org/jenkinsci/plugins/xunit/XUnitBuilder.java src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java src/main/java/org/jenkinsci/plugins/xunit/XUnitUtil.java src/main/java/org/jenkinsci/plugins/xunit/threshold/FailedThreshold.java src/main/java/org/jenkinsci/plugins/xunit/threshold/SkippedThreshold.java src/main/java/org/jenkinsci/plugins/xunit/threshold/XUnitThreshold.java src/main/java/org/jenkinsci/plugins/xunit/threshold/XUnitThresholdDescriptor.java src/main/resources/org/jenkinsci/plugins/xunit/XUnitBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/xunit/XUnitPublisher/config.jelly src/main/resources/org/jenkinsci/plugins/xunit/threshold/Messages.properties src/main/resources/util/hetero-list-readonly.jelly src/main/resources/util/threshold.jelly src/test/java/org/jenkinsci/plugins/xunit/XUnitSerialisationTest.java src/test/java/org/jenkinsci/plugins/xunit/XUnitWorkflowTest.java src/test/resources/org/jenkinsci/plugins/xunit/XUnitSerialisationTest/builder_1_103/jobs/foo/config.xml src/test/resources/org/jenkinsci/plugins/xunit/XUnitSerialisationTest/publisher_1_103/jobs/foo/config.xml src/test/resources/org/jenkinsci/plugins/xunit/config.xml http://jenkins-ci.org/commit/xunit-plugin/46caa54a002cb93c218c4bb843b8d9ef1e7516a9 Log: JENKINS-37611 Add "@Symbol" annotation to xunit and parameters Move threshold parameters from required to optional. Remove also unreachable checks of % character in case of percent threshold mode. Add form validation for all threshold values. Add unit test to guarantee serialisation works properly with plugin version before 1.103. Manage negative value of time margin and fix NPE when a build step or recorder has no tools defined. Compare: https://github.com/jenkinsci/xunit-plugin/compare/7ea630590a18...46caa54a002c *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-51081) no issues found verdict for any issue

2018-05-02 Thread aquarell...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tatiana Didik commented on  JENKINS-51081  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: no issues found verdict for any issue   
 

  
 
 
 
 

 
 Have you read this article?  https://stackoverflow.com/questions/48707380/sonar-gerrit-plugin-not-reporting-results/48770604#48770604 make sure that sonar qube report contains issues for the files changed in the commit that is being checked if that's not the thing, make sure that you specified subproject paths (or just tick on auto-match option, it should make the magic if it is the case) If all the above doesn't help, feel free to send me your sonarqube report (email can be found on the plugin page and in git repo). But I can't promise that I would be able to take a look anytime soon...  
 

  
 
 
 
 

 
 
 

 
 
 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-37611) Add "@Symbol" annotation to xunit and parameters

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco started work on  JENKINS-37611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
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-51056) xUnit throws NPE when no threshold was specified

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: xUnit throws NPE when no threshold was specified   
 

  
 
 
 
 

 
 Code changed in jenkins User: Nikolas Falco Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitBuilder.java src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java src/test/java/org/jenkinsci/plugins/xunit/XUnitWorkflowTest.java http://jenkins-ci.org/commit/xunit-plugin/875dc671cc49b7981a7b9dfb2a7aa99e5d3504df Log: JENKINS-51056 xUnit throws NPE when no threshold was specified Add check for null in builder and publisher constructors when tools and thresholds are not defined.  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-51056) xUnit throws NPE when no threshold was specified

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51056  
 
 
  xUnit throws NPE when no threshold was specified   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 In Progress 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-48933) Unstoppable Multibranch Pipeline Scan

2018-05-02 Thread kevin.lan...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Lannen commented on  JENKINS-48933  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unstoppable Multibranch Pipeline Scan   
 

  
 
 
 
 

 
 There definitely needs to be some sort of timeout here, this happens less now since we have backed off our polling interval to avoid it (not ideal). We have been able to link all the times that these have occurred to connection issues with our Bitbucket server. A connection error should not require a restart of Jenkins though   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51056) xUnit throws NPE when no threshold was specified

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco edited a comment on  JENKINS-51056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: xUnit throws NPE when no threshold was specified   
 

  
 
 
 
 

 
 In the standard build step thresholds are always defined also if without values. It's true that in the pipeline you can around these kind of constraints. Anyway I test your pipeline and it fails because thresholdMode is required  could , it can  not be defaulted to nul (it is int).  Are you sure the pipeline you post is correct? I will add check for null to avoid NPE.  
 

  
 
 
 
 

 
 
 

 
 
 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-51056) xUnit throws NPE when no threshold was specified

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-51056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: xUnit throws NPE when no threshold was specified   
 

  
 
 
 
 

 
 In the standard build step thresholds are always defined also if without values. It's true that in the pipeline you can around these kind of constraints. Anyway I test your pipeline and it fails because thresholdMode is required could not be defaulted to nul (it is int). I will add check for null to avoid NPE.  
 

  
 
 
 
 

 
 
 

 
 
 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-51056) xUnit throws NPE when no threshold was specified

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco started work on  JENKINS-51056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
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-51056) xUnit throws NPE when no threshold was specified

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51056  
 
 
  xUnit throws NPE when no threshold was specified   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Summary: 
 Jenkins XUnit Plugin version 1.103 fails without xUnit throws NPE when no  threshold  was  specified  
 

  
 
 
 
 

 
 
 

 
 
 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-45817) Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable

2018-05-02 Thread npa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolae Pascu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45817  
 
 
  Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable   
 

  
 
 
 
 

 
Change By: 
 Nicolae Pascu  
 
 
Flagged: 
 Impediment  
 

  
 
 
 
 

 
 
 

 
 
 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-45817) Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable

2018-05-02 Thread npa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolae Pascu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45817  
 
 
  Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable   
 

  
 
 
 
 

 
Change By: 
 Nicolae Pascu  
 
 
Sprint: 
 Blue Ocean 1.6 - beta 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-45817) Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable

2018-05-02 Thread npa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolae Pascu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45817  
 
 
  Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable   
 

  
 
 
 
 

 
Change By: 
 Nicolae Pascu  
 
 
Flagged: 
 Impediment  
 

  
 
 
 
 

 
 
 

 
 
 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-47582) When save the UpdateMode is set to 'full' by default

2018-05-02 Thread da...@gotliebs.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Gotlieb commented on  JENKINS-47582  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When save the UpdateMode is set to 'full' by default
 

  
 
 
 
 

 
 I am experiencing similar issue with the same plugin version  Jenkins core 2.89.2  aws-lambda-plugin 0.5.10 When creating, modifying and saving the projects, I am unable to get anything other than 'Full' option in the Update Mode parameter in 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-51073) local repo does not work maven wrapper

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51073  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: local repo does not work maven wrapper   
 

  
 
 
 
 

 
 Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution.java http://jenkins-ci.org/commit/pipeline-maven-plugin/1b555b519eafd8872034af6f783e2d817dc389dc Log: Merge pull request #147 from pauxus/patch-1 JENKINS-51073 Quick fix for quote problems Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/b44b70a777c1...1b555b519eaf *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-51073) local repo does not work maven wrapper

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51073  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: local repo does not work maven wrapper   
 

  
 
 
 
 

 
 Code changed in jenkins User: Stephan Pauxberger Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution.java http://jenkins-ci.org/commit/pipeline-maven-plugin/5dda60ed3ca6a5c48ecb8875378b2ebb9ee2949f Log: JENKINS-51073 Quick fix for quote problems by surrounding the whole -D statement with quotes (`"-Dmaven.repo.local=/bla/blub"` instead of `-Dmaven.repo.local="/bla/blub"`), the local repo works with maven wrapper as well as with standalone maven.  
 

  
 
 
 
 

 
 
 

 
 
 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-51056) Jenkins XUnit Plugin version 1.103 fails without threshold specified

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco assigned an issue to Nikolas Falco  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51056  
 
 
  Jenkins XUnit Plugin version 1.103 fails without threshold specified   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Assignee: 
 Andrew Bayer Nikolas Falco  
 

  
 
 
 
 

 
 
 

 
 
 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-9104  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/ProcessTree.java test/src/test/java/hudson/util/ProcessTreeKillerTest.java http://jenkins-ci.org/commit/jenkins/3465da4764c322baf4fb5b90651ef6b9bcd409fb Log: Merge pull request #3419 from dwnusbaum/JENKINS-9104-test-fix Fix test failure by cleaning up static state after tests Compare: https://github.com/jenkinsci/jenkins/compare/ddbc4bbce7d3...3465da4764c3 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-44231) Safely pass args to sh step

2018-05-02 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-44231  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Safely pass args to sh step   
 

  
 
 
 
 

 
 From a dev list conversation: this aspect of some Bourne shells means that an implementation which ultimately runs a shell, as opposed to Runtime.exec or the like, may omit certain environment variables.  
 

  
 
 
 
 

 
 
 

 
 
 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-51008  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Complete the PCT flow started in JENKINS-50540 for git plugin   
 

  
 
 
 
 

 
 Raul Arabaolaza Isa Vilacides I have created a PR for JENKINS-51093 with basic Incrementals support. Please let me know whether it's enough for you. Or do you need JENKINS-51094 (automatic picking of latest releases)?  
 

  
 
 
 
 

 
 
 

 
 
 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-51093) Custom WAR Packager - Support building with versions from Incrementals repo

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-51093  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51093  
 
 
  Custom WAR Packager - Support building with versions from Incrementals repo   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51093) Custom WAR Packager - Support building with versions from Incrementals repo

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-51093  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51094) Custom WAR Packager - Support building with LATEST versions from Incrementals repo

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51094  
 
 
  Custom WAR Packager - Support building with LATEST versions from Incrementals repo   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Same as JENKINS-51093, but build with Latest Incrementals  repo  version so that we can get rolling build  
 

  
 
 
 
 

 
 
 

 
 
 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-51094) Custom WAR Packager - Support building with LATEST versions from Incrementals repo

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51094  
 
 
  Custom WAR Packager - Support building with LATEST versions from Incrementals repo   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Same as JENKINS-51093, but build with Latest Incrementals repo  
 

  
 
 
 
 

 
 
 

 
 
 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-51093) Custom WAR Packager - Support building with versions from Incrementals repo

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51093  
 
 
  Custom WAR Packager - Support building with versions from Incrementals repo   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 custom-war-packager  
 
 
Created: 
 2018-05-02 22:11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you

[JIRA] (JENKINS-51094) Custom WAR Packager - Support building with LATEST versions from Incrementals repo

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51094  
 
 
  Custom WAR Packager - Support building with LATEST versions from Incrementals repo   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 custom-war-packager  
 
 
Created: 
 2018-05-02 22:11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message

[JIRA] (JENKINS-50968) DATA dissapear from Input with several textfields

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50968  
 
 
  DATA dissapear from Input with several textfields
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 pipeline-input-step-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-50199) Failed pipeline jobs stuck running after incorrect resume

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed pipeline jobs stuck running after incorrect resume   
 

  
 
 
 
 

 
 Mike Kozell That is... the exact opposite of what I would expect. Not sure what's going on there, since the ci.jenkins.io builder does both Windows and Linux builds and they succeed. Weird.  
 

  
 
 
 
 

 
 
 

 
 
 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-51039) http proxy are ignored by git operations for loading pipeline libraries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51039  
 
 
  http proxy are ignored by git operations for loading pipeline libraries   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 workflow-cps-global-lib-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-51002) Quiet period for parameterized pipeline job not working fully

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51002  
 
 
  Quiet period for parameterized pipeline job not working fully   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 workflow-job-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-51083) List does not contain added objects

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51083  
 
 
  List does not contain added objects   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 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-51083) List does not contain added objects

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-51083  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: List does not contain added objects   
 

  
 
 
 
 

 
 I'll check when I get a chance to see why += isn't working, but, fwiw, someList << someObject or someList.add(someObject) will work fine.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-48933  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unstoppable Multibranch Pipeline Scan   
 

  
 
 
 
 

 
 Today I learned that multibranch indexing is The Juggernaut and there is no stopping it.  rsandell Could it be that we need to include SCM timeouts or better exception handling somewhere?  
 

  
 
 
 
 

 
 
 

 
 
 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-51083) += doesn't append to list

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51083  
 
 
  += doesn't append to list   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Summary: 
 List does not contain added objects += doesn't append to list  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51083) List does not contain added objects

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51083  
 
 
  List does not contain added objects   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 workflow-cps-plugin  
 
 
Component/s: 
 groovy-plugin  
 
 
Component/s: 
 pipeline  
 
 
Assignee: 
 vjuranek  
 

  
 
 
 
 

 
 
 

 
 
 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-51091) Make test results available on currentBuild

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-51091  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make test results available on currentBuild   
 

  
 
 
 
 

 
 It'd be at least a little complicated - the workflow-support plugin would need to depend on the junit plugin, etc. For what it's worth, the junit step does return a TestResultSummary.  
 

  
 
 
 
 

 
 
 

 
 
 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-43413) RejectedExecutionException at SingleLaneExecutorService when loading CpsFlowExecution after restart

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Oleg Nenashev This should be resolved by the workflow-cps 2.50 and workflow-job 2.21 releases  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-43413  
 
 
  RejectedExecutionException at SingleLaneExecutorService when loading CpsFlowExecution after restart   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

[JIRA] (JENKINS-43413) RejectedExecutionException at SingleLaneExecutorService when loading CpsFlowExecution after restart

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43413  
 
 
  RejectedExecutionException at SingleLaneExecutorService when loading CpsFlowExecution after restart   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Labels: 
 maybe-fixed-by-durability-megafix regression  
 

  
 
 
 
 

 
 
 

 
 
 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-50429) Shell command are really slower than before

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50429  
 
 
  Shell command are really slower than before   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Component/s: 
 kubernetes-plugin  
 
 
Component/s: 
 workflow-durable-task-step-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-50429) Shell command are really slower than before

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50429  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shell command are really slower than before   
 

  
 
 
 
 

 
 That sounds like an issue with the Kubernetes plugin then, so I'm going to reassign this.  My suspicion is that this has to do with how logging is handled in some fashion.   
 

  
 
 
 
 

 
 
 

 
 
 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-37589) Replay link does not show up if Jenkinsfile had a syntax error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-37589  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Replay link does not show up if Jenkinsfile had a syntax error   
 

  
 
 
 
 

 
 R. Tyler Croy Christopher Orr Can you check if the error occurs with workflow-cps 2.50 and workflow-cps 2.21? I just released a set of fixes that I think address this.   
 

  
 
 
 
 

 
 
 

 
 
 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-48491) NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm going to assume this was fixed since R. Tyler Croy never replied back and we've addressed this with code changes.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48491  
 
 
  NPE in CpsThreadGroup.run & IOOBE in CpsThreadGroup.readResolve   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

[JIRA] (JENKINS-37589) Replay link does not show up if Jenkinsfile had a syntax error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37589  
 
 
  Replay link does not show up if Jenkinsfile had a syntax error   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Labels: 
 community-bee  maybe-fixed-by-durability-megafix  
 

  
 
 
 
 

 
 
 

 
 
 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-50199) Failed pipeline jobs stuck running after incorrect resume

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-50199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixes released with workflow-cps 2.50 and workflow-job 2.21 – would really appreciate if you guys could install the latest and confirm the issue is resolved. CCMike Kozell Matt Gaspar  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50199  
 
 
  Failed pipeline jobs stuck running after incorrect resume   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 In Review 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

[JIRA] (JENKINS-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort started work on  JENKINS-49686  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 Reopened 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-49686) NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Should be resolved with release of workflow-cps 2.50 and workflow-job 2.21 CC bentoi  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49686  
 
 
  NPE in CPS VM thread at WorkflowRun$GraphL.onNewHead   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Status: 
 In Progress 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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more

[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API

2018-05-02 Thread ol...@apache.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated  JENKINS-48357  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48357  
 
 
  Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-48357  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API   
 

  
 
 
 
 

 
 Code changed in jenkins User: Olivier Lamy Path: README.md pom.xml src/main/java/com/atlassian/httpclient/apache/httpcomponents/ApacheAsyncHttpClient.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/CommonBuilder.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/DefaultHttpClientFactory.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/DefaultMessage.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/DefaultRequest.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/DefaultResponse.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/EntityByteArrayInputStream.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/Headers.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/MavenUtils.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/PromiseHttpAsyncClient.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/RedirectStrategy.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/RequestEntityEffect.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/SettableFuturePromiseHttpPromiseAsyncClient.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProvidedProxyConfig.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProxyConfig.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProxyConfigFactory.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/ProxyCredentialsProvider.java src/main/java/com/atlassian/httpclient/apache/httpcomponents/proxy/SystemPropertiesProxyConfig.java src/main/java/com/atlassian/httpclient/base/event/AbstractHttpRequestEvent.java src/main/java/com/atlassian/httpclient/base/event/HttpRequestCompletedEvent.java src/main/java/com/atlassian/httpclient/base/event/HttpRequestFailedEvent.java src/main/resources/atlassian-httpclient-plugin-0.23.0.pom http://jenkins-ci.org/commit/jira-plugin/abd092848b1e617ceb31b16de07b1445d34c4d03 Log: JENKINS-48357 get rid of atlassian http client (#145) JENKINS-48357 
 
import sources from Atlassian Async HttpClient so we can use whatever we want as apache httpclient version 
 Signed-off-by: olivier lamy  
 
remove non used imported classes 
 Signed-off-by: olivier lamy  
 
get rid of this class 
 Signed-off-by: olivier lamy  
 
modern  
 Signed-off-by: olivier lamy  
 
add note on Atlassian sources import 
 Signed-off-by: olivier lamy

[JIRA] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated  JENKINS-50888  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Tom Ghyselinck This should be fixed by release 2.21 of workflow-job plugin now.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50888  
 
 
  NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
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

[JIRA] (JENKINS-51079) Custom WAR Packager should support BOM as input

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-51079  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51079) Custom WAR Packager should support BOM as input

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-51079  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51079  
 
 
  Custom WAR Packager should support BOM as input   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51092) Two Factor Auth in Github Breaks Authentication for Github Organization

2018-05-02 Thread gray...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Gray created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51092  
 
 
  Two Factor Auth in Github Breaks Authentication for Github Organization   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jenkins.jpg  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2018-05-02 20:36  
 
 
Environment: 
 Jenkins ver. 2.107.2  GitHub Branch Source 2.3.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alex Gray  
 

  
 
 
 
 

 
 We are enforcing Two Factor Authentication on all users in our GitHub Organization. When we enabled it, all of our Jenkins jobs were fine EXCEPT for our "Github Organization" jobs. It seems this plugin only support username/password creds, not id_rsa or access_tokens, which work fine with Two Factor Authentication. If you use username/access_token credentials, you get access denied: 

 


Started by user 
[Alex Gray|https://jenkins.clearcare.it/user/alex.gray]
java.io.FileNotFoundException: 
[https://api.github.com/]
	at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243)
	at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
	at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)
	at org.kohsuke.github.Requester.parse(Requester.java:612)
	at org.kohsuke.github.Requester.parse(Requester.java:594)
	at org.kohsuke.github.Requester._to(Requester.java:272)
Caused:

[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed pipeline jobs stuck running after incorrect resume   
 

  
 
 
 
 

 
 Mike Kozell Are you building on Windows, by any chance? I'd try to set the platform encoding to UTF-8 – that error is safe to ignore though. You can comment out the whole test by adding "@Ignore" to src/test/java/org/jenkinsci/plugins/workflow/job/CLITest.java on line 85.  
 

  
 
 
 
 

 
 
 

 
 
 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-51091) Make test results available on currentBuild

2018-05-02 Thread zeratul...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean MacKay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51091  
 
 
  Make test results available on currentBuild   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-05-02 20:05  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sean MacKay  
 

  
 
 
 
 

 
 Currently, as described here, the only way to get the archived test results in a Pipeline job is through the currentBuild.rawBuild object and pulling an AbstractTestResultAction out of it to read test results. This involved whitelisting several external methods.  This is a lot of work to try and say, generate a slack message saying "Build BUILD failed, X/Y tests failed". How hard would it be to define a property on the currentBuild Global Variable live this: currentBuild.testResult.failCount ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-51090) Emails no longer sent to developers on build failure

2018-05-02 Thread michaeldkfow...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51090  
 
 
  Emails no longer sent to developers on build failure   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 After updating both the git and email-ext plugins, a project that had been working for years no longer sends emails to developers on a build failure.{code:java}Email was triggered for: Failure - AnySending email for trigger: Failure - AnyAn attempt to send an e-mail to empty list of recipients, ignored.{code}A simplified configuration to recreate the issue is shown below:!image-2018-05-02-15-28-53-400.png!!image-2018-05-02-15-29-47-973.png! !image-2018-05-02-15-34-10-012.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51090) Emails no longer sent to developers on build failure

2018-05-02 Thread michaeldkfow...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51090  
 
 
  Emails no longer sent to developers on build failure   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Attachment: 
 image-2018-05-02-15-34-10-012.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-50953) Tool to offer incremental updates

2018-05-02 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50953  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tool to offer incremental updates   
 

  
 
 
 
 

 
 Starting work on such a tool. The main work should be encapsulated in a reusable function which would be callable from several front-ends, one of which would offer to update deps in a POM, another for essentials.yaml.  
 

  
 
 
 
 

 
 
 

 
 
 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-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs

2018-05-02 Thread mac...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 macetw commented on  JENKINS-20706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make Cobertura plug-in support multi-configuration (matrix) jobs   
 

  
 
 
 
 

 
 Marc Abramowitz  James Talton This issue is "in progress," but without activity in 3.5 years. Shall we call this "won't fix" or is there a different approach to refer to?  
 

  
 
 
 
 

 
 
 

 
 
 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-51090) Emails no longer sent to developers on build failure

2018-05-02 Thread michaeldkfow...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51090  
 
 
  Emails no longer sent to developers on build failure   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David van Laatum  
 
 
Attachments: 
 image-2018-05-02-15-28-53-400.png, image-2018-05-02-15-29-47-973.png  
 
 
Components: 
 email-ext-plugin, git-plugin  
 
 
Created: 
 2018-05-02 19:30  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 After updating both the git and email-ext plugins, a project that had been working for years no longer sends emails to developers on a build failure. 

 

Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
An attempt to send an e-mail to empty list of recipients, ignored.
 

 A simplified configuration to recreate the issue is shown below:

[JIRA] (JENKINS-51089) Allow issue assignment

2018-05-02 Thread m...@mytran.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 My Tran created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51089  
 
 
  Allow issue assignment   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Daniel Lo Nigro  
 
 
Components: 
 github-issues-plugin  
 
 
Created: 
 2018-05-02 18:56  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 My Tran  
 

  
 
 
 
 

 
 I would be nice to be able to assign issues. Looked around but didn't see it as an option anywhere in the plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-51088) Provisioning fails on API errors for image lookups

2018-05-02 Thread ty...@monkeypox.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51088  
 
 
  Provisioning fails on API errors for image lookups   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2018-05-02 18:41  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 We have now seen this multiple times break our ability to provision new images on ci.jenkins.io In the VM Template the "Provisioning Failure Reason" field has: 

 

Failed to validate the provided image reference: java.net.SocketTimeoutException: timeout
 

 This is a very problematic issue as we cannot tell that Azure VM provisioning has failed in any automated way, they just stop provisioning  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-50953) Tool to offer incremental updates

2018-05-02 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-50953  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
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-51087) Add monitoring of the SQL calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51087  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add monitoring of the SQL calls   
 

  
 
 
 
 

 
 Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/DependencyGraphTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/0cfa2fe3cef248063b9204ea0d8eba21d98c3756 Log: JENKINS-51087 fix "unit tests". As they take more than 30 mins to run, I sometimes skip them and sometimes I'm wrong  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-51086) Replace static lookups of dependencies by @Inject

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51086  
 
 
  Replace static lookups of dependencies by @Inject   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
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-51086) Replace static lookups of dependencies by @Inject

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc commented on  JENKINS-51086  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Replace static lookups of dependencies by @Inject   
 

  
 
 
 
 

 
 planned for 3.5.6  
 

  
 
 
 
 

 
 
 

 
 
 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-51087) Add monitoring of the SQL calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 planned for 3.5.6  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51087  
 
 
  Add monitoring of the SQL calls   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
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-51086) Replace static lookups of dependencies by @Inject

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51086  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Replace static lookups of dependencies by @Inject   
 

  
 
 
 
 

 
 Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginMonitoringDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncItemListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncRunListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DownstreamPipelineTriggerRunListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/DependencyGraphTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/619187831f7b6de1793fee8aa57a4a56247a5bef Log: Merge pull request #148 from jenkinsci/JENKINS-51086 JENKINS-51086 & JENKINS-51087 Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/5f87e0698573...619187831f7b *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-51087) Add monitoring of the SQL calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51087  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add monitoring of the SQL calls   
 

  
 
 
 
 

 
 Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginMonitoringDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncItemListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncRunListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DownstreamPipelineTriggerRunListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/DependencyGraphTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/619187831f7b6de1793fee8aa57a4a56247a5bef Log: Merge pull request #148 from jenkinsci/JENKINS-51086 JENKINS-51086 & JENKINS-51087 Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/5f87e0698573...619187831f7b *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort edited a comment on  JENKINS-50199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed pipeline jobs stuck running after incorrect resume   
 

  
 
 
 
 

 
 [~mkozell] Also I think we're clear for release of this now -- but I'm aiming to  day  delay  until at least tonight EST if that'll permit enough time to land it on some real-world Jenkins masters as a sanity check.    
 

  
 
 
 
 

 
 
 

 
 
 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-50199) Failed pipeline jobs stuck running after incorrect resume

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed pipeline jobs stuck running after incorrect resume   
 

  
 
 
 
 

 
 Mike Kozell Also I think we're clear for release of this now – but I'm aiming to day until at least tonight EST if that'll permit enough time to land it on some real-world Jenkins masters as a sanity check.   
 

  
 
 
 
 

 
 
 

 
 
 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-48656) Mercurial triggers broken by duplicate checkout in Multibranch pipeline

2018-05-02 Thread bren...@brendoncolby.com (JIRA)

Title: Message Title

Brendon Colby edited a comment on JENKINS-48656

Re: Mercurial triggers broken by duplicate checkout in Multibranch pipeline

I decided to troubleshoot this more. I can't for the life of me get a multibranch pipeline to trigger. In the jenkins.log, it says: {code:java}INFO: Triggering BitBucket job default{code} I see in the Bitbucket Hook Log that it runs "/usr/bin/hg pull" and that the new changesets DO get pulled in, but for some reason it always says "No changes" and doesn't trigger the pipeline to run no matter what I do. So for whatever reason, multibranch pipelines with Bitbucket and Mercurial seem to be broken.We don't use branches in these repos so I created a regular pipeline project (not sure why I didn't do this in the first place). I CAN get these to run on a push, but it creates duplicate changelog entries. In the Bitbucket Hook Log, I see a series of Mercurial commands run twice. The pipeline is called "test-staging" so I see "hg pull" etc. run for "test-staging@script" and then again for "test-staging". I assume the first one is to pull in the Jenkinsfile and the second is the default SCM checkout.If I add this to the Jenkinsfile:{code:java}options { skipDefaultCheckout()}{code}Then I see exactly one changelog entry per commit. Of course, the local repo is never updated, so I added a "Checkout" stage that runs "hg update" (because the changesets were already pulled down by the pipeline itself ). This seems to work well for us.Of course, this won't work on the initial pipeline setup because the repo has to be cloned first, but in that case all you need to do is leave out skipDefaultCheckout() on the first run then add it back in after that.

Add Comment

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

[JIRA] (JENKINS-51086) Replace static lookups of dependencies by @Inject

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51086  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Replace static lookups of dependencies by @Inject   
 

  
 
 
 
 

 
 Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncItemListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DatabaseSyncRunListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DownstreamPipelineTriggerRunListener.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/DependencyGraphTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/35e3d0361e758fed422a8a87200acaf570481b9b Log: JENKINS-51086 Replace static lookups of dependencies by @Inject  
 

  
 
 
 
 

 
 
 

 
 
 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-51087) Add monitoring of the SQL calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51087  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add monitoring of the SQL calls   
 

  
 
 
 
 

 
 Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/GlobalPipelineMavenConfig.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginMonitoringDao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/2c249e2715a6fd813e12311498e44f742e9fc8a0 Log: JENKINS-51087 Add monitoring of the SQL calls Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/35e3d0361e75^...2c249e2715a6 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 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-48656) Mercurial triggers broken by duplicate checkout in Multibranch pipeline

2018-05-02 Thread bren...@brendoncolby.com (JIRA)

Title: Message Title

Brendon Colby commented on JENKINS-48656

Re: Mercurial triggers broken by duplicate checkout in Multibranch pipeline

I decided to troubleshoot this more. I can't for the life of me get a multibranch pipeline to trigger. In the jenkins.log, it says:

INFO: Triggering BitBucket job default

I see in the Bitbucket Hook Log that it runs "/usr/bin/hg pull" and that the new changesets DO get pulled in, but for some reason it always says "No changes" and doesn't trigger the pipeline to run no matter what I do. So for whatever reason, multibranch pipelines with Bitbucket and Mercurial seem to be broken. We don't use branches in these repos so I created a regular pipeline project (not sure why I didn't do this in the first place). I CAN get these to run on a push, but it creates duplicate changelog entries. In the Bitbucket Hook Log, I see a series of Mercurial commands run twice. The pipeline is called "test-staging" so I see "hg pull" etc. run for "test-staging@script" and then again for "test-staging". I assume the first one is to pull in the Jenkinsfile and the second is the default SCM checkout. If I add this to the Jenkinsfile:

options {
skipDefaultCheckout()
}

Then I see exactly one changelog entry per commit. Of course, the local repo is never updated, so I added a "Checkout" stage that runs "hg update" (because the changesets were already pulled down). This seems to work well for us. Of course, this won't work on the initial pipeline setup because the repo has to be cloned first, but in that case all you need to do is leave out skipDefaultCheckout() on the first run then add it back in after that.

Add Comment

[JIRA] (JENKINS-51087) Add monitoring of the SQL calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51087  
 
 
  Add monitoring of the SQL calls   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Cyrille Le Clerc  
 
 
Components: 
 pipeline-maven-plugin  
 
 
Created: 
 2018-05-02 17:18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Cyrille Le Clerc  
 

  
 
 
 
 

 
 Add monitoring of the SQL calls. Will be important when we connect to an external database instead of using the in-process embedded H2 DB.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-51086) Replace static lookups of dependencies by @Inject

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51086  
 
 
  Replace static lookups of dependencies by @Inject   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Cyrille Le Clerc  
 
 
Components: 
 pipeline-maven-plugin  
 
 
Created: 
 2018-05-02 17:14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Cyrille Le Clerc  
 

  
 
 
 
 

 
 Replace static lookups of dependencies by @Inject  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed pipeline jobs stuck running after incorrect resume   
 

  
 
 
 
 

 
 Mike Kozell Sure! The code is here, modulo an extra line or two of logging and a couple of small tweaks since then (nothing substantial):  https://github.com/jenkinsci/workflow-job-plugin/pull/96 https://github.com/jenkinsci/workflow-cps-plugin/pull/223 Feel free to add code review too if you like, though it's just gotten a final pass by the other two people that do a lot of Pipeline core development.   
 

  
 
 
 
 

 
 
 

 
 
 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-51024) Update hashicorp-vault plugin version to pick up NPE fixes.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Tierno closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Just published release 2.1.1 which picks up these changes  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51024  
 
 
  Update hashicorp-vault plugin version to pick up NPE fixes.   
 

  
 
 
 
 

 
Change By: 
 Peter Tierno  
 
 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit

[JIRA] (JENKINS-46794) Dynamic secrets should be revoked after build wrapper completes