[JIRA] (JENKINS-58157) "delete build" button is to long

2019-06-27 Thread mmh19891...@qq.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Minghui Ma commented on  JENKINS-58157  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "delete build" button is to long   
 

  
 
 
 
 

 
 edit the "build info" set the title  
 

  
 
 
 
 

 
 
 

 
 
 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.200205.1561341295000.11184.1561701180166%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58237) dSYMs not generated in version 2.0.11

2019-06-27 Thread kazuhid...@linux-powered.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kazuhide Takahashi commented on  JENKINS-58237  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dSYMs not generated in version 2.0.11   
 

  
 
 
 
 

 
 biAji Na The old Xcode seems to have been somewhere else, but in recent Xcode, dSYM files should always be created in build/brbrbr.../.xcarchive/dSYMs under the build directory. And the plug-in assumes that dSYMs file is there, and it is searching only there. However, I see your message, the dSYMs file seems to be in a different place (other than build/brbrbr.../.xcarchive/dSYMs). Are you running the build with some special parameters for xcodebuild ?  
 

  
 
 
 
 

 
 
 

 
 
 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.200298.156162958.11182.1561699980182%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-18696) Not all test results are being reported

2019-06-27 Thread khneal+jenkins...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Neal commented on  JENKINS-18696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not all test results are being reported   
 

  
 
 
 
 

 
 Usually the newer issue duplicates the older issue, but I found that one first and submitted a PR today. This issue has a PR open, but it's out of date.  
 

  
 
 
 
 

 
 
 

 
 
 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.150044.1373481073000.11174.1561699441020%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-18696) Not all test results are being reported

2019-06-27 Thread khneal+jenkins...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Neal updated  JENKINS-18696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-18696  
 
 
  Not all test results are being reported   
 

  
 
 
 
 

 
Change By: 
 Kevin Neal  
 
 
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.150044.1373481073000.11176.1561699441216%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58248) CLI command install-plugin does not take Proxy configuration into account

2019-06-27 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58248  
 
 
  CLI command install-plugin does not take Proxy configuration into account   
 

  
 
 
 
 

 
Change By: 
 Allan BURDAJEWICZ  
 

  
 
 
 
 

 
 When trying to install a plugin with the Jenkins CLI and providing a URL as argument, the proxy configuration of the Jenkins master does not seem to be taken into account.For example if I use the following command: > {code}  java -jar jenkins-cli.jar -logger FINE -s https://my.jenkinsexample.com -noCertificateCheck -auth myUser:myPassword install-plugin https://jenkins-updates.cloudbees.com/download/plugins/cloudbees-aws-cli/1.5.9/cloudbees-aws-cli.hpi {code}   But requires to be behind an HTTP proxy to be able to download that plugin, it fails with: > {code}  ERROR: Unexpected exception occurred while performing install-plugin command.  >  java.net.ConnectException: Connection timed out  {code}   Even if I have a proxy configured under **Manage Jenkins > Manage Plugins > Advanced**.h3. Evidence* https://github.com/jenkinsci/jenkins/blob/jenkins-2.176.1/core/src/main/java/hudson/cli/InstallPluginCommand.java#L100-L122* https://github.com/jenkinsci/jenkins/blob/jenkins-2.176.1/core/src/main/java/hudson/FilePath.java#L965-L976h3. WorkaroundOnly workaround seem to be to set the proxy via system properties on the master:{code}-Dhttps.proxyHost=myproxy.server.com-Dhttps.proxyPort=8080-Dhttps.proxyUser=myUser-Dhttp.proxyPassword=myPassword{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-58248) CLI command install-plugin does not take Proxy configuration into account

2019-06-27 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58248  
 
 
  CLI command install-plugin does not take Proxy configuration into account   
 

  
 
 
 
 

 
Change By: 
 Allan BURDAJEWICZ  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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.200311.156169808.11167.1561698780080%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58248) CLI command install-plugin does not take Proxy configuration into account

2019-06-27 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58248  
 
 
  CLI command install-plugin does not take Proxy configuration into account   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 cli, core  
 
 
Created: 
 2019-06-28 05:01  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Allan BURDAJEWICZ  
 

  
 
 
 
 

 
 When trying to install a plugin with the Jenkins CLI and providing a URL as argument, the proxy configuration of the Jenkins master does not seem to be taken into account. For example if I use the following command: > java -jar jenkins-cli.jar -logger FINE -s https://my.jenkinsexample.com -noCertificateCheck -auth myUser:myPassword install-plugin https://jenkins-updates.cloudbees.com/download/plugins/cloudbees-aws-cli/1.5.9/cloudbees-aws-cli.hpi But requires to be behind an HTTP proxy to be able to download that plugin, it fails with: > ERROR: Unexpected exception occurred while performing install-plugin command.  > java.net.ConnectException: Connection timed out  Even if I have a proxy configured under *Manage Jenkins > Manage Plugins > Advanced*. Evidence 
 
https://github.com/jenkinsci/jenkins/blob/jenkins-2.176.1/core/src/main/java/hudson/cli/InstallPluginCommand.java#L100-L122 
https://github.com/jenkinsci/jenkins/blob/jenkins-2.176.1/core/src/main/java/hudson/FilePath.java#L965-L976 
 Workaround Only workaround seem to be to set the proxy via system properties on the master: 

 

-Dhttps.proxyHost=myproxy.server.com
-Dhttps.proxyPort=8080
-Dhttps.proxyUser=myUser
-Dhttp.proxyPassword=myPassword
 

   

