date:20190612

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goldy Liang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57997  
 
 
  Performance plugin parses the same file multiple times   
 

  
 
 
 
 

 
Change By: 
 Goldy Liang  
 

  
 
 
 
 

 
 In some cases, the Performance plugin parses the same CSV files of the same build multiple times, even if has been already parsed. This causes the UI halting and not able to show any data, until all of them get parsed multiple times, which takes extremely long time.The way I reproduce it is to run the same build again and again without delay (performance reporting of large csv files, but without testing), like below pipeline snippet:{quote}{{//A CSV file named report.csv is firstly created with large dataset}}{{perfReport report.csv}}{quote} When the multiple builds are being run, keep the job's UI page open in one browser. After several builds, the job 's  UI  page  is halting and there is no performance report showed, unless after an extremely long time.From the Jenkins log, I can see the same report gets parsed again and again.For example, after building #67, #68 & #69, below is the Jenkins log:{quote}Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/69/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/69/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. {quote}Two work-arounds: # Make sure the Jenkins job UI page is not opened in any browsers when multiple builds are being run without delay. It seems like the parsing is triggered from UI request, and if the job UI page is opened, and the build only contains one report each, it will

[JIRA] (JENKINS-57997) Performance plugin parses the same file multiple times

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goldy Liang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57997  
 
 
  Performance plugin parses the same file multiple times   
 

  
 
 
 
 

 
Change By: 
 Goldy Liang  
 

  
 
 
 
 

 
 In some cases, the Performance plugin parses the same CSV files of the same build multiple times, even if has been already parsed. This causes the UI halting and not able to show any data, until all of them get parsed multiple times, which takes extremely long time.The way I reproduce it is to run the same build again and again without delay (performance reporting of large csv files, but without testing), like below pipeline snippet:{quote}{{//A CSV file named report.csv is firstly created with large dataset}}{{perfReport report.csv}}{quote}After several builds, the job UI is halting and there is no performance report showed, unless after an extremely long time.From the Jenkins log, I can see the same report gets parsed again and again.For example, after building #67, #68 & #69, below is the Jenkins log:{quote}Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/69/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/69/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. {quote} A Two  work- around I found arounds: # Make sure the Jenkins job UI page  is  not opened in any browsers when multiple builds are being run without delay. It seems like the parsing is triggered from UI request, and if the job UI page is opened, and the build only contains one report each, it will request the performance report and trigger Jenkins  to  restart  parse

[JIRA] (JENKINS-57997) Performance plugin parses the same file multiple times

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goldy Liang commented on  JENKINS-57997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin parses the same file multiple times   
 

  
 
 
 
 

 
 In AbstractParser.parse, it tries to load the report from file/cache, and if not parsed yet, run the parser. I think this can be synchronized by file name, so that if thread A is already trying to parse, the other thread B won't try doing that again, but just wait for the thread A finishes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57997) Performance plugin parses the same file multiple times

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goldy Liang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57997  
 
 
  Performance plugin parses the same file multiple times   
 

  
 
 
 
 

 
Change By: 
 Goldy Liang  
 

  
 
 
 
 

 
 In some cases, the Performance plugin parses the same CSV files of the same build multiple times, even if has been already parsed. This causes the UI halting and not able to show any data, until all of them get parsed multiple times, which takes extremely long time.The way I reproduce it is to run the same build again and again without delay (performance reporting of large csv files, but without testing), like below pipeline snippet:{quote}{{//A CSV file named report.csv is firstly created with large dataset}}{{perfReport report.csv}}{quote}After several builds, the job UI is halting and there is no performance report showed, unless after an extremely long time.From the Jenkins log, I can see the same report gets parsed again and again.For example, after building #67, #68 & #69, below is the Jenkins log:{quote}Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/69/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/69/performance-reports/JMeterCSV/full_report' with filterRegex 'null'.Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. {quote}   A work-around I found is to restart the Jenkins after multiple builds have been performed, then run only one more new build. After that, the plugin parses all builds which have not been parsed yet only once, but not multiple times.

[JIRA] (JENKINS-57997) Performance plugin parses the same file multiple times

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goldy Liang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57997  
 
 
  Performance plugin parses the same file multiple times   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrey Pokhilko  
 
 
Components: 
 performance-plugin  
 
 
Created: 
 2019-06-13 03:22  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Goldy Liang  
 

  
 
 
 
 

 
 In some cases, the Performance plugin parses the same CSV files of the same build multiple times, even if has been already parsed. This causes the UI halting and not able to show any data, until all of them get parsed multiple times, which takes extremely long time. The way I reproduce it is to run the same build again and again without delay (performance reporting of large csv files, but without testing), like below pipeline snippet: 

//A CSV file named report.csv is firstly created with large dataset 
perfReport report.csv
 After several builds, the job UI is halting and there is no performance report showed, unless after an extremely long time. From the Jenkins log, I can see the same report gets parsed again and again. For example, after building #67, #68 & #69, below is the Jenkins log: 

Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/69/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/67/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing report file '/local/jenkins/jobs/loadtest/builds/68/performance-reports/JMeterCSV/full_report' with filterRegex 'null'. Performance: Parsing

[JIRA] (JENKINS-57996) Parameter JIRA_ISSUES cannot get all jira-ids if commit message is too long.

2019-06-12 Thread syb.0...@aliyun.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Helen Song updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57996  
 
 
  Parameter JIRA_ISSUES cannot get all jira-ids if commit message is too long.   
 

  
 
 
 
 

 
Change By: 
 Helen Song  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57996) Parameter JIRA_ISSUES cannot get all jira-ids if commit message is too long.

2019-06-12 Thread syb.0...@aliyun.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Helen Song created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57996  
 
 
  Parameter JIRA_ISSUES cannot get all jira-ids if commit message is too long.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jira-plugin  
 
 
Created: 
 2019-06-13 03:13  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Helen Song  
 

  
 
 
 
 

 
 Parameter JIRA_ISSUES cannot get all jira-ids if commit message is too long. it will fail to get Jira ids if the Jira id behind 50 (or 70?) characters.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira

[JIRA] (JENKINS-49022) Performance plugin. Allow choosing percentiles to track

Title: Message Title


 
 
 
 

 
 
 

 
   
 Goldy Liang commented on  JENKINS-49022  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance plugin. Allow choosing percentiles to track   
 

  
 
 
 
 

 
 Hi Senthil, Is there a plan to show trend graphs with custom percentile values? I am really looking forward to that. And further more, it looks to me the graph of response time only shows the average value, even I choose the graphType as 'PRT'. Below is my code snippet, maybe there is something missing in it? perfReport filterRegex: null, graphType: 'PRT', percentiles: '0,90,95,99,100', sourceDataFiles: 'SLA' I don't see anywhere using my percentile values, except in the table of "last report". Goldy    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57970) Add checks for available updates and known security issues in the installation script

2019-06-12 Thread natasha.st...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa commented on  JENKINS-57970  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add checks for available updates and known security issues in the installation script   
 

  
 
 
 
 

 
 Nevermind, I think I found it. It looks like under "signature", there's an array of warnings.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57970) Add checks for available updates and known security issues in the installation script

2019-06-12 Thread natasha.st...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa commented on  JENKINS-57970  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add checks for available updates and known security issues in the installation script   
 

  
 
 
 
 

 
 How are known security issues flagged in the update center .json file?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-28734) Maintain Active Choices selections between filter applications

2019-06-12 Thread brunodepau...@yahoo.com.br (JIRA)

Title: Message Title

Bruno P. Kinoshita commented on JENKINS-28734

Re: Maintain Active Choices selections between filter applications

We must also consider the two closed duplicated tickets. In one of them (51054) it appears that a simpler approach would be enough to fix the use case of the user. One where we do not clear the selections. However, not sure what happens if we have items A, B[selected], C[seleted] in the first state. Then the user changes another parameter and then the items displayed are now only A, C[selected]... not sure if the user would still want B[selected] if B is displayed again, or if it would be in a reset/clear state. If the latter, that's much easier. Also, we could suggest the simplest solution (not clearing selections), instead of maintaining the full state of selections between states (much harder, with more risk of bugs). For later, as this will probably need at least a minor version release. Next release will be probably patch/bugs.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

[JIRA] (JENKINS-51054) Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter

2019-06-12 Thread brunodepau...@yahoo.com.br (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated  JENKINS-51054  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51054  
 
 
  Enable Filter is only passing the filtered value but not the all selected item in Active Choice Reactive Parameter   
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

2019-06-12 Thread brunodepau...@yahoo.com.br (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruno P. Kinoshita updated  JENKINS-50837  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50837  
 
 
  [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3
 

  
 
 
 
 

 
Change By: 
 Bruno P. Kinoshita  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-50837) [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

2019-06-12 Thread brunodepau...@yahoo.com.br (JIRA)

Title: Message Title

Bruno P. Kinoshita commented on JENKINS-50837

Re: [ActiveChoicePlugin] FIlter is not working properly with the ActiveChoice plugin version 1.5.3

No updates from me. I'm currently overseas for a conference, back in July, will have some time with family before returning to $work. Then once I have time to work on Open Source will triage issues here to see what can be fixed and included in the next release. Closing this and the other duplicate issues, as there is an older issue for this already. Multiple issues make it harder to triage things and can be confusing to users too. This is not too complicated to fix, but requires a lot of patience and time, as it would require creating a state layer in _javascript_, with some sort of Stack/State, and link it with the choices selected... this can lead to multiple issues with different browsers, or different parameter types. Pull requests welcome! Always happy to review contributions by others and include in a future release. If there is urgency in this issue, please consider also hiring professional services, as there is a number of companies that offer Jenkins development (e.g. CloudBees, Praqma, most IT shops, and several Jenkins plugin maintainers), as most of the work here is maintained as Open Source volunteer work.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

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

[JIRA] (JENKINS-56168) Extrem long loading times, when opening Blue Ocean dashboard, activity or branches view the first time

2019-06-12 Thread gim...@ferrari-electronic.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Gimpel commented on  JENKINS-56168  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extrem long loading times, when opening Blue Ocean dashboard, activity or branches view the first time   
 

  
 
 
 
 

 
 Any news regarding the issue? The issue description shows clearly the root cause of the problem and nobody cares about it?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57392) AWS API timeout

2019-06-12 Thread seanzo...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Zou commented on  JENKINS-57392  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS API timeout   
 

  
 
 
 
 

 
 I attempted, but It is going to be a huge change to pass the timeout in the config to everywhere in the code. The createClientConfiguration method is static, so I can't access EC2Cloud member methods directly, have to pass in as a parameter. Any suggestions?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57995) Zombie pods are created when resources are not sufficient for pods and idleMinutes is set to a non-zero value

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishi Thakkar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57995  
 
 
  Zombie pods are created when resources are not sufficient for pods and idleMinutes is set to a non-zero value
 

  
 
 
 
 

 
Change By: 
 Rishi Thakkar  
 
 
Summary: 
 Zombie pods are created when resources are not sufficient for pods and  idleTimeout  idleMinutes  is set to a non-zero value   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57995) Zombie pods are created when resources are not sufficient for pods and idleTimeout is set to a non-zero value

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishi Thakkar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57995  
 
 
  Zombie pods are created when resources are not sufficient for pods and idleTimeout is set to a non-zero value
 

  
 
 
 
 

 
Change By: 
 Rishi Thakkar  
 

  
 
 
 
 

 
 Zombie pods are created when resources are not sufficient for secluding pods and  idleTimeout  idleMinutes  is set to a non-zero value.This causes multiple pods to be launched from one pod template where one of the pods is in a zombie state and one is active. As the zombie pods accumulate, there are no resources left over to schedule actual pods.WAR: set up a cron job to delete pods in error state or set idleMinutes to 0.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57995) Zombie pods are created when resources are not sufficient for secluding pods and idleTimeout is set to a non-zero value

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishi Thakkar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57995  
 
 
  Zombie pods are created when resources are not sufficient for secluding pods and idleTimeout is set to a non-zero value
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2019-06-12 22:18  
 
 
Environment: 
 Jenkins ver. 2.180  Kubernetes-plugin ver 1.16.0  Kubernetes ver 1.12.7   
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Rishi Thakkar  
 

  
 
 
 
 

 
 Zombie pods are created when resources are not sufficient for secluding pods and idleTimeout is set to a non-zero value. This causes multiple pods to be launched from one pod template where one of the pods is in a zombie state and one is active. As the zombie pods accumulate, there are no resources left over to schedule actual pods. WAR: set up a cron job to delete pods in error state.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57995) Zombie pods are created when resources are not sufficient for pods and idleTimeout is set to a non-zero value

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishi Thakkar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57995  
 
 
  Zombie pods are created when resources are not sufficient for pods and idleTimeout is set to a non-zero value
 

  
 
 
 
 

 
Change By: 
 Rishi Thakkar  
 

  
 
 
 
 

 
 Zombie pods are created when resources are not sufficient for secluding pods and idleTimeout is set to a non-zero value.This causes multiple pods to be launched from one pod template where one of the pods is in a zombie state and one is active. As the zombie pods accumulate, there are no resources left over to schedule actual pods.WAR: set up a cron job to delete pods in error state  or set idleMinutes to 0 .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57995) Zombie pods are created when resources are not sufficient for pods and idleTimeout is set to a non-zero value

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishi Thakkar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57995  
 
 
  Zombie pods are created when resources are not sufficient for pods and idleTimeout is set to a non-zero value
 

  
 
 
 
 

 
Change By: 
 Rishi Thakkar  
 
 
Summary: 
 Zombie pods are created when resources are not sufficient for  secluding  pods and idleTimeout is set to a non-zero value   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-35414) Folders don't show up in dashboard view after upgrade

2019-06-12 Thread jenk...@mraz.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mraz commented on  JENKINS-35414  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Folders don't show up in dashboard view after upgrade   
 

  
 
 
 
 

 
 Experiencing this same issue with Dashboard View 2.10, Jenkins 2.164.1    I removed the Last Success Version plugin as its added column doesn't produce a working link any longer.  But, uninstalling the plugin left the default All view with the broken column.  I tried to replace the default view with a simple Job List but cannot get the nested folder structure provided by the default All view due to this issue.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57994) Shared Libraries: Branch specifier ignored when passing within list of shared libraries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Mutti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57994  
 
 
  Shared Libraries: Branch specifier ignored when passing within list of shared libraries   
 

  
 
 
 
 

 
Change By: 
 Mark Mutti  
 
 
Summary: 
 Shared Libraries: Branch specifier ignored when passing  a  within  list of shared libraries  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57994) Shared Libraries: Branch specifier ignored when passing a list of shared libraries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Mutti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57994  
 
 
  Shared Libraries: Branch specifier ignored when passing a list of shared libraries   
 

  
 
 
 
 

 
Change By: 
 Mark Mutti  
 

  
 
 
 
 

 
 I've searched for an existing bug describing this behavior to no avail, but please forgive me if this issue is a duplicate. *Expected Behavior*Per +[the official "Extending with Shared Libraries" doc|#using-libraries]+, we can load multiple libraries like so , using a branch specifier to fetch a specific version :{code:java}@Library(['my-shared-library', 'otherlib@abc1234']) _{code}   *Experienced Behavior*However, I've found that not to be the case and I've concluded that when using a list of shared libraries, the branch specifier is ignored: || ||Single Library||Library List|||_Code_|{code:java}@Library('otherlib@abc1234') _{code}|{code:java}@Library(['my-shared-library', 'otherlib@abc1234']) _{code}||_Loading Message_|{code:java}Loading library otherlib@abc1234{code}|{code:java}Loading library otherlib@abc1234{code}||_Result_|The println in the +dev branch+ is shown as expected|The println in the +master+ branch is shown||_Conclusion_|Works as intended!|Something's wrong. We should be able to version-pin any library from within a list|  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups

[JIRA] (JENKINS-57994) Shared Libraries: Branch specifier ignored when passing a list of shared libraries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Mutti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57994  
 
 
  Shared Libraries: Branch specifier ignored when passing a list of shared libraries   
 

  
 
 
 
 

 