[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics

2019-06-27 Thread marky.r.jack...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson stopped work on  JENKINS-49222  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Marky Jackson  
 
 
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.188064.1517215041000.11164.1561697400277%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin

2019-06-27 Thread marky.r.jack...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson commented on  JENKINS-58247  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix link to Jenkins dockerhub for plugin   
 

  
 
 
 
 

 
 PR awaiting approval: https://github.com/jenkinsci/amazon-ecs-plugin/pull/112  
 

  
 
 
 
 

 
 
 

 
 
 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.200310.156169730.11161.1561697340826%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin

2019-06-27 Thread marky.r.jack...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58247  
 
 
  Fix link to Jenkins dockerhub for plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Marky Jackson  
 
 
Components: 
 amazon-ecs-plugin  
 
 
Created: 
 2019-06-28 04:48  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marky Jackson  
 

  
 
 
 
 

 
 Fix links to dockerhub. Currently references jenkinsci/jnlp-slave but should be jenkins/jnlp-slave  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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


[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin

2019-06-27 Thread marky.r.jack...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson started work on  JENKINS-58247  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Marky Jackson  
 
 
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.200310.156169730.11159.1561697340696%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58246) Better setup and runbook style documentation for this plugin

2019-06-27 Thread marky.r.jack...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson commented on  JENKINS-58246  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Better setup and runbook style documentation for this plugin   
 

  
 
 
 
 

 
 Link to GitHub repo issues I created for this: https://github.com/jenkinsci/prometheus-plugin/issues/113  
 

  
 
 
 
 

 
 
 

 
 
 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.200309.1561697059000.11155.1561697160112%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58246) Better setup and runbook style documentation for this plugin

2019-06-27 Thread marky.r.jack...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58246  
 
 
  Better setup and runbook style documentation for this plugin   
 

  
 
 
 
 

 
Change By: 
 Marky Jackson  
 
 
Summary: 
 Better setup and  runback  runbook  style documentation for this 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.200309.1561697059000.11153.1561697100309%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58246) Better setup and runback style documentation for this plugin

2019-06-27 Thread marky.r.jack...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58246  
 
 
  Better setup and runback style documentation for this plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Marky Jackson  
 
 
Components: 
 prometheus-plugin  
 
 
Created: 
 2019-06-28 04:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marky Jackson  
 

  
 
 
 
 

 
 As a plugin maintainer, I need to create better setup and runbook style documentation that will live on the wiki.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-58244) JIRA Site at folder level doesn't show credentials for non-admin users

2019-06-27 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58244  
 
 
  JIRA Site at folder level doesn't show credentials for non-admin users   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Status: 
 In Progress 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.200307.156168212.11149.1561692120086%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception

2019-06-27 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 should be fixed by https://github.com/jenkinsci/jira-plugin/pull/192  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57664  
 
 
  On Release of a Version recieve a Null Pointer exception   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Olivier Lamy  
 
 
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.199597.1558709739000.11145.1561691880428%40Atlassian.JIRA.
For more 

[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception

2019-06-27 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57664  
 
 
  On Release of a Version recieve a Null Pointer exception   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Labels: 
 jira-plugin-3.0.8  
 

  
 
 
 
 

 
 
 

 
 
 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.199597.1558709739000.11140.1561691820227%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58244) JIRA Site at folder level doesn't show credentials for non-admin users

2019-06-27 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy commented on  JENKINS-58244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JIRA Site at folder level doesn't show credentials for non-admin users   
 

  
 
 
 
 

 
 pr https://github.com/jenkinsci/jira-plugin/pull/193  
 

  
 
 
 
 

 
 
 

 
 
 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.200307.156168212.11138.1561690740047%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48583) Junit test reports are dropped if they have a timestamp within the same second as another test report

2019-06-27 Thread khneal+jenkins...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Neal started work on  JENKINS-48583  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kevin Neal  
 
 
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.187223.1513365491000.11133.1561690020316%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58245) jenkins job is block on master node

2019-06-27 Thread hp...@163.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 hong feng created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58245  
 
 
  jenkins job is block on master node   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2019-06-28-10-15-57-137.png, image-2019-06-28-10-16-16-642.png, image-2019-06-28-10-16-27-547.png, image-2019-06-28-10-24-30-945.png, image-2019-06-28-10-25-21-154.png  
 
 
Components: 
 pipeline  
 
 
Created: 
 2019-06-28 02:25  
 
 
Environment: 
 linux docker  
 
 
Labels: 
 blocked jobblock  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 hong feng  
 

  
 
 
 
 

 
 i'm using declarative pipeline to build android and ios app, jenkins master is running on docker. sometime jenkins job will block on master node , can't dispatch to slave node, but my slave node is everything ok. the image is blow. my slave is physical machine, and declarative pipeline will start a docker to run job. my server and agent is centos, linux kernel version is 3.10.0. my jdk version is 1.8.0. somtimes block jobs, the block job is randomly, i have no idea what to do.                     
 

  
 
 
 
 

 

[JIRA] (JENKINS-58157) "delete build" button is to long

2019-06-27 Thread linuxsu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58157  
 
 
  "delete build" button is to long   
 

  
 
 
 
 

 
Change By: 
 Rick  
 
 
Attachment: 
 image-2019-06-28-10-11-20-506.png  
 

  
 
 
 
 

 
 
 

 
 
 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.200205.1561341295000.11128.1561687920343%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58157) "delete build" button is to long

2019-06-27 Thread linuxsu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick commented on  JENKINS-58157  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "delete build" button is to long   
 

  
 
 
 
 

 
  This is my screenshot. There's no problem.  
 

  
 
 
 
 

 
 
 

 
 
 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.200205.1561341295000.11130.1561687920412%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58244) JIRA Site at folder level doesn't show credentials for non-admin users

2019-06-27 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58244  
 
 
  JIRA Site at folder level doesn't show credentials for non-admin users   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Olivier Lamy  
 
 
Components: 
 jira-plugin  
 
 
Created: 
 2019-06-28 00:35  
 
 