Change By: 
 Mark Mutti  
 

  
 
 
 
 

 
 I've searched for an existing bug describing this behavior to no avail, but please forgive me if this issue is a duplicate. *Expected Behavior*Per +[the official "Extending with Shared Libraries" doc|#using-libraries] ] +, we can load multiple libraries like so:{code:java}@Library(['my-shared-library', 'otherlib@abc1234']) _{code}*Experienced Behavior*However, I've found that not to be the case and I've concluded that when using a list of shared libraries, the branch specifier is ignored: || ||Single Library||Library List|||_Code_|{code:java}@Library('otherlib@abc1234') _{code}|{code:java}@Library(['my-shared-library', 'otherlib@abc1234']) _{code}||_Loading Message_|{code:java}Loading library otherlib@abc1234{code}|{code:java}Loading library otherlib@abc1234{code}||_Result_|The println in the +dev branch+ is shown as expected|The println in the +master+ branch is shown||_Conclusion_|Works as intended!|Something's wrong. We should be able to version-pin any library from within a list|  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57994) Shared Libraries: Branch specifier ignored when passing a list of shared libraries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Mutti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57994  
 
 
  Shared Libraries: Branch specifier ignored when passing a list of shared libraries   
 

  
 
 
 
 

 
Change By: 
 Mark Mutti  
 

  
 
 
 
 

 
 I've searched for an existing bug describing this behavior to no avail, but please forgive me if this issue is a duplicate. *Expected Behavior*Per  +  [the official "Extending with Shared Libraries" doc|  [https://jenkins.io/doc/book/pipeline/shared-libraries/ #using-libraries]] + , we can load multiple libraries like so:{code:java}@Library(['my-shared-library', 'otherlib@abc1234']) _{code}  *Experienced Behavior*However, I've found that not to be the case and I've concluded that when using a list of shared libraries, the branch specifier is ignored: || ||Single Library||Library List|||_Code_|{code:java}@Library('otherlib@abc1234') _{code}|{code:java}@Library(['my-shared-library', 'otherlib@abc1234']) _{code}||_Loading Message_|{code:java}Loading library otherlib@abc1234{code}|{code:java}Loading library otherlib@abc1234{code}||_Result_|The println in the +dev branch+ is shown as expected|The println in the +master+ branch is shown||_Conclusion_|Works as intended!|Something's wrong. We should be able to version-pin any library from within a list|  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google

[JIRA] (JENKINS-57994) Shared Libraries: Branch specifier ignored when passing a list of shared libraries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Mutti created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57994  
 
 
  Shared Libraries: Branch specifier ignored when passing a list of shared libraries   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2019-06-12 21:30  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Mark Mutti  
 

  
 
 
 
 

 
 I've searched for an existing bug describing this behavior to no avail, but please forgive me if this issue is a duplicate.   Expected Behavior Per the official "Extending with Shared Libraries" doc, we can load multiple libraries like so: 

 

@Library(['my-shared-library', 'otherlib@abc1234']) _
 

 Experienced Behavior However, I've found that not to be the case and I've concluded that when using a list of shared libraries, the branch specifier is ignored:   
 

 
 
  
Single Library 
Library List 
 
 
Code

[JIRA] (JENKINS-57993) Noisy ClosedChannelException from DefaultJnlpSlaveReceiver.channelClosed

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-57993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57993  
 
 
  Noisy ClosedChannelException from DefaultJnlpSlaveReceiver.channelClosed   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-8360) Expose Maven Release Version via REST API Call: i.e. link build no. and Maven version

2019-06-12 Thread o...@nerdnetworks.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Mehegan updated  JENKINS-8360  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-8360  
 
 
  Expose Maven Release Version via REST API Call: i.e. link build no. and Maven version   
 

  
 
 
 
 

 