Labels: 
 jira-plugin-3.0.8  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Olivier Lamy  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-58244) JIRA Site at folder level doesn't show credentials for non-admin users

2019-06-27 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy started work on  JENKINS-58244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
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.200307.156168212.11126.1561682160230%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48583) Junit test reports are dropped if they have a timestamp within the same second as another test report

2019-06-27 Thread khneal+jenkins...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Neal assigned an issue to Kevin Neal  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I've opened a PR to fix this issue: https://github.com/jenkinsci/junit-plugin/pull/120 Builds are a bit backed up, but hopefully it will go through by tomorrow. Sanae Rosen Jes Andersen or anybody else, do you have time to review the PR to see if it will fix your use case?  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48583  
 
 
  Junit test reports are dropped if they have a timestamp within the same second as another test report   
 

  
 
 
 
 

 
Change By: 
 Kevin Neal  
 
 
Assignee: 
 Kevin Neal  
 

  
 
 
 
 

 
 
 

 
 
 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.187223.1513365491000.11120.1561678500284%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script

2019-06-27 Thread jbennett2...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeffrey Bennett commented on  JENKINS-37984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script   
 

  
 
 
 
 

 
 There is a work around, of sorts.  There is a fixed limit to the size of the groovy.  No way around that limit, but you can do things to minimize what's in groovy. Eliminate clutter.   For us, that was stuff like echo statements, and unused variables.  You might also be able to alter the jenkins job's configuration rather than setting options in the groovy.   A better answer is to shift large blocks to scripts.  For example, if you have a bunch of "sh" or "bat" commands in a row, put them in a script file, then invoke the script from groovy.    Good luck.  This limit should still be fixed (or raised).  You just cannot get to enterprise worthy pipelines with 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.174127.1473169024000.11065.1561674001276%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58018) High CPU load at slave with SSH-agent running freestyle project

2019-06-27 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-58018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: High CPU load at slave with SSH-agent running freestyle project   
 

  
 
 
 
 

 
 Hmmm ...  So, it's not really a CPU load problem. sshd also shows heavy CPU load. That's good to know. That's a lot of data transfer. I didn't have anything like that with my jobs trying to duplicate the problem. My console output shows practically nothing. Do you get a large amount of stuff in your console output? A lot of times things that appear to be Remoting problems turn out to be caused by plugins. Sometimes it involves weird interactions between plugins. That could be what's going on here. Unfortunately, it can be complicated to isolate the problem and track it down. I don't have experience with the retainOrigin setting. Reading the code, it appears to reduce some of the resource consumption. However, if you're getting to the point where that makes a difference, there is probably something going on that is still keeping the consumption too high. Sometimes it's high server load. Network issues. Agent load. VM host issues or load. These links have some related info: JENKINS-49736, JENKINS-48810, and https://groups.google.com/forum/#!topic/jenkinsci-dev/zAkbD_NmnrM . Most of these point to resource issues. These can be really challenging to track down.  
 

  
 
 
 
 

 
 
 

 
 
 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.200038.1560499496000.11062.1561673580215%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.

2019-06-27 Thread omar.velazq...@softtek.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Omar Velazquez commented on  JENKINS-58224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
 

  
 
 
 
 

 
 Fixed, I really appreciate your quick response Best regards  
 

  
 
 
 
 

 
 
 

 
 
 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.200284.1561581863000.11060.1561672740155%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57595) with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors

2019-06-27 Thread a...@allir.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aðalsteinn Rúnarsson commented on  JENKINS-57595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: with GitHub OAuth plugin 0.31->0.32 Matrix-based security errors   
 

  
 
 
 
 

 
 Exact same issue here too, with same versions. 0.32 of Github Authentication. 2.4.2 of Matrix Authorization.  
 

  
 
 
 
 

 
 
 

 
 
 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.199519.1558510674000.11048.1561671480465%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"

2019-06-27 Thread iss...@aol.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Isaac Cohen commented on  JENKINS-57351  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for making Jenkins a "GitHub App"   
 

  
 
 
 
 

 
 depends on https://github.com/kohsuke/github-api/pull/522 which would implement GitHub Apps for kohsuke/github-api 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.199127.1557217283000.11043.1561670820168%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler

2019-06-27 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-53322  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove patched dom4j from Stapler   
 

  
 
 
 
 

 
 PR in Stapler to change to standard dom4j: https://github.com/stapler/stapler/pull/164 Enablement PR in Jenkins to old or new to work fine: https://github.com/jenkinsci/jenkins/pull/4089 ec2-plugin PR to enable old or new to work fine: https://github.com/jenkinsci/ec2-plugin/pull/372 (Already merged) Additional PRs to come later to include the new versions.  
 

  
 
 
 
 

 
 
 

 
 
 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.193404.153555107.11040.1561669800262%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58243) P4-plugin Multiple jobs with same stream do not trigger

2019-06-27 Thread kiegerha...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 kyle ian created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58243  
 
 
  P4-plugin Multiple jobs with same stream do not trigger   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2019-06-27 21:06  
 
 
Environment: 
 Jenkins 2.181  P4 Plugin 1.10.0  Windows 10 Pro  
 
 
Labels: 
 perforce p4-plugin p4  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 kyle ian  
 

  
 
 
 
 

 
 I have Perforce and Swarm set up to trigger the Jenkins p4 plugin as written in the docs, which I have confirmed works for me on a git multibranch pipeline, where the branches' Jenkinsfile specifies `pipelineTriggers([p4Trigger()])` as part of its properties and the branch specified matches a stream name. In an effort to do away with the multibranch pipeline for ease of adding new streams, I'm moving toward a job DSL bootstrap where I build out a set of folders under which many job pipelines are created for each stream. One of these subjobs, which shares the name of the stream ( "build-refactor" ) will act as the job to be triggered by p4trigger, and then trigger other pipeline jobs in the folder; this p4trigger job I have set up this up as follows in the pipelineJob config: 

 