Change By: 
 Owen Mehegan  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-54439) Support configuration as code plugin

2019-06-12 Thread luisf.po...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Luis Pollo commented on  JENKINS-54439  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support configuration as code plugin   
 

  
 
 
 
 

 
 Any updates on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change

2019-06-12 Thread jthomp...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson started work on  JENKINS-57713  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jeff Thompson  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57830) Better default for PodTemplateStep.label

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-57830  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better default for PodTemplateStep.label   
 

  
 
 
 
 

 
 Note that pod names default to label.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-42679) Allow lock retrieval based on requested priority

2019-06-12 Thread tobias-jenk...@23.gs (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42679  
 
 
  Allow lock retrieval based on requested priority   
 

  
 
 
 
 

 
Change By: 
 Tobias Gruetzmacher  
 
 
Assignee: 
 Tobias Gruetzmacher  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-42679) Allow lock retrieval based on requested priority

2019-06-12 Thread tobias-jenk...@23.gs (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Gruetzmacher commented on  JENKINS-42679  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow lock retrieval based on requested priority   
 

  
 
 
 
 

 
 It seem some kind of priority support was already part of this plugin before version 1.7, but it was removed. I'll take a look at the merge request, but my focus is currently more on bug-fixing...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57993) Noisy ClosedChannelException from DefaultJnlpSlaveReceiver.channelClosed

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57993  
 
 
  Noisy ClosedChannelException from DefaultJnlpSlaveReceiver.channelClosed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 core  
 
 
Created: 
 2019-06-12 19:38  
 
 
Labels: 
 diagnostics logging kubernetes  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 Running KubernetesPipelineTest.runInPod you can see this unhelpful stack trace: 

 

  49.595 [run In Pod #1] [Pipeline] }
  49.595 [id=92]	INFO	o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent runinpod-...
  49.596 [id=92]	FINE	o.c.j.p.k.KubernetesCloud#connect: Building connection to Kubernetes kubernetes URL null namespace kubernetes-plugin-test
  49.596 [id=92]	FINE	o.c.j.p.k.KubernetesCloud#connect: Connected to Kubernetes kubernetes URL http://127.0.0.1:8080/
  49.648 [run In Pod #1] [Pipeline] // node
  49.654 [id=103]	WARNING	j.s.DefaultJnlpSlaveReceiver#channelClosed: IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.1.1.1:... remote=10.1.1.15/10.1.1.15:...]] / Computer.threadPoolForRemoting [#...] for runinpod-... terminated
java.nio.channels.ClosedChannelException
	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209)
	at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
	at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
	at

[JIRA] (JENKINS-57993) Noisy ClosedChannelException from DefaultJnlpSlaveReceiver.channelClosed

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-57993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-50664) Default slave labels are missing in kubernetes-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50664  
 
 
  Default slave labels are missing in kubernetes-plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 jekins  kuberentes  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-30894) Kubernetes plugin should support certificate-based https API calls

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30894  
 
 
  Kubernetes plugin should support certificate-based https API calls   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 certificate credentials  kuberentes  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-54540) Pods stuck in error state is not cleaned up

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54540  
 
 
  Pods stuck in error state is not cleaned up   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 jenkins jnlp jnlp-slave  kuberentes  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-55960) Missing DeclarativePipeline podTemplate parameters

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55960  
 
 
  Missing DeclarativePipeline podTemplate parameters
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 declarative declarative-variable-and-method-resolution  kuberentes  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-50864) kubernetes-cli-plugin is not working.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50864  
 
 
  kubernetes-cli-plugin is not working.   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes-plugin pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-47947) CGROUP_MATCHER_PATTERN does not work with Kubernetes >= 1.6

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47947  
 
 
  CGROUP_MATCHER_PATTERN does not work with Kubernetes >= 1.6   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 Docker kuberentes kubernetes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-55094) "commands" and "args" are being defaulted using Kubernetes plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55094  
 
 
  "commands" and "args" are being defaulted using Kubernetes plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin

2019-06-12 Thread sis...@live.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 sigur commented on  JENKINS-56305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need some help with init scripts on this plugin   
 

  
 
 
 
 

 
 Thank you, I promise this will only be used for good. note for future users: 'ios' is the name of the job  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-56735) Builds hanging after pod start in version 1.14.9

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56735  
 
 
  Builds hanging after pod start in version 1.14.9   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 jenkins  kuberenetes-plugin  kubernetes plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57449) Unable to use kubernetes agent block in declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57449  
 
 
  Unable to use kubernetes agent block in declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 declarative  kuberenetes- plugin  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-45885) Recieving context deadline exceeded when Helm and Tiller are interact

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45885  
 
 
  Recieving context deadline exceeded when Helm and Tiller are interact   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 helm  kuberenetes-plugin  pipeline tiller  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-52829) Is there a way to inherit a pod template with declarative pipeline?

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52829  
 
 
  Is there a way to inherit a pod template with declarative pipeline?   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57155) Not able to connect to aws EKS

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57155  
 
 
   Not able to connect to aws EKS
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes- plugin  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-47951) Pod or container environment variables are not recognized in declarative pipeline

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47951  
 
 
  Pod or container environment variables are not recognized in declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes- plugin  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57770) For the life of me cannot get this to work

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57770  
 
 
  For the life of me cannot get this to work   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-47055) Jenkins kubernetes plugin - support freestyle jobs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47055  
 
 
  Jenkins kubernetes plugin - support freestyle jobs   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57396) Pods Terminate before container image can download

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57396  
 
 
  Pods Terminate before container image can download   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 jenkins kuberenetes-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-49424) kubernetes plugin pipeline error with "error executing command in container: tls: use of closed connection"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49424  
 
 
  kubernetes plugin pipeline error with "error executing command in container: tls: use of closed connection"   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 jenkins  kuberenetes-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49660  
 
 
  Unable to configure plugin using ibm k8s   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes- plugin  plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-54540) Pods stuck in error state is not cleaned up

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54540  
 
 
  Pods stuck in error state is not cleaned up   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 jenkins jnlp jnlp-slave  kuberenetes-plugin  kuberentes plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56307  
 
 
  Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 kuberenetes-plugin  performance  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-50664) Default slave labels are missing in kubernetes-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50664  
 
 
  Default slave labels are missing in kubernetes-plugin   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 jekins  kuberenetes-plugin  kuberentes plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-55198) java.nio.channels.ClosedChannelException

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-55198  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.nio.channels.ClosedChannelException   
 

  
 
 
 
 

 
 The original report suggests the Artifactory plugin is involved. Any known way to reproduce this error from scratch?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-42643) Conditional application of triggers in Declarative

2019-06-12 Thread t...@tridnguyen.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tri Nguyen edited a comment on  JENKINS-42643  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Conditional application of triggers in Declarative   
 

  
 
 
 
 

 
 - I imagine the cron string could be set conditionally (only has a value on `master` branch, and  an empty string if not)? In the case that you call cron with an empty string, would it have any side effect? -   I tried this out, and while I can just set the cron job to an empty string, the problem is that I can't have an _expression_ evaluated for the triggers. Here's how I tried it:{code:java}pipeline {  triggers {cron( env.BRANCH_NAME.equals('master') ? '* 1 * * *' : '')  }} {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57951) [FUTURE] Use JIRA plugin to maintain release notes

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57951  
 
 
  [FUTURE] Use JIRA plugin to maintain release notes   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Summary: 
 [FUTURE] Use JIRA plugin to maintain release notes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57755) [FUTURE] Hot reload while running `mvn:hpi run` gives error

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57755  
 
 
  [FUTURE] Hot reload while running `mvn:hpi run` gives error   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Summary: 
 [FUTURE] Hot reload while running `mvn:hpi run` gives error  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57920) [FUTURE] Restrict user from naming a gitlab server configuration with already existing

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda commented on  JENKINS-57920  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [FUTURE] Restrict user from naming a gitlab server configuration with already existing   
 

  
 
 
 
 

 
 Presently, if a user names a gitlab server with the same name then only the oldest server with the name is persisted. No warning is shown at the runtime.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57883) [FUTURE] Remove gitlab server name from user view

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Not in the present plan, will reopen if we decide to do it.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57883  
 
 
  [FUTURE] Remove gitlab server name from user view   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57947) [FUTURE] More secured method to manage credentials in JCasC yaml

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57947  
 
 
  [FUTURE] More secured method to manage credentials in JCasC yaml   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Summary: 
 [FUTURE] More secured method to manage credentials in JCasC yaml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57686) Add Java 8 functional interfaces for behavioural design pattern

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57686  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Added stream apis for gitlab servers filter methods  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57686  
 
 
  Add Java 8 functional interfaces for behavioural design pattern
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57976) Add JCasC configuration instructions to README

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57976  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Added a basic instruction, will improve in future releases.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57976  
 
 
  Add JCasC configuration instructions to README   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57987) Unable to add environment variable for jcasc token

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57987  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Had a misunderstanding between global properties and environment variable.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57987  
 
 
  Unable to add environment variable for jcasc token   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57747  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed it by fetching public projects from /projects endpoint.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57747  
 
 
  Add form validation for gitlab gold and ultimate server urls   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57988  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 By adding persistent descriptor and saving in setter.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57988  
 
 
  UI not reflecting the state of the list of servers   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57992) QueueItemAuthenticatorMonitor.blurb is confusing for Windows users

2019-06-12 Thread jsoref+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57992  
 
 
  QueueItemAuthenticatorMonitor.blurb is confusing for Windows users   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Josh Soref  
 
 
Components: 
 core  
 
 
Created: 
 2019-06-12 18:27  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/blob/5562b2fec6428b730a7b88ad6390a7ed741ba792/core/src/main/resources/jenkins/security/QueueItemAuthenticatorMonitor/message.properties#L1 

 