pipelineJob("${streamFolder}/${stream.key}") {
   configure { project ->
 project / 'triggers' << 'org.jenkinsci.plugins.p4.trigger.P4Trigger'{
   spec ''
   }
}
 

   

[JIRA] (JENKINS-58243) P4-plugin Multiple jobs with same stream name do not trigger

2019-06-27 Thread kiegerha...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 kyle ian updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58243  
 
 
  P4-plugin Multiple jobs with same stream name do not trigger   
 

  
 
 
 
 

 
Change By: 
 kyle ian  
 
 
Summary: 
 P4-plugin Multiple jobs with same stream  name  do not trigger  
 

  
 
 
 
 

 
 
 

 
 
 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.200306.1561669582000.11038.1561669620183%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50156) Check Gendarme Parser Test on Windows

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-50156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50156  
 
 
  Check Gendarme Parser Test on Windows   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.189173.1520982705000.11021.1561669381975%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57278) Console Log View

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-57278  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57278  
 
 
  Console Log View   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.199044.1556741728000.11036.1561669382126%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50155) Make all integration tests run on Windows

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-50155  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50155  
 
 
  Make all integration tests run on Windows   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.189172.1520982552000.11019.1561669381954%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57281) Details Tab (in Details View)

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-57281  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57281  
 
 
  Details Tab (in Details View)   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.199047.1556742712000.11032.1561669382088%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-56007  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56007  
 
 
  Can't copy source files from slave to master if security is enabled
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.197425.1549494089000.11017.1561669381932%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57391) Id for Snipped Generator Page

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-57391  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57391  
 
 
  Id for Snipped Generator Page
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.199173.1557437154000.11034.1561669382107%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57817) Job DSL + Warnings-NG + Spotbugs not working

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-57817  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57817  
 
 
  Job DSL + Warnings-NG + Spotbugs not working   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.199771.1559562134000.11024.1561669382004%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57098) JSON Exchange format for import/export?

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-57098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57098  
 
 
  JSON Exchange format for import/export?   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.198843.16000.11027.1561669382037%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57245) Support Kotlin compiler warnings (in an obvious manner)

2019-06-27 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-57245  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57245  
 
 
  Support Kotlin compiler warnings (in an obvious manner)   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 5.2.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.199008.1556622259000.11030.1561669382068%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58242) Look into Failed Junit Test on Ubuntu

2019-06-27 Thread natasha.st...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58242  
 
 
  Look into Failed Junit Test on Ubuntu   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 plugin-installation-manager-tool  
 
 
Created: 
 2019-06-27 20:58  
 
 
Labels: 
 gsoc-2019 plugin-manager  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Natasha Stopa  
 

  
 
 
 
 

 
 The junit test for bundled plugins is failing on Ubuntu but didn't on Mac. The following error was thrown.  java.lang.reflect.InaccessibleObjectException: Unable to make boolean jdk.nio.zipfs.ZipFileSystem.isDirectory(byte[]) throws java.io.IOException accessible: module jdk.zipfs does not "opens jdk.nio.zipfs" This might be due to differences in jdks. We might want to add a note in the documentation about what jdks the tool is compatible with.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-58200) Console logs are masking my data as "FILTERED"

2019-06-27 Thread hc...@marqeta.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henry Chen updated  JENKINS-58200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58200  
 
 
  Console logs are masking my data as "FILTERED"   
 

  
 
 
 
 

 
Change By: 
 Henry Chen  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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.200256.1561506249000.11006.1561668720933%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58200) Console logs are masking my data as "FILTERED"

2019-06-27 Thread hc...@marqeta.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henry Chen updated  JENKINS-58200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58200  
 
 
  Console logs are masking my data as "FILTERED"   
 

  
 
 
 
 

 
Change By: 
 Henry Chen  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.200256.1561506249000.11008.1561668720957%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58200) Console logs are masking my data as "FILTERED"

2019-06-27 Thread hc...@marqeta.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henry Chen commented on  JENKINS-58200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Console logs are masking my data as "FILTERED"   
 

  
 
 
 
 

 
 Apologies, I found the issue. Somehow the environment used had the incorrect build configurations. Nothing to do with your plugin. I'm closing out. Thank you!  
 

  
 
 
 
 

 
 
 

 
 
 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.200256.1561506249000.11004.1561668720806%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58241) Support comments to skip line

2019-06-27 Thread timjaco...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58241  
 
 
  Support comments to skip line   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Natasha Stopa  
 
 
Components: 
 plugin-installation-manager-tool  
 
 
Created: 
 2019-06-27 19:38  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tim Jacomb  
 

  
 
 
 
 

 
 In install-plugins.sh it skips lines starting with # I tried this on the plugins.txt file we use for our docker image, and it failed because we have a couple of commented out plugins in there, see stacktrace: 

 

Exception in thread "main" java.lang.IllegalArgumentException: Illegal character in fragment at index 61: https://updates.jenkins.io/download/plugins/#sonar/2.9-hmcts/#sonar.hpiException in thread "main" java.lang.IllegalArgumentException: Illegal character in fragment at index 61: https://updates.jenkins.io/download/plugins/#sonar/2.9-hmcts/#sonar.hpi at java.net.URI.create(URI.java:852) at org.apache.http.client.methods.HttpGet.(HttpGet.java:66) at io.jenkins.tools.pluginmanager.impl.PluginManager.downloadToFile(PluginManager.java:356) at io.jenkins.tools.pluginmanager.impl.PluginManager.downloadPlugin(PluginManager.java:301) at io.jenkins.tools.pluginmanager.impl.PluginManager.downloadPlugins(PluginManager.java:196) at io.jenkins.tools.pluginmanager.impl.PluginManager.start(PluginManager.java:111) at io.jenkins.tools.pluginmanager.cli.Main.main(Main.java:94)Caused by: java.net.URISyntaxException: Illegal character in fragment at index 61: https://updates.jenkins.io/download/plugins/#sonar/2.9-hmcts/#sonar.hpi at java.net.URI$Parser.fail(URI.java:2848) at java.net.URI$Parser.checkChars(URI.java:3021) at java.net.URI$Parser.parse(URI.java:3067) at java.net.URI.(URI.java:588) at java.net.URI.create(URI.java:850) ... 6 more  

  