blurb = Builds in Jenkins run as the virtual SYSTEM user with full permissions by default. \  

   On Windows, there's a SYSTEM account. Usually, users create per task accounts, e.g. a Jenkins account, and run services with those accounts. Because the Windows SYSTEM account (and is the equivalent of Unix root), it's very confusing to see a warning as the current warning displays.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-55353) Upgrade Jenkins core to 2.138.4

2019-06-12 Thread jsoref+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55353  
 
 
  Upgrade Jenkins core to 2.138.4   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 

  
 
 
 
 

 
 After tested the plugin to compile against different Jenkins core versions, I have detected some changes that I have to make to test it.  * Update Jenkins file to compile an test on Jenkins core 2.150.1, 2.164.1, and 2.168 (2 LTS and last weekly)* Compile and test weekly with JDK 11* Upgrade Jenkins core to 2.150.1, I will support 2 LTS versions* Remove  JDKInstaler  JDKInstaller  references, is not used in ssh-slaves and it is no longer in Jenkins core, it is in tool-jdk plugin* Remove deprecated constructors, all these constructors were marked with a warning in logs 6 months ago.* Remove unused code* Remove old fields related to deprecated constructors* Fix tests after changes* Remove deprecated package  depencency  dependency  javax.xml.bind* fix Inconsistent synchronization of hudson.plugins.sshslaves.SSHLauncher.host  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-56343) Intermittent java.io.NotSerializableException when running scripts in parallel

2019-06-12 Thread marcello_desa...@intuit.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcello de Sales commented on  JENKINS-56343  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent java.io.NotSerializableException when running scripts in parallel   
 

  
 
 
 
 

 
 

 

def releasePrs = prMergesMessages.collectEntries{ prShaMessage ->
def separate = prShaMessage.split(":")
[separate[0], separate[1]]
  }.collect{ entry ->
def matcher = entry.value =~ /(?#[0-9]+)/
def pr = matcher.find() ? matcher.group("prNumber") : "none"
matcher = null
[commitId: entry.key, prNumber: pr]
  } 

   We've been getting this on the same problem around the Matcher... I got the problem to be resolved for a while by setting the matcher to null... However, today we started experiencing the intermittent behavior without code changes...  I'm deciding to add a try/catch in this block with the hopes to not see this error again, but it's definitely difficult to spot the bug the first time due to the horrible logs... (See below)   The code is in a shared library already and it breaks all of our different DSL-based builds...     

 


n exception which occurred:
	in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals
	in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@63468bc9
	in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
	in object com.cloudbees.groovy.cps.impl.LoopBlockScopeEnv@16c46b7c
	in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
	in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@63fd3e95
	in field com.cloudbees.groovy.cps.impl.CallEnv.caller
	in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@47149d74
	in field com.cloudbees.groovy.cps.Continuable.e
	in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@24b7f5ac
	in field org.jenkinsci.plugins.workflow.cps.CpsThread.program
	in object org.jenkinsci.plugins.workflow.cps.CpsThread@3b872106
	in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads
	in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@606f1e48
	in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@606f1e48
Also:   org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
		at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.cancel(CpsBodyExecution.java:253)
		at org.jenkinsci.plugins.workflow.steps.BodyExecution.cancel(BodyExecution.java:76)
		at org.jenkinsci.plugins.workflow.cps.steps.ParallelStepExecution.stop(ParallelStepExecution.java:67)
		at org.jenkinsci.plugins.workflow.cps.CpsThread.stop(CpsThread.java:296)
		at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:1151)
		at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:1140)
Caused: java.io.NotSerializableException: java.util.regex.Matcher
	at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:926)
	at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65)
	at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56)
	at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50)
	at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179)
	at

[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.

2019-06-12 Thread d...@dsak.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dave Miller commented on  JENKINS-55075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline: If job fails it will run again on next poll.   
 

  
 
 
 
 

 
 I just upgraded to 1.10.0 to address a different issue, and I'm trying to understand why commit 283834eabea30f31cde59b1ab3b743a01b2f47cb, which claims to be associated with this ticket, is now throwing un-actionable "Severe warnings" when it finds duplicate SyncIDs. Why do duplicate syncIDs justify a severe log entry, what do they have to to with this ticket, and how should they be addressed? These "Severe warnings" are dramatically clogging our server logs. Paul Allen?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-55013) support for App Center

2019-06-12 Thread mez.pah...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan commented on  JENKINS-55013  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support for App Center   
 

  
 
 
 
 

 
 Hi Abel Berhane good question. For the HockeyApp plugin no. I'm not going to support that or allow updates to it. If something critical comes up I'll take a look but the intention is to drop it. For the AppCenter plugin yes I will. And I'm also open to pull requests if people want to contribute.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-55013) support for App Center

2019-06-12 Thread aberh...@topps.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abel Berhane commented on  JENKINS-55013  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support for App Center   
 

  
 
 
 
 

 
 Hi there Mez. I hope that things are going well. I have added the App Center Plugin and attempted to run a job. Question, will you be making continued updates to this plugin before the full depreciation of HockeyApp in November?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-56581) org.jenkinsci.remoting.protocol.IOHub takes 100% CPU