[JIRA] (JENKINS-58200) Console logs are masking my data as "FILTERED"

2019-06-27 Thread tzach.solo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tzach Solomon commented on  JENKINS-58200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Console logs are masking my data as "FILTERED"   
 

  
 
 
 
 

 
 Henry Chen, I do not understand, are you using the 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.200256.1561506249000.11000.1561662960111%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57856) subversion list branch/tags not working with release plugin

2019-06-27 Thread 4rch...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arch Loy commented on  JENKINS-57856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: subversion list branch/tags not working with release plugin   
 

  
 
 
 
 

 
 Made some experiments. Looking at configuration file, both parameters definitions are same btw "normal" subversion parameter and "release". By modifing the configuration file, use the same parameter name. Now it list my branches and tags.   Conclusion : the problem exists on the configuration page. It seems that on configuration, subversion plugin register our parameter. But not correctly when it comes from Release 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.199815.1559723995000.10998.1561662600262%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57856) subversion list branch/tags not working with release plugin

2019-06-27 Thread 4rch...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arch Loy commented on  JENKINS-57856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: subversion list branch/tags not working with release plugin   
 

  
 
 
 
 

 
 'kay. I will try to debug, maybe it's trivial  
 

  
 
 
 
 

 
 
 

 
 
 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.199815.1559723995000.10988.1561659060107%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source

2019-06-27 Thread ethanjdiam...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Diamond commented on  JENKINS-58172  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source   
 

  
 
 
 
 

 
 Thanks for the quick turnaround Liam! Unfortunately it doesn't seem to have fixed my problem. I've attached images proving that the plugin was installed correctly and the error message when I try to build. It looks like the API is reporting the tag as "Not Found", which is what it does when you try to hit that API and are unauthenticated. I think the auth might be failing. For example, if you go to: https://api.github.com/repos/rafastealth/ios-patient-client/git/refs/tags/0.0.12 you'll see it's reporting the same not found message and it's because you don't have access.  
 

  
 
 
 
 

 
 
 

 
 
 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.200223.1561408065000.10984.1561658882015%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source

2019-06-27 Thread ethanjdiam...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Diamond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58172  
 
 
  Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source   
 

  
 
 
 
 

 
Change By: 
 Ethan Diamond  
 
 
Attachment: 
 plugin_installed.png  
 

  
 
 
 
 

 
 
 

 
 
 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.200223.1561408065000.10982.1561658881938%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source

2019-06-27 Thread ethanjdiam...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Diamond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58172  
 
 
  Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source   
 

  
 
 
 
 

 
Change By: 
 Ethan Diamond  
 
 
Attachment: 
 error_message.png  
 

  
 
 
 
 

 
 
 

 
 
 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.200223.1561408065000.10976.1561658820216%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop

2019-06-27 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46076  
 
 
  Test flake in CpsThreadTest.stop   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Released As: 
 workflow-job 2.33  
 

  
 
 
 
 

 
 
 

 
 
 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.184309.1502230337000.10970.1561658700351%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source

2019-06-27 Thread ethanjdiam...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Diamond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58172  
 
 
  Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source   
 

  
 
 
 
 

 
Change By: 
 Ethan Diamond  
 

  
 
 
 
 

 
 *Issue:*   When I click Jenkins reports a tag that exists as "Not Found" and failing the build with this message:   12:52:41 Branch indexing 19:52:41 [2019-06-24T19:52:41.964Z] Connecting to [https://api.github.com|https://api.github.com/] using dev-rafabuildadmin/** (github dev-rafabuildadmin user (required to publish build/deploy status)) 12:52:42 java.io.FileNotFoundException: [https://api.github.com/repos/rafastealth/ios-patient-client/git/refs/tags/0.0.4] 12:52:42     at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) 12:52:42     at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) 12:52:42     at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) 12:52:42     at org.kohsuke.github.Requester.parse(Requester.java:625) 12:52:42     at org.kohsuke.github.Requester.parse(Requester.java:607) 12:52:42     at org.kohsuke.github.Requester._to(Requester.java:285) 12:52:42 Caused: org.kohsuke.github.GHFileNotFoundException: \{"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"} 12:52:42     at org.kohsuke.github.Requester.handleApiError(Requester.java:699) 12:52:42     at org.kohsuke.github.Requester._to(Requester.java:306) 12:52:42     at org.kohsuke.github.Requester.to(Requester.java:247) 12:52:42     at org.kohsuke.github.GHRepository.getRef(GHRepository.java:891) 12:52:42     at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1521) 12:52:42     at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582) 12:52:42     at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98) 12:52:42     at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) 12:52:42     at hudson.model.ResourceController.execute(ResourceController.java:97) 12:52:42    at hudson.model.Executor.run(Executor.java:429) 12:52:42 Finished: FAILURE   See "github_tag.png" for proof the tag does indeed exist. I've tried re-indexing, but the issue never resolves.   *Repro Steps:*   - Set up tags to build with your repo (see tag_setup.png) - Create a tag (say, 0.0.4) in your git repo and push it up to origin. This will cause it to auto build. - In git, delete the tag and push that deletion up to Github.    - In  Jenkins, in the job made by the tag, click "Build Now" - It should fail to find the tag - In  git, tag a new commit with the same tag name (0.0.4) as above and push it up to Github. - In Jenkins, in the job made by the tag, click "Build Now"   -    Note that Jenkins  still  can't find the tag  even though it exists.       
 

   

[JIRA] (JENKINS-58016) Move Parsing to Plugin Management CLI from Library

2019-06-27 Thread natasha.st...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa updated  JENKINS-58016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This was done in Phase 1 coding.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58016  
 
 
  Move Parsing to Plugin Management CLI from Library
 

  
 
 
 
 

 
Change By: 
 Natasha Stopa  
 
 
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.200036.1560455413000.10965.1561657260318%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58016) Move Parsing to Plugin Management CLI from Library