2019-06-12 Thread jthomp...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-56581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.jenkinsci.remoting.protocol.IOHub takes 100% CPU   
 

  
 
 
 
 

 
 That is a surprising amount of messages, all with the same timestamp. I still have no idea what's going on with it, though. If you can gather any further information and diagnosis, please share it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-43656) Allow SSH Agent to be used with Promted Build Plugin

2019-06-12 Thread isaacleww...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Isaac Lew commented on  JENKINS-43656  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow SSH Agent to be used with Promted Build Plugin   
 

  
 
 
 
 

 
 Hello, I'm running into this issue as well. Are there any known workarounds?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-52205) Add support of JCasC plugin to the Locale Plugin

2019-06-12 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52205  
 
 
  Add support of JCasC plugin to the Locale Plugin   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 jcasc-compatibility  stalled-pr  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-52205) Add support of JCasC plugin to the Locale Plugin

2019-06-12 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev stopped work on  JENKINS-52205  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page

2019-06-12 Thread bot.git...@meterian.io (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Meterian Bot edited a comment on  JENKINS-57154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page   
 

  
 
 
 
 

 
 Same here. Very frustrating as v0.31 is affected by this vulnerability:  [ https://jenkins.io/security/advisory/2019-04-30/#SECURITY-443 ]But downgrading to 0.31 gives us back a configuration page that you can save  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page

2019-06-12 Thread bot.git...@meterian.io (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Meterian Bot commented on  JENKINS-57154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page   
 

  
 
 
 
 

 
 Same here. Very frustrating as v0.31 is affected by this vulnerability: https://jenkins.io/security/advisory/2019-04-30/#SECURITY-443  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57835) Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'

2019-06-12 Thread fraser.ad...@prudential.co.uk (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fraser Adair updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57835  
 
 
  Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'
 

  
 
 
 
 

 
Change By: 
 Fraser Adair  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated  JENKINS-57991  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57991  
 
 
  Improve the error message when the credentials of the remote Jenkins are not correct   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57835) Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'

2019-06-12 Thread fraser.ad...@prudential.co.uk (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fraser Adair updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57835  
 
 
  Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'
 

  
 
 
 
 

 
Change By: 
 Fraser Adair  
 

  
 
 
 
 

 
 Connectivity between Jenkins and Subversion fails intermittently with  'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: 'Remote host closed connection during handshake' error  these errors .  When error appears it seems any further attempts result in same errors and  Appears   the only way to recover appears to be to restart Jenkins. Can happen a few times a day but can also go several days without issue.Trying to understand why receiving these intermittent issues and how to resolve.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57988) UI not reflecting the state of the list of servers

2019-06-12 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57988  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57988  
 
 
  UI not reflecting the state of the list of servers   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz started work on  JENKINS-57991  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57835) Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'

2019-06-12 Thread fraser.ad...@prudential.co.uk (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fraser Adair updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57835  
 
 
  Jenkins - Subversion - 'svn: E170001: HTTP proxy authorization failed' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'
 

  
 
 
 
 

 
Change By: 
 Fraser Adair  
 
 
Summary: 
 Jenkins - Subversion -  '  svn: E170001: HTTP proxy authorization failed ' and/or 'svn: E175002: SSL handshake failed: Remote host closed connection during handshake'   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57945) p4 sync corrupts symlinks

2019-06-12 Thread kwi...@perforce.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth commented on  JENKINS-57945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: p4 sync corrupts symlinks   
 

  
 
 
 
 

 
 Hi Michael Rose - Matthew Smeeth was uanble to repro this on 2.166 so I just tried upgrading my Jenkins to 2.164.2 and it seems to have solved the problem. Therefore this looks like a Jenkins bug or at least related to the version of Java it ships with or other dependencies. Are you able to upgrade jenkins to confirm this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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

[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57991  
 
 
  Improve the error message when the credentials of the remote Jenkins are not correct   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 job-import-plugin  
 
 
Created: 
 2019-06-12 15:41  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Pierre Beitz  
 

  
 
 
 
 

 
 Current situation does an error difficult to decrypt because the plugin doesn't check for the response status code:   

 
2019-06-12 11:14:33.668+ [id=86689] SEVERE  o.j.c.p.j.client.RestApiClient#getRemoteItems: Failed to list job from remote  org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 3; The element type "hr" must be terminated by the matching end-tag "". at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.jenkins.ci.plugins.jobimport.client.RestApiClient.getRemoteItems(RestApiClient.java:34) at org.jenkins.ci.plugins.jobimport.JobImportAction.doQueryInternal(JobImportAction.java:278) at org.jenkins.ci.plugins.jobimport.JobImportAction.doQuery(JobImportAction.java:174) 

   Proposed fix checking for this status code: 

 
Jun 12, 2019 5:36:04 PM org.jenkins.ci.plugins.jobimport.client.RestApiClient getRemoteItems
SEVERE: Failed to list job from remote /SEVERE: Failed to list job from remote /org.acegisecurity.AccessDeniedException: Remote Jenkins denied access.

[JIRA] (JENKINS-57991) Improve the error message when the credentials of the remote Jenkins are not correct