2019-06-27 Thread natasha.st...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa updated  JENKINS-58016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58016  
 
 
  Move Parsing to Plugin Management CLI from Library
 

  
 
 
 
 

 
Change By: 
 Natasha Stopa  
 
 
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.200036.1560455413000.10964.1561657260305%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58016) Move Parsing to Plugin Management CLI from Library

2019-06-27 Thread natasha.st...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natasha Stopa started work on  JENKINS-58016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Natasha Stopa  
 
 
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.200036.1560455413000.10962.1561657200185%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45455) Restarting stages

2019-06-27 Thread varuag.chha...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gaurav Chhabra updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45455  
 
 
  Restarting stages   
 

  
 
 
 
 

 
Change By: 
 Gaurav Chhabra  
 
 
Comment: 
 Thanks for the response [~bdevcich]. Hardware dependency can definitely be one reason but will tying a job to a slave also _ensure_ that subsequent builds will use the same workspace which was used by last failed build?  
 

  
 
 
 
 

 
 
 

 
 
 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.183623.1499805325000.10853.1561657083492%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users

2019-06-27 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman assigned an issue to Liam Newman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53752  
 
 
  Block PRs from forks from untrusted users   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Assignee: 
 rsandell Liam Newman  
 

  
 
 
 
 

 
 
 

 
 
 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.194259.1537809356000.10845.1561657020542%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57856) subversion list branch/tags not working with release plugin

2019-06-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: subversion list branch/tags not working with release plugin   
 

  
 
 
 
 

 
 I do not think so. The plugin is up for adoption, and eventually somebody will take the ownership. There is also https://jenkins.io/projects/gsoc/2019/artifact-promotion-plugin-for-jenkins-pipeline/ which may eventually lead to a merger of Release Plugin and Promoted Builds, but it is a moon shot ATM.   
 

  
 
 
 
 

 
 
 

 
 
 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.199815.1559723995000.10836.1561655580108%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58048) P4 error - No open file stream in ClientSystemFileCommands.writeFile()

2019-06-27 Thread er...@piap.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Blom commented on  JENKINS-58048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4 error - No open file stream in ClientSystemFileCommands.writeFile()   
 

  
 
 
 
 

 
 I also encountered this problem today. We are running P4 Plugin 1.10.0 on Jenkins 2.164.3. Downgrading to 1.9.7 fixed the 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.200069.1560779623000.10830.1561655340248%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException

2019-06-27 Thread sverre....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sverre Moe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58130  
 
 
  JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException   
 

  
 
 
 
 

 
Change By: 
 Sverre Moe  
 
 
Component/s: 
 coverity-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.200175.1561064567000.10825.1561654200389%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException

2019-06-27 Thread sverre....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sverre Moe commented on  JENKINS-58130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException   
 

  
 
 
 
 

 
 I changed the component to synopsys-coverity-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.200175.1561064567000.10827.1561654200421%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException

2019-06-27 Thread sverre....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sverre Moe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58130  
 
 
  JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException   
 

  
 
 
 
 

 
Change By: 
 Sverre Moe  
 
 
Component/s: 
 synopsys-coverity-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.200175.1561064567000.10822.1561654200355%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException

2019-06-27 Thread sverre....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sverre Moe commented on  JENKINS-58130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException   
 

  
 
 
 
 

 
 It would seem the new Coverity Plugin has similar shortcomings running on Jenkins with Java 11. 1) Error injecting constructor, java.lang.NoClassDefFoundError: javax/xml/ws/WebServiceException at com.synopsys.integration.jenkins.coverity.extensions.wrap.CoverityEnvironmentWrapper$DescriptorImpl.(CoverityEnvironmen tWrapper.java:169)  
 

  
 
 
 
 

 
 
 

 
 
 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.200175.1561064567000.10818.1561654080127%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException

2019-06-27 Thread sverre....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sverre Moe commented on  JENKINS-58130  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException   
 

  
 
 
 
 

 
 Thanks. I wasn't aware of that. I guess then this is a no issue. Will try the new plugin and see if it is running fine with Java 11.  
 

  
 
 
 
 

 
 
 

 
 
 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.200175.1561064567000.10815.1561653780185%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"

2019-06-27 Thread iss...@aol.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Isaac Cohen commented on  JENKINS-57351  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for making Jenkins a "GitHub App"   
 

  
 
 
 
 

 
 This would definitely be very helpful. As a GitHubber, I can tell you that this is the #1 challenge of my customers when integrating Jenkins with GitHub. Another huge benefit of GitHub Apps is that they are not tied to a specific user but rather to the Organization which means you don't need to create a "machine-user" with full access to the entire Organization. Happy to provide more context on this one!  
 

  
 
 
 
 

 
 
 

 
 
 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.199127.1557217283000.10811.1561652580216%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source

2019-06-27 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman assigned an issue to Liam Newman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58172  
 
 
  Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Assignee: 
 Liam Newman  
 

  
 
 
 
 

 
 
 

 
 
 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.200223.1561408065000.10804.1561650600385%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source

2019-06-27 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-58172  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source   
 

  
 
 
 
 

 
 Ethan Diamond  Please take a look at https://github.com/jenkinsci/github-branch-source-plugin/pull/229 .  Try this patched hpi to see if fixes you issue: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.4-rc850.6b329ab1a13f/  
 

  
 
 
 
 

 
 
 

 
 
 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.200223.1561408065000.10802.1561650600358%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58240) Plugins should be able to provide onBlur for codemirror textarea

2019-06-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-58240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugins should be able to provide onBlur for codemirror textarea   
 

  
 
 
 
 

 
 Workaround example: https://github.com/jenkinsci/jenkins/pull/4046#issuecomment-497481088  
 

  
 
 
 
 

 
 
 

 
 
 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.200302.1561649246000.10792.1561649340077%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58240) Plugins should be able to provide onBlur for codemirror textarea

2019-06-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58240  
 
 
  Plugins should be able to provide onBlur for codemirror textarea   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-06-27 15:27  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Placeholder for https://github.com/jenkinsci/jenkins/pull/4046 Currently, plugins cannot cleanly provide a custom onBlur handler for their codemirror textareas, because it is being overridden in core. This has been the case since 4e48eaa, but it does not look like that side-effect has been intentional. (Plugins could work around this in a hackish way, by adding })// at the end of their codemirror-config.)    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[JIRA] (JENKINS-55647) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable

2019-06-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55647  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable   
 

  
 
 
 
 

 
 I am coinverting it to the Core issue for better error handling and diagnostics. Whatever is the failing plugin, Jenkins should be robust against such issues.  
 

  
 
 
 
 

 
 
 

 
 
 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.196824.1547723815000.10789.1561648860232%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55647) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable

2019-06-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55647  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable   
 

  
 
 
 
 

 
 The core code has not been edited for years. It looks like some of the implementations improperly defines the Describable generic., but I cannot pin point to the failing plugin. It is likely a plugin with a really old core dependency. Somebody could add some diagnostics to the core. to track down failing descriptors in the rebuild() call. It could be logging on FIEST level or just runtime exception handler      
 

  
 
 
 
 

 
 
 

 
 
 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.196824.1547723815000.10781.1561648800551%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55647) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable

2019-06-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55647  
 
 
  java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 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.196824.1547723815000.10786.1561648800607%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55647) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable

2019-06-27 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55647  
 
 
  java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 core  
 
 
Component/s: 
 _unsorted  
 

  
 
 
 
 

 
 
 

 
 
 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.196824.1547723815000.10784.1561648800584%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55647) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable

2019-06-27 Thread siphomang...@outlook.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sipho mangena commented on  JENKINS-55647  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable   
 

  
 
 
 
 

 
 Got the same issue after upgrading to 1.176.1 using an existing config.xml.  
 

  
 
 
 
 

 
 
 

 
 
 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.196824.1547723815000.10757.1561645740592%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57741) M1-Support regional days

2019-06-27 Thread jxpea...@godaddy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Pearce resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57741  
 
 
  M1-Support regional days
 

  
 
 
 
 

 
Change By: 
 Jeff Pearce  
 
 
Status: 
 In Progress 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.199686.1559142382000.10751.1561641600404%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57742) Add presets for popular holidays

2019-06-27 Thread jxpea...@godaddy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Pearce closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57742  
 
 
  Add presets for popular holidays   
 

  
 
 
 
 

 
Change By: 
 Jeff Pearce  
 
 
Status: 
 In Progress 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.199687.1559142401000.10753.1561641600433%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57745) Rewrite time range config in React

2019-06-27 Thread jxpea...@godaddy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Pearce closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57745  
 
 
  Rewrite time range config in React   
 

  
 
 
 
 

 
Change By: 
 Jeff Pearce  
 
 
Status: 
 In Progress 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.199690.1559142496000.10755.1561641600457%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57737) Publish blog post

2019-06-27 Thread jxpea...@godaddy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Pearce started work on  JENKINS-57737  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jeff Pearce  
 
 
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.199681.1559138155000.10747.1561641420131%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline

2019-06-27 Thread zdmer...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Merlin commented on  JENKINS-53162  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blueocean support for visualizing stages in parallel block in scripted pipeline   
 

  
 
 
 
 

 
 Thanks for your input Jake.    
 

  
 
 
 
 

 
 
 

 
 
 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.193173.1534855202000.10683.1561641301339%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak edited a comment on  JENKINS-52005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
  {code:java}node {stage("successful"){echo "successful stage"}stage("unstable"){catchError(buildResult: 'SUCCESS', stageResult: 'UNSTABLE'){sh "gooo version"}}stage("continue working"){echo "continue working"}}{code}  I also have this is issue.Jenkins v2.164.3 (Basic Steps 2.18)  already installer doesn't work if I update Basic Steps but when I was testing on new spiup Jenkins with the same version 2.164.3 it is work  !Screen Shot 2019-06-27 at 4.02.19 PM.png|thumbnail!  !Screen Shot 2019-06-27 at 4.02.56 PM.png|thumbnail!
 

  
 
 
 
 

 
 
 

 
 
 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.191506.1529326312000.10677.1561640820499%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52005  
 
 
  catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 
 
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.191506.1529326312000.10679.1561640820524%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52005  
 
 
  catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
Change By: 
 Alexandr Semak  
 
 
Attachment: 
 Screen Shot 2019-06-27 at 4.02.19 PM.png  
 
 
Attachment: 
 Screen Shot 2019-06-27 at 4.02.56 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 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.191506.1529326312000.10669.1561640760335%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred

2019-06-27 Thread lividfa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandr Semak commented on  JENKINS-52005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: catchError should give a visual hint in which stage the error occurred   
 

  
 
 
 
 

 
 

 

node {
stage("successful"){
echo "successful stage"
}
stage("unstable"){
catchError(buildResult: 'SUCCESS', stageResult: 'UNSTABLE'){
sh "gooo version"
}
}
stage("continue working"){
echo "continue working"
}
}
 

 I also have this is issue. Jenkins v2.164.3 already installer doesn't work if I update Basic Steps but when I was testing on new spiup Jenkins with the same version 2.164.3 it is 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.191506.1529326312000.10671.1561640760361%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58118) Prepare demo for coding phase I

2019-06-27 Thread jxpea...@godaddy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Pearce closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58118  
 
 
  Prepare demo for coding phase I   
 

  
 
 
 
 

 
Change By: 
 Jeff Pearce  
 
 
Status: 
 In Progress 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.200163.1561038166000.10665.1561640400657%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51202) choiceParam not listed in JobDSL API viewer

2019-06-27 Thread roman.donche...@intel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Donchenko reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I think there is still a bug here. There is a non-dynamic version of choiceParam (https://github.com/jenkinsci/job-dsl-plugin/blob/job-dsl-1.74/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/BuildParametersContext.groovy#L86), and that one is not visible in the API viewer. Compare it with, for example, booleanParam, for which both dynamic and non-dynamic versions are shown.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51202  
 
 
  choiceParam not listed in JobDSL API viewer   
 

  
 
 
 
 

 
Change By: 
 Roman Donchenko  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-52208) Fix FindBugs violations

2019-06-27 Thread bmat...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 CloudBees Foundation Security commented on  JENKINS-52208  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fix FindBugs violations   
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 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.191968.1530092941000.10660.1561638661173%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart

2019-06-27 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57795  
 
 
  Orphaned EC2 instances after Jenkins restart   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 
 
Environment: 
 Jenkins ver. 2.176.1ec2 plugin 1.43, 1.44  
 

  
 
 
 
 

 
 
 

 
 
 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.199745.1559315049000.10656.1561638300177%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository

2019-06-27 Thread alexeyj...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksei Pushnov commented on  JENKINS-43749  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support multiple Jenkinsfiles from the same repository   
 

  
 
 
 
 

 
 This feature would allow to ease up configuration on many environments.  
 

  
 
 
 
 

 
 
 

 
 
 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.181165.1492753177000.10557.1561638062094%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57856) subversion list branch/tags not working with release plugin

2019-06-27 Thread 4rch...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arch Loy commented on  JENKINS-57856  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: subversion list branch/tags not working with release plugin   
 

  
 
 
 
 

 
 Understand. Thanks for reply Is the plugin dead ?  
 

  
 
 
 
 

 
 
 

 
 
 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.199815.1559723995000.10555.1561637820162%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart

2019-06-27 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski commented on  JENKINS-57795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Orphaned EC2 instances after Jenkins restart   
 

  
 
 
 
 

 
 I double checked this. If I'm at cap = 1 with 1 orphaned instance and increase the cap to 2 then the plugin will spawn a new instance. If I'm at cap = 2 with 2 orphaned instances and terminate one of the instances manually then the plugin will reconnect the other instance  
 

  
 
 
 
 

 
 
 

 
 
 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.199745.1559315049000.10552.1561637520111%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57719) Pegdown plugin not supported by JCasC

2019-06-27 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-57719  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57719  
 
 
  Pegdown plugin not supported by JCasC   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.199662.1559061709000.10549.1561636140342%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57719) Pegdown plugin not supported by JCasC

2019-06-27 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-57719  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Works correctly with the configuration as code plugin 1.21  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57719  
 
 
  Pegdown plugin not supported by JCasC   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
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.199662.1559061709000.10547.1561636140223%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57720) Legacy pipeline library definition not supported by JCasC

2019-06-27 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-57720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57720  
 
 
  Legacy pipeline library definition not supported by JCasC   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
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.199663.1559067514000.10545.1561635960257%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart

2019-06-27 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski commented on  JENKINS-57795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Orphaned EC2 instances after Jenkins restart   
 

  
 
 
 
 

 
 Above looks like maybe there is some "off by one" error, when the plugin won't attempt to re-connect instances if it's at instance cap  
 

  
 
 
 
 

 
 
 

 
 
 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.199745.1559315049000.10543.1561635660112%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart

2019-06-27 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski commented on  JENKINS-57795  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Orphaned EC2 instances after Jenkins restart   
 

  
 
 
 
 

 
 I'm now getting this situation with instance cap = 2. I have two matching instances on EC2, both are active. Plugin is looping with above message, with no agents available for the builds. Now when I terminated one of the instances an interesting thing happened. Jenkins was able to pick up the other instance and reconnect it  

 
SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Cannot provision - no capacity for instances: 0

Jun 27, 2019 11:35:07 AM WARNING hudson.plugins.ec2.EC2Cloud provision

Can't raise nodes for SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}

Jun 27, 2019 11:35:16 AM INFO hudson.plugins.ec2.EC2Cloud provision

SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Attempting to provision slave needed by excess workload of 1 units

Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo

SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Considering launching

Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice

AMI had xvda

Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate setupRootDevice

{DeleteOnTermination: true,SnapshotId: snap-0b70f104d64ae4a48,VolumeSize: 8,VolumeType: gp2,Encrypted: false,}

Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo

SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate

Jun 27, 2019 11:35:17 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo

SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. Looking for existing instances with describe-instance: {Filters: SNAP

Jun 27, 2019 11:35:18 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo

SlaveTemplate{ami='ami-0efbb291c6e8cc847', labels='docker docker-bakery'}. checkInstance: i-0e454aea630ccb88f. true - Instance is not connected to Jenkins
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
 

[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11

2019-06-27 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-57341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57341  
 
 
  Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
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.199116.1557144976000.10534.1561634460590%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11

2019-06-27 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57341  
 
 
  Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.199116.1557144976000.10537.1561634460629%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


  1   2   >