[JIRA] (JENKINS-48231) Pickup TestNG Junit report under target/surefire-reports/junitreports

2018-11-01 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran updated  JENKINS-48231  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48231  
 
 
  Pickup TestNG Junit report under target/surefire-reports/junitreports   
 

  
 
 
 
 

 
Change By: 
 dan tran  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48231) Pickup TestNG Junit report under target/surefire-reports/junitreports

2018-11-01 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran stopped work on  JENKINS-48231  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 dan tran  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48231) Pickup TestNG Junit report under target/surefire-reports/junitreports

2018-11-01 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran updated  JENKINS-48231  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48231  
 
 
  Pickup TestNG Junit report under target/surefire-reports/junitreports   
 

  
 
 
 
 

 
Change By: 
 dan tran  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-48231) Pickup TestNG Junit report under target/surefire-reports/junitreports

2018-11-01 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran commented on  JENKINS-48231  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pickup TestNG Junit report under target/surefire-reports/junitreports   
 

  
 
 
 
 

 
 testng now also generates a single junit report TEST-xxx.xml  under surefire-reports directory.  so it works for me  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"

2018-11-01 Thread martin.moess...@coop.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Mössner commented on  JENKINS-54333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Projects are triggered twice by "build with parameters"   
 

  
 
 
 
 

 
 Yes, 2.147 works and beginning from 2.148 Projects triggered twice with Internet Explorer 11 and Edge. With Google Chrome it works.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2018-11-01 Thread eric.blackw...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Blackwell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54418  
 
 
  Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
Change By: 
 Eric Blackwell  
 

  
 
 
 
 

 
 I have a jenkins job that uses packer to generate my GCE images on demand, so that we can maintain our build and dev environments in version control. When building this way, we can set an "image_family" parameter to a custom string, and name the image with version string. It would be great if, in the configuration there was an option to select the image via 'OS Family', and always use the latest version. This way, we don't have to constantly adjust the image used, and it can be picked up dynamically.   *EDIT*After a bit of research I found that what you would want to use is  compute.Images.GetFromFamily. I do not know java very well, and I wouldn't know where to begin or I would it myself. But I think if you just make the current "image name" and add "os family" parameter to the form, and make them an OR or use radio boxes, then take the input from os family, it could work automatically, as the documentation says it will already return the latest.Here is the documentation:https://developers.google.com/resources/api-libraries/documentation/compute/v1/java/latest/com/google/api/services/compute/Compute.Images.GetFromFamily.html Thanks!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

 

[JIRA] (JENKINS-54418) Ability to select images based on OS_FAMILY and select lastest version

2018-11-01 Thread eric.blackw...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Blackwell created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54418  
 
 
  Ability to select images based on OS_FAMILY and select lastest version   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Evan Brown  
 
 
Components: 
 google-compute-engine-plugin  
 
 
Created: 
 2018-11-02 05:34  
 
 
Environment: 
 Jenkins with GCE plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Eric Blackwell  
 

  
 
 
 
 

 
 I have a jenkins job that uses packer to generate my GCE images on demand, so that we can maintain our build and dev environments in version control. When building this way, we can set an "image_family" parameter to a custom string, and name the image with version string.   It would be great if, in the configuration there was an option to select the image via 'OS Family', and always use the latest version. This way, we don't have to constantly adjust the image used, and it can be picked up dynamically.  Thanks!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

   

[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors

2018-11-01 Thread mike.scho...@preh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Scholze commented on  JENKINS-33412  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors   
 

  
 
 
 
 

 
 It is fixed with 2.138.2! https://jenkins.io/changelog-stable/  Update Winstone-Jetty from 4.4 to 5.0 to fix HTTP/2 support and threading problems on hosts with 30+ cores. (issue 53239, issue 52804, issue 51136, issue 52358)  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54417) jenkins 升级到2.138.2, 登陆时报错

2018-11-01 Thread guochaorong...@163.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 chaorong guo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54417  
 
 
  jenkins 升级到2.138.2, 登陆时报错   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Beck  
 
 
Components: 
 login-theme-plugin  
 
 
Created: 
 2018-11-02 04:58  
 
 
Environment: 
 linux centos 6 , resin部署jenkins  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 chaorong guo  
 

  
 
 
 
 

 
 Stack trace org.apache.commons.jelly.JellyException: Could not parse Jelly script : jar:file:/disk6/ynote/jenkins/resin-4.0.48/webapps/jenkins/WEB-INF/lib/jenkins-core-2.138.2.jar!/jenkins/model/Jenkins/login.jelly at   ... 106 more  [18-11-02 12:29:01.573] {Handling GET /jenkins/login from 61.135.255.83 : resin-port-18098-50} Underlying exception: org.apache.commons.jelly.JellyException: Could not parse Jelly script : http://www.w3.org/2000/svg/svg.jellytag     org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java:529) at org.kohsuke.stapler.jelly.JellyClassTearOff.parseScript(JellyClassTearOff.java:56) at org.kohsuke.stapler.jelly.JellyClassTearOff.parseScript(JellyClassTearOff.java:47) at org.kohsuke.stapler.AbstractTearOff.resolveScript(AbstractTearOff.java:91) at org.kohsuke.stapler.jelly.JellyClassTearOff.resolveScript(JellyClassTearOff.java:94) at org.kohsuke.stapler.jelly.JellyClassTearOff.resolveScript(JellyClassTearOff.java:47) at org.kohsuke.stapler.AbstractTearOff.loadScript(AbstractTearOff.java:97) at org.kohsuke.stapler.CachingScriptLoader$1.load(CachingScriptLoader.java:31) at org.kohsuke.stapler.CachingScriptLoader$1.load(CachingScriptLoader.java:28) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCach

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2018-11-01 Thread sar...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Huang Echo commented on  JENKINS-16163  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when sending post build emails - all triggers appear to be impacted   
 

  
 
 
 
 

 
 I had created a new issue,  here: https://issues.jenkins-ci.org/browse/JENKINS-54363   
 

 
 
Email Extension Plugin  
 

 
 Version: 2.63  Win10 X86 Jenkin version: 2.121.2  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-01 Thread dcher...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitry Chernivetsky commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 I can confirm this bug. All PR branches are failing to build. Environment: Bitbucket server  v4.12.0 Latest jenkins with latest plugins,  Bitbucket branch source plugin 2.2.14 Multibranch pipeline is autocreated from Bitbucket team/project. Nothing really special about configuration. Screenshot attached.   
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-01 Thread dcher...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitry Chernivetsky updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54401  
 
 
  java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
Change By: 
 Dmitry Chernivetsky  
 
 
Attachment: 
 image-2018-11-02-00-43-19-214.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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54416) Configure Systems Page Showing Oops Page. Unable to Save

2018-11-01 Thread agnibha.b...@gupshup.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Agnibha Bose created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54416  
 
 
  Configure Systems Page Showing Oops Page. Unable to Save   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-11-02 04:20  
 
 
Environment: 
 Jenkins Version: org.jenkins-ci.main:jenkins-war:2.138.2  Plugins:  ace-editor 1.1 true  android-emulator 3.0 true  ansicolor 0.5.2 true  ant 1.9 true  antisamy-markup-formatter 1.5 true  apache-httpcomponents-client-4-api 4.5.5-3.0 true  artifactory 2.16.2 true  authentication-tokens 1.3 true  aws-credentials 1.23 true  aws-java-sdk 1.11.403 true  azure-commons 0.2.8 true  azure-credentials 1.6.0 true  azure-vm-agents 0.7.4 true  blueocean 1.9.0 true  blueocean-autofavorite 1.2.2 true  blueocean-bitbucket-pipeline 1.9.0 true  blueocean-commons 1.9.0 true  blueocean-config 1.9.0 true  blueocean-core-js 1.9.0 true  blueocean-dashboard 1.9.0 true  blueocean-display-url 2.2.0 true  blueocean-events 1.9.0 true  blueocean-git-pipeline 1.9.0 true  blueocean-github-pipeline 1.9.0 true  blueocean-i18n 1.9.0 true  blueocean-jira 1.9.0 true  blueocean-jwt 1.9.0 true  blueocean-personalization 1.9.0 true  blueocean-pipeline-api-impl 1.9.0 true  blueocean-pipeline-editor 1.9.0 true  blueocean-pipeline-scm-api 1.9.0 true  blueocean-rest 1.9.0 true  blueocean-rest-impl 1.9.0 true  blueocean-web 1.9.0 true  bouncycastle-api 2.17 true  branch-api 2.0.20 true  build-name-setter 1.6.9 true  build-timeout 1.19 true  cloud-stats 0.19 true  cloudbees-bitbucket-branch-source 2.2.14 true  cloudbees-folder 6.6 true  command-launcher 1.2 true  conditional-buildstep 1.3.6 true  config-file-provider 3.4 true  copyartifact 1.41 true  credentials 2.1.18 true  credentials-binding 1.17 true  cvs 2.14 true  display-url-api 2.2.0 true  docker-build-publish 1.3.2 true  docker-commons 1.13 true  docker-workflow 1.17 true  durable-task 1.26 true  ec2 1.41 true  embeddable-build-status 1.9 true  external-monitor-job 1.7 true  favorite 2.3.1 true  ghprb 1.42.0 true  git 3.9.1 true  git-client 2.7.3 true  git-server 1.7 true  github 1.29.3 true  github-api 1.92 true  github-branch-source 2.4.1 true  github-organization-folder 1.6 true  gitlab-plugin 1.5.10 true  gradle 1.29 true  greenballs 1.15 true  handlebars 1.1.1 true  handy-uri-templates-2-api 2.1.6-1.0 true  hockeyapp 1.3.3 true  htmlpublisher 1.17 true  ivy 1.28 true  jackson2-api 2.8.11.3 true  javadoc 1.4 true  jdk-tool 1.1 true  jenkins-design-language 1.9.0 true  jira 3.0.4 true  job-dsl 1.70 true  jobConfigHistory 2.18.3 true  jquery 1.12.4-0 true  jquery-detached 1.2.1 true  jsch 0.1.54.2 true  junit 1.26.1 true  ldap 1.20 true  lockable-resources 2.3 true 

[JIRA] (JENKINS-54415) jep-200 issue w/ matrix reloaded plugin

2018-11-01 Thread mike...@zzzcomputing.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mike bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54415  
 
 
  jep-200 issue w/ matrix reloaded plugin   
 

  
 
 
 
 

 
Change By: 
 mike bayer  
 
 
Labels: 
 JEP-200  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54415) jep-200 issue w/ matrix reloaded plugin

2018-11-01 Thread mike...@zzzcomputing.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mike bayer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54415  
 
 
  jep-200 issue w/ matrix reloaded plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Praqma Support  
 
 
Components: 
 matrix-reloaded-plugin  
 
 
Created: 
 2018-11-02 04:02  
 
 
Environment: 
 jenkins 2.138.2  latest version of the matrix plugin (1.30 I think) and latest matrix reloaded plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 mike bayer  
 

  
 
 
 
 

 
 getting one of those "failed to serialize" exceptions that seem to be reported everywhere re: the jep-200 change, with respect to the matrix reloaded plugin.  this plugin is not listed at https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200, however when I uninstalled it, all the issues  was having went away.   the stack trace is below, and along with it, a successful matrix build fails to set itself as "successful" in some way, e.g. the junit.xml doesn't get written and it the lastSuccessfulBuild symlink seems to get reset, I don't know how all these things work but that's the handwavy summary.   SEVERE: Failed to save build record java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixRun at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:2015) at hudson.model.Run.execute(Run.java:1876) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixRun at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converte

[JIRA] (JENKINS-54413) DocLinks Uses HTML Frames

2018-11-01 Thread hube...@verizon.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Huber closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Problem is in Doxygen output that is being published.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54413  
 
 
  DocLinks Uses HTML Frames   
 

  
 
 
 
 

 
Change By: 
 Mike Huber  
 
 
Status: 
 Open Closed  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54383) consider adding bitbucket-oauth and github-oauth to essentials

2018-11-01 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy commented on  JENKINS-54383  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: consider adding bitbucket-oauth and github-oauth to essentials   
 

  
 
 
 
 

 
 I think this might be better suited for a "bitbucket" flavor Baptiste Mathus, that may be a way we can incorporate more plugins like this which I've never used, in a manner that doesn't bloat the other flavors. As an added bonus, we might be able to find somebody who actually uses bitbucket to maintain that flavor   
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54384) consider adding pipeline-maven to essentials

2018-11-01 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy commented on  JENKINS-54384  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: consider adding pipeline-maven to essentials   
 

  
 
 
 
 

 
 My personal opinion of the pipeline-maven plugin is very very low unfortunately. I've always thought it makes more sense as a shared library, and is not worth the security vulnerability attack surface area it adds to Jenkins. With regards to the config-file-provider, that is pulled in as a transitive dependency for what it's worth.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54414) NullPointerException when packaging IPA

2018-11-01 Thread tianliang.bl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 L welkiner created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54414  
 
 
  NullPointerException when packaging IPA   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 xcode-plugin  
 
 
Created: 
 2018-11-02 02:42  
 
 
Environment: 
 XCode plugin 2.08  Jenkins 2.60  Xcode 9.3  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 L welkiner  
 

  
 
 
 
 

 
 [iOS_HETTestTool] $ /usr/bin/xcodebuild -exportArchive -archivePath /Users/Admin/Documents/workspace/iOS_HETTestTool/build/Release-iphoneos/HETTestTool.xcarchive -exportPath /Users/Admin/Documents/Output/HETTestTool -exportOptionsPlist /Users/Admin/Documents/Output/HETTestTool/enterprise2F46R5UK38ExportOptions.plist 2018-11-02 10:30:16.324 xcodebuild[9310:33474424] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/36/v_wn9hdd6g157hxt_dhkf6swgn/T/HETTestTool_2018-11-02_10-30-16.323.xcdistributionlogs'. Exported HETTestTool.xcarchive to: /Users/Admin/Documents/Output/HETTestTool 
 
 
 
EXPORT SUCCEEDED ** 
  
 Archiving dSYM ERROR: Build step failed with exception java.lang.NullPointerException at java.util.ArrayList.addAll(ArrayList.java:577) at au.com.rayh.XCodeBuilder._perform(XCodeBuilder.java:1980) at au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:1028) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735) at hudson.model.Build$BuildExecution.b

[JIRA] (JENKINS-54413) DocLinks Uses HTML Frames

2018-11-01 Thread hube...@verizon.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Huber created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54413  
 
 
  DocLinks Uses HTML Frames   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 sogabe  
 
 
Components: 
 doclinks-plugin  
 
 
Created: 
 2018-11-02 02:39  
 
 
Environment: 
 System Properties  awt.toolkit sun.awt.X11.XToolkit  executable-war /apps/jenkins/war/jenkins.war-2.70  file.encoding UTF-8  file.encoding.pkg sun.io  file.separator /  java.awt.graphicsenv sun.awt.X11GraphicsEnvironment  java.awt.headless true  java.awt.printerjob sun.print.PSPrinterJob  java.class.path /apps/jenkins/war/jenkins.war  java.class.version 52.0  java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/endorsed  java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/ext:/usr/java/packages/lib/ext  java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre  java.io.tmpdir /apps/jenkins/tmp  java.library.path :/usr/local/lib:/usr/lib:/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib  java.runtime.name OpenJDK Runtime Environment  java.runtime.version 1.8.0_161-b14  java.specification.name Java Platform API Specification  java.specification.vendor Oracle Corporation  java.specification.version 1.8  java.vendor Oracle Corporation  java.vendor.url http://java.oracle.com/  java.vendor.url.bug http://bugreport.sun.com/bugreport/  java.version 1.8.0_161  java.vm.info mixed mode  java.vm.name OpenJDK 64-Bit Server VM  java.vm.specification.name Java Virtual Machine Specification  java.vm.specification.vendor Oracle Corporation  java.vm.specification.version 1.8  java.vm.vendor Oracle Corporation  java.vm.version 25.161-b14  JENKINS_HOME /apps/jenkins  jetty.git.hash d5fc0523cfa96bfebfbda19606cad384d772f04c  jna.loaded true  jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/mysql  jnidispatch.path /apps/jenkins/tmp/jna-101011358/jna1483037073107752018.tmp  line.separator  mail.smtp.sendpartial true  mail.smtps.sendpartial true  os.arch amd64  os.name Linux  os.version 3.10.0-693.21.1.el7.x86_64  path.separator :  sun.arch.data.model 64  sun.boot.class.path /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/jf

[JIRA] (JENKINS-54412) Testng Plugin should have capability to save the reports in

2018-11-01 Thread ratsa...@adobe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rati Saxena created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54412  
 
 
  Testng Plugin should have capability to save the reports in
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nalin Makar  
 
 
Components: 
 testng-plugin  
 
 
Created: 
 2018-11-02 01:49  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Rati Saxena  
 

  
 
 
 
 

 
 I am running my testing jobs on Jenkins which publish testng results using the testng-plugin . The daily reports The testng-results.xml are by default stored in the 

 

/jobs//builds//testng/testng-results.xml
 

 Now i want to change the BUILD URL directory so that the builds are saved into the directory, something like this - 

 

/jobs//builds///testng/testng-results.xml
 

 where the  is declared in each job . Since the PARAMETER is defined in each job , I cannot change the build workspace globally for Jenkins. After looking at the github code ,  I see that if I could somehow pass the value of "testngDir" into the plugin then my problem should be resolved  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-54411) Configure page show Oops page (/configure)

2018-11-01 Thread andrew.paul.g...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Gray updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54411  
 
 
  Configure page show Oops page (/configure)   
 

  
 
 
 
 

 
Change By: 
 Andrew Gray  
 

  
 
 
 
 

 
 Upgrading the config-file-provider plugin from 3.3 to 3.4 causes the /configure page to  through  throw  a stacktrace.Downgrading back to 3.3 resolves 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54411) Configure page show Oops page (/configure)

2018-11-01 Thread andrew.paul.g...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Gray created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54411  
 
 
  Configure page show Oops page (/configure)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Dominik Bartholdi  
 
 
Components: 
 config-file-provider-plugin  
 
 
Created: 
 2018-11-02 01:34  
 
 
Environment: 
 Windows 2012; Jenkins 138.2 config-file-provider v3.4  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Andrew Gray  
 

  
 
 
 
 

 
 Upgrading the config-file-provider plugin from 3.3 to 3.4 causes the /configure page to through a stacktrace. Downgrading back to 3.3 resolves the issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[JIRA] (JENKINS-54410) Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic

2018-11-01 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz started work on  JENKINS-54410  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54410) Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic

2018-11-01 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-54410  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic   
 

  
 
 
 
 

 
 PR up.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54410) Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic

2018-11-01 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated  JENKINS-54410  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54410  
 
 
  Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54410) Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic

2018-11-01 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54410  
 
 
  Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Karl Shultz  
 
 
Components: 
 blueocean-acceptance-test  
 
 
Created: 
 2018-11-02 01:00  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Karl Shultz  
 

  
 
 
 
 

 
 Summary The Blue Ocean Acceptance Tests, when run against a version of core >= 2.128, will fail to login correctly, causing many tests to time out. That's because the new button says "Submit" and the old button says "log in". The exact line where we time out is this one. We haven't seen this until now, because the "default" in Blue Ocean's ATH runner script, is set to 2.121.1.  A simple if/else to check for the style of login, and act accordingly, should do the trick.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number

2018-11-01 Thread 895943...@qq.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liu Wang commented on  JENKINS-54181  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number   
 

  
 
 
 
 

 
 Artem Fedorov Thanks for your help, I will try to update the plugin when v3.13 is released.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54233) Pipeline Script textarea missing

2018-11-01 Thread andrew.paul.g...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Gray updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54233  
 
 
  Pipeline Script textarea missing   
 

  
 
 
 
 

 
Change By: 
 Andrew Gray  
 
 
Component/s: 
 workflow-cps-plugin  
 
 
Component/s: 
 groovy-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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53176) How to safely rotate master.key and hudson.util.Secret?

2018-11-01 Thread block....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon B commented on  JENKINS-53176  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: How to safely rotate master.key and hudson.util.Secret?   
 

  
 
 
 
 

 
 Could someone at CloudBees please comment on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48850) Random java.io.IOException: Unexpected termination of the channel

2018-11-01 Thread federi...@al.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Naum commented on  JENKINS-48850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Random java.io.IOException: Unexpected termination of the channel   
 

  
 
 
 
 

 
 Hi Jeff, I agree with you that the logs are not helpful at all, I tried following the remoting debug strategies to find what was happening but I could not find the root cause. Also, I put a layer on top and started monitoring the machines (network/CPU/RAM/ I/O ) to see If I could correlate that to this Unexpected termination, but again I could not anything. In my experience, the only thing that alleviated this situation is to run things serially, when my multi-build stage run in parallel is when I started to see this issue more frequently. I'm giving the Kafka-agent plugin a go, and that seems to improve. (my understanding is that the agent plugin is a rewritten version of remoting original engine)      
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread sorri...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Morrison commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 Also see this on LTS 2.138.2  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-54186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
 I have a fix for the logspam, but am still working on the testcase (a bit fiddly).   
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54409) It doesn;t like my password

2018-11-01 Thread wherk...@kingtux.me (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wyatt Herkamp created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54409  
 
 
  It doesn;t like my password   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 _unsorted  
 
 
Created: 
 2018-11-01 22:05  
 
 
Environment: 
 18.04 Ubuntu  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Wyatt Herkamp  
 

  
 
 
 
 

 
 Example Password I tried Test500%)) Error https://paste.ee/p/5TuUU  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-54186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
 I suppose the simplest “fix” would just be to log NoStaplerConstructorException at FINE.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-49816) swarm node says connected succesffuly, but master has placed it offline

2018-11-01 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-49816  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: swarm node says connected succesffuly, but master has placed it offline   
 

  
 
 
 
 

 
 I have no idea what's going on here and I haven't seen any other similar reports. Unfortunately there isn't enough information in the logs to figure anything out. It might be possible to figure more out with finer-grained logging but that would make it difficult to sift through it all to find something interesting. As Alex Gray notes it's common enough to be a nuisance but not frequent enough to be a big problem. Without more info there's not much to take action on. I don't know there's much reason to hold this ticket 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-01 Thread onod...@mail.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexey Marin commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 No problem, as soon as I get back to the office in the morning, but I have no idea what "source job configuration trait" is. I take it it's some part of the multibranch pipeline configuration?  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-48850) Random java.io.IOException: Unexpected termination of the channel

2018-11-01 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-48850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Random java.io.IOException: Unexpected termination of the channel   
 

  
 
 
 
 

 
 Unfortunately, I don't have any ideas or suggestions on this one. The logs don't provide any helpful information. It looks like the agent ones pretty much lack anything useful. Commonly Remoting issues involve something in the networking or system environment terminating the connection from outside the process. The trick can be to determine what is doing that. People report a number of different causes, or at least changes that seem to make the problem go away. It can involve issues from the system, network, environment, or hosting / containerization system. I've heard that VM systems are sometimes particularly susceptible. On the other hand, many people are very successful with long-running jobs and connections remain very stable.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread benoit.gue...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 benoit guerin commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 Seems to be resolved by https://github.com/jenkinsci/config-file-provider-plugin/commit/e1073591435f44ceb1fe984673edf1701613639a, on 3.4.1  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors

2018-11-01 Thread skee...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shaun Keenan commented on  JENKINS-33412  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors   
 

  
 
 
 
 

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


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-54186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
 Yes, this is purely a log-spam issue – we catch all exceptions from trying to store step arguments. Jesse's comment sparks some ideas for me.   
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort assigned an issue to Sam Van Oort  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54186  
 
 
  No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Assignee: 
 Sam Van Oort  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors

2018-11-01 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-33412  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors   
 

  
 
 
 
 

 
 As this was not nominated as an LTS candidate, it will not be in 2.138.3 next week. I expect it'll be in the next LTS 2.1xx.1 scheduled for December 5. For reference https://jenkins.io/download/lts/#backporting-process  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

2018-11-01 Thread casey.mother...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Motherway edited a comment on  JENKINS-54366  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing   
 

  
 
 
 
 

 
 It seems like this is probably an issue on the Ansible Tower end.  There is a variable on the workspace in the AT API: {code:java}ask_variables_on_launch{code}It is defaulted to false.  After setting this to true via the API my extra vars are now making it from Jenkins to AT and passing through to the jobs.  This should probably be a bug in AT for changing the default behavior, while there is no option in the UI to set it.The warning in the Jenkins Console Output went away also. Kudos to our amazing IT guy (SD) for figuring this out, and saving the day.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

2018-11-01 Thread casey.mother...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Motherway edited a comment on  JENKINS-54366  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing   
 

  
 
 
 
 

 
 It sees like this is probably an issue on the Ansible Tower end.  There is a variable on the workspace in the AT API: {code:java}ask_variables_on_launch{code}It is defaulted to false.  After setting this to true via the API my extra vars are now making it from Jenkins to AT and passing through to the jobs.  This should probably be a bug in AT for changing the default behavior, while there is no option in the UI to set it. The warning in the Jenkins Console Output went away also.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

2018-11-01 Thread casey.mother...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Motherway edited a comment on  JENKINS-54366  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing   
 

  
 
 
 
 

 
 It  sees  seems  like this is probably an issue on the Ansible Tower end.  There is a variable on the workspace in the AT API: {code:java}ask_variables_on_launch{code}It is defaulted to false.  After setting this to true via the API my extra vars are now making it from Jenkins to AT and passing through to the jobs.  This should probably be a bug in AT for changing the default behavior, while there is no option in the UI to set it.The warning in the Jenkins Console Output went away also.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors

2018-11-01 Thread skee...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shaun Keenan commented on  JENKINS-33412  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors   
 

  
 
 
 
 

 
 Another ping - when will this make it into LTS?  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

2018-11-01 Thread casey.mother...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Motherway edited a comment on  JENKINS-54366  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing   
 

  
 
 
 
 

 
 It sees like this is probably an issue on the Ansible Tower end.  There is a variable on the workspace in the AT API:  {code:java} ask_variables_on_launch {code} It is defaulted to false.  After setting this to true via the API my extra vars are now making it from Jenkins to AT and passing through to the jobs.  This should probably be a bug in AT for changing the default behavior, while there is no option in the UI to set 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

2018-11-01 Thread casey.mother...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Motherway commented on  JENKINS-54366  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing   
 

  
 
 
 
 

 
 It sees like this is probably an issue on the Ansible Tower end.  There is a variable on the workspace in the AT API:  ask_variables_on_launch It is defaulted to false.  After setting this to true via the API my extra vars are now making it from Jenkins to AT and passing through to the jobs.  This should probably be a bug in AT for changing the default behavior, while there is no option in the UI to set 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54186  
 
 
  No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-54186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
 

the only actual impact of this bug is large stack traces in the logs – not actual functional problems
 More or less, yes. There is a bit of a functional problem but you are unlikely to care about the impact. Certainly not worth giving up the critical security fix for.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"

2018-11-01 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-54333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Projects are triggered twice by "build with parameters"   
 

  
 
 
 
 

 
 Could you please clarify that 2.147 works and 2.148 does not? I'm confused because there's nothing in 2.148 that could cause this. https://github.com/jenkinsci/jenkins/compare/jenkins-2.147...jenkins-2.148  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-54186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
 MergeWithGitSCMExtension and GitSCMSourceDefaults deliberately lack descriptors and are not intended to be databound. This is a bug in ArgumentsActionImpl resulting from the fix of JENKINS-54032. I suspect something like 

 

diff --git a/src/main/java/org/jenkinsci/plugins/workflow/cps/actions/ArgumentsActionImpl.java b/src/main/java/org/jenkinsci/plugins/workflow/cps/actions/ArgumentsActionImpl.java
index dd292481..0bacdc36 100644
--- a/src/main/java/org/jenkinsci/plugins/workflow/cps/actions/ArgumentsActionImpl.java
+++ b/src/main/java/org/jenkinsci/plugins/workflow/cps/actions/ArgumentsActionImpl.java
@@ -291,6 +291,9 @@ public class ArgumentsActionImpl extends ArgumentsAction {
 } else if (tempVal instanceof UninstantiatedDescribable) {
 tempVal = ((UninstantiatedDescribable)tempVal).toMap();
 } else if (tempVal instanceof Describable) {  // Raw Describables may not be safe to store, so we should explode it
+if (Jenkins.get().getDescriptor(tempVal.getClass().asSubclass(Describable.class)) == null) {
+return NotStoredReason.UNSERIALIZABLE;
+}
 m = DescribableModel.of(tempVal.getClass());
 tempVal = m.uninstantiate2(o).toMap();
 }
 

 would fix it, but the issue needs to be reproduced in a functional test first.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen

2018-11-01 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-54261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Submit ( go ) on Email Template Testing produces blank screen   
 

  
 
 
 
 

 
 Steve Graham Could you explain in some more detail how this can be reproduced?  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-54186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch

2018-11-01 Thread gun...@grodotzki.co.za (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gunter Grodotzki reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54206  
 
 
  Merged PRs not being removed from multibranch   
 

  
 
 
 
 

 
Change By: 
 Gunter Grodotzki  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Resolved 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54032) ArgumentsActionImpl should protect against storing bizarre step arguments

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Sam Van Oort  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54032  
 
 
  ArgumentsActionImpl should protect against storing bizarre step arguments   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Sam Van Oort  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54186  
 
 
  No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54186  
 
 
  No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 regression  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54372) NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension

2018-11-01 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54372  
 
 
  NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31832) javaposse.jobdsl.dsl.Job is not a suitable parent class for javaposse.jobdsl.dsl.jobs.WorkflowJob (org.jenkinsci.plugins.workflow.job.WorkflowJob does not extend hudson.model.Ab

2018-11-01 Thread frankgenera...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Gen commented on  JENKINS-31832  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: javaposse.jobdsl.dsl.Job is not a suitable parent class for javaposse.jobdsl.dsl.jobs.WorkflowJob (org.jenkinsci.plugins.workflow.job.WorkflowJob does not extend hudson.model.AbstractProject)   
 

  
 
 
 
 

 
 Hello, Will this issue be resolved and released any time soon? We started having builds launched in parallel, even though they should have been queued. Thanks  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54284) Add `@Symbol` to warning parsers

2018-11-01 Thread jeremystuartmarsh...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeremy Marshall closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 merged into plugin warnings-ng  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54284  
 
 
  Add `@Symbol` to warning parsers   
 

  
 
 
 
 

 
Change By: 
 Jeremy Marshall  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54408) docker exec runs as root within docker.image.inside which docker run runs as the jenkins user

2018-11-01 Thread hontv...@flyordie.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 HONTVÁRI Levente created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54408  
 
 
  docker exec runs as root within docker.image.inside which docker run runs as the jenkins user   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2018-11-01 19:54  
 
 
Environment: 
 Jenkins ver. 2.138.2  
 
 
Priority: 
  Major  
 
 
Reporter: 
 HONTVÁRI Levente  
 

  
 
 
 
 

 
 A docker.image.inside block causes Jenkins to run a 'docker run ... cat' command and later a docker exec command. The run command runs as the Jenkins user (specifically with the same uid), while docker exec runs as root. The result is that files created withing the inside block has root owners in the workplace, causing issues in later stages. I would expect the opposite behavior. "docker run ... cat" should run as root, in order to be able to initialize the docker container. Specifically I have to create a user with the same uid as the jenkins user of the agent (otherwise sudo, ssh will not work). On the other hand docker exec, which does the actual build job, should run under the jenkins user uid, so the owner of the newly created files in mounted directories is the jenkins user.  
 

  
 
 
 
 

 
 
 

 
   

[JIRA] (JENKINS-52973) Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2

2018-11-01 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-52973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2   
 

  
 
 
 
 

 
 JENKINS-54406 is a ticket to quayio-plugin BTW  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-51191) hudson.remoting.Channel$CallSiteStackTrace: Remote call to

2018-11-01 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-51191  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hudson.remoting.Channel$CallSiteStackTrace: Remote call to
 

  
 
 
 
 

 
 I'm at a loss to explain this one. I've seen a few other reports where people using pipeline were getting an InterruptedException. I haven't yet seen any indication of what caused it. Maybe an interaction between different plugins. I see timestamps in the agent logs but none in the master. Do these different events and logs match up? My only suggestion is to try and isolate or reproduce the problem somehow.  Have you seen any changes in the behavior or the frequency?  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54407) docker exec fails within docker.image.inside because of empty environment variable name

2018-11-01 Thread hontv...@flyordie.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 HONTVÁRI Levente created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54407  
 
 
  docker exec fails within docker.image.inside because of empty environment variable name   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2018-11-01 19:46  
 
 
Environment: 
 Jenkins ver. 2.138.2  
 
 
Priority: 
  Major  
 
 
Reporter: 
 HONTVÁRI Levente  
 

  
 
 
 
 

 
 There is an environment variable from unknown source which has an empty name. Jenkins would run a docker exec command to execute the content of an sh step within a docker.image.inside block. The docker exec command fails because of the environment variable. I have written a wrapper bash script around the docker command which filters out the empty environment variable name. With this script in place the same Jenkinsfile runs sucessfully. The environment variable does not appear on the global configure system page, neither on the agent page. Its value is 'build'.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

[JIRA] (JENKINS-54406) [JEP-200] Failed to serialize class

2018-11-01 Thread rz...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronnie Zhou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54406  
 
 
  [JEP-200] Failed to serialize class   
 

  
 
 
 
 

 
Change By: 
 Ronnie Zhou  
 

  
 
 
 
 

 
  Job failed with stack trace:{{}}{code:java}FATAL: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild java.lang.UnsupportedOperationException: Refusing to marshal net.sf.json.JSONObject for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.quayio.trigger.PushEventNotification#payload for class org.jenkinsci.plugins.quayio.trigger.PushEventNotification at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) Can you please help us to understand what is causing this and what can be done to come across this errors . I am attaching the console output , support bundle and config.xml of the job to the case {code}{{}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-54406) [JEP-200] Failed to serialize class

2018-11-01 Thread rz...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ronnie Zhou created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54406  
 
 
  [JEP-200] Failed to serialize class   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jean-Christophe Sirot  
 
 
Components: 
 quayio-trigger-plugin  
 
 
Created: 
 2018-11-01 19:41  
 
 
Labels: 
 JEP-200  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Ronnie Zhou  
 

  
 
 
 
 

 
 
 

 
 
 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.

[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-01 Thread nfalc...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 Thanks for detailed report. I'm on leave but i will have a look this monday. Seems from stracktrace the issue happens in PR branches. could you please post the source job configuration trait?  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox

2018-11-01 Thread hsku...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Skupin commented on  JENKINS-53462  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox   
 

  
 
 
 
 

 
 Daniel Beck, I simply want to report back that one of our engineers who works a lot with Jenkins just checked the latest release of Jenkins and it indeed seems to work all fine. Having it in the next LTS release would be fantastic! Thanks!  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing

2018-11-01 Thread casey.mother...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Motherway commented on  JENKINS-54366  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing   
 

  
 
 
 
 

 
 I am seeing the same issue.  Additionally there is a new warning message in the Jenkins Console Output that was not there before: 

 

 [WARNING]: Extra variables defined but prompt for variables on launch is not set in tower job 

 We recently upgraded to AT 3.3.1 and Jenkins AT plugin 0.9.0. My Jenkins job kicks off an AT Workflow.  The workflow has never had a "Prompt on Launch" option.  The jobs within the workflow do have the prompt option enabled.  In the past, the extra vars passed over by the Jenkins AT plugin have always magically passed through to the Jobs.  Now the vars do not make it through. I would consider this to be a blocking issue, not a minor 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread ri...@meetfeli.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rienk Prinsen assigned an issue to Rienk Prinsen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54399  
 
 
  Configuration page no longer loads   
 

  
 
 
 
 

 
Change By: 
 Rienk Prinsen  
 
 
Assignee: 
 Rienk Prinsen  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch

2018-11-01 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-54206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Merged PRs not being removed from multibranch   
 

  
 
 
 
 

 
 as reporter you should be able to reopen  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread keith.b...@inmarsat.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Ball commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 I just ran into the same issue as well and downgrading to 3.3. also fixed the problem for me.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch

2018-11-01 Thread gun...@grodotzki.co.za (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gunter Grodotzki commented on  JENKINS-54206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Merged PRs not being removed from multibranch   
 

  
 
 
 
 

 
 Is this perhaps related to us using: https://github.com/jenkinsci/basic-branch-build-strategies-plugin - or would that completely be unrelated? Also can we please re-open the issue as this indeed a bug we are experiencing    
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54378) Pipeline templates in parallel blocks are interpreted as being "nested"

2018-11-01 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is intended and correct behavior - you can only run one Declarative Pipeline per run, meaning you can't nest them and you can't run two in parallel within the same Jenkinsfile.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54378  
 
 
  Pipeline templates in parallel blocks are interpreted as being "nested"   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch

2018-11-01 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-54206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Merged PRs not being removed from multibranch   
 

  
 
 
 
 

 
 Very strange... because it is working for me  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54405) New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment

2018-11-01 Thread adamstrace...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Stracener created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54405  
 
 
  New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 _unsorted  
 
 
Created: 
 2018-11-01 17:27  
 
 
Environment: 
 Jenkins Version: 2.147  Plugin Version: 1.4  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Adam Stracener  
 

  
 
 
 
 

 
 Ever since upgrading the 1.4 of the plugin all attempts to notify New Relic of deployment fails with ERROR: Failed to notify New Relic. Application ID:    There is no Component listed for this plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
  

[JIRA] (JENKINS-48421) Support kubernetes in Declarative Pipeline

2018-11-01 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is basically handled by the kubernetes plugin's Declarative support.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48421  
 
 
  Support kubernetes in Declarative Pipeline
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54404) google compute engine plugin support "stopped mode"

2018-11-01 Thread kai_j...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kai Jing created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54404  
 
 
  google compute engine plugin support "stopped mode"   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Evan Brown  
 
 
Components: 
 google-compute-engine-plugin  
 
 
Created: 
 2018-11-01 17:19  
 
 
Environment: 
 Linux 18.04  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Kai Jing  
 

  
 
 
 
 

 
 Likely current gce plugin doesn't support the feature "to make instance in stopped mode instead of terminate it after disconnection". Here is the feature statement of jenkins aws plugin can do: "Check this if you want the instance to be stopped instead of terminated when it times out due to being idle. This allows existing instances to be used when provisioning a slave. You would use this option to preserve the state of the instance, including that of the EBS volume connections."  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace

2018-11-01 Thread adam.broussea...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Brousseau edited a comment on  JENKINS-54225  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using disableDeferredWipeout within pipeline job results in no deleted workspace   
 

  
 
 
 
 

 
 Also seeing this issue. Seems to leave behind the workspace (and .git folder) but the Git repository is "corrupt" so the next build will fail.{quote} fatal:  Running shell script+ git clean -ffxd fatal: Not a git repository (or any parent up to mount point /home/jenkins)Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).{quote}  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace

2018-11-01 Thread adam.broussea...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Brousseau commented on  JENKINS-54225  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using disableDeferredWipeout within pipeline job results in no deleted workspace   
 

  
 
 
 
 

 
 Also seeing this issue. Seems to leave behind the workspace (and .git folder) but the Git repository is "corrupt" so the next build will fail. {{fatal: Running shell script + git clean -ffxd Not a git repository (or any parent up to mount point /home/jenkins) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).}}  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace

2018-11-01 Thread adam.broussea...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Brousseau edited a comment on  JENKINS-54225  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using disableDeferredWipeout within pipeline job results in no deleted workspace   
 

  
 
 
 
 

 
 Also seeing this issue. Seems to leave behind the workspace (and .git folder) but the Git repository is "corrupt" so the next build will fail.{ { quote} fatal: Running shell script+ git clean -ffxdNot a git repository (or any parent up to mount point /home/jenkins)Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). {quote } }  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-50730) NoClassDefFound errors in Cloud Slaves

2018-11-01 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-50730  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NoClassDefFound errors in Cloud Slaves   
 

  
 
 
 
 

 
 As far as I've been able to tell so, this is not a cause of failures or even a direct symptom. It results after an earlier connection failure and just indicates that a reconnection attempt has failed. The stack traces all begin with a failure in onReconnect(). This indicates the connection has terminated and Remoting is attempting to reconnect. Unfortunately, the reconnect attempt fails and this message results. Connection failures and disconnects can happen for many reasons, commonly associated with system, network, or environment issues. Particularly if nothing has changed and this suddenly starts occurring it is likely to be one of these external causes. It might be possible to improve the retry logic but without further information on what is occurring it is difficult to know what changes might improve it. One thing I could easily do is to change the log messaging and downgrade the severity of this particular message.  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-52973) Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2

2018-11-01 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing the original report as a duplicate of JENKINS-48944   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52973  
 
 
  Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Resolved  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread jonathan_tan...@colpal.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Tancer commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 I just ran into this same issue. Downgrading to 3.3 fixed the 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52973) Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2

2018-11-01 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev edited a comment on  JENKINS-52973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2   
 

  
 
 
 
 

 
 [~vputhiye] "Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.quayio.trigger.PushEventNotificationCause#notification for class". This is an issue in another plugin: [https://github.com/jenkinsci/quayio-trigger-plugin] . A separate issue needs to be raised for it to the plugin maintainersJSONObject is explicitly blacklisted from serialization  tho, so the fix mileage may vary  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-52973) Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2

2018-11-01 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-52973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log on jenkins 2.121.2   
 

  
 
 
 
 

 
 Vinay Puthiyedath "Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.quayio.trigger.PushEventNotificationCause#notification for class". This is an issue in another plugin: https://github.com/jenkinsci/quayio-trigger-plugin . A separate issue needs to be raised for it to the plugin maintainers JSONObject is explicitly blacklisted from serialization  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version

2018-11-01 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-32793  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version   
 

  
 
 
 
 

 
 

Its intended to receive a job config.xml? Its being passed a string like this: "" Im trying to parse this explanation but so confused where job config.xml fits in here
 That's a clever hack of the API, but not the intended purpose. You can submit any XML you want, it only cares about the plugin attributes. And those typically appear in Jenkins job config.xml files (potentially build.xml, too lazy to check). The idea is to ease the migration of job configurations (and potentially build data) by ensuring a Jenkins instance is able to read a given XML file.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13

2018-11-01 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran commented on  JENKINS-54331  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13   
 

  
 
 
 
 

 
 Torsten Kleiber does 2.2.14 work out for you?   It is not for me.   With 2.2.14, new submitted PR does not get built, no build for subsequence commits to the branch.   ended up to revert back to 2.2.13, delete the PR and create new one   For my production build, we stick with 2.2.12  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-01 Thread nickbr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicholas Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54401  
 
 
  java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
Change By: 
 Nicholas Brown  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version

2018-11-01 Thread fakemailred...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 red der commented on  JENKINS-32793  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version   
 

  
 
 
 
 

 
 I dont understand what this means:  "This URL is intended to receive a job config.xml file, which has included the plugin versions to generate it for some time. We expect that new plugin releases are able to load old job config.xml's, therefore any current version will satisfy a requirement of an older release specified in the job config.xml." Its intended to receive a job config.xml? Its being passed a string like this: "" Im trying to parse this explanation but so confused where job config.xml fits in here      
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54396) `Configure System` page doesn't work after upgrading to 2.138.2

2018-11-01 Thread kantm...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 kant makm commented on  JENKINS-54396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `Configure System` page doesn't work after upgrading to 2.138.2   
 

  
 
 
 
 

 
 Thanks.  I downloaded the 3.3 .hpi from here https://updates.jenkins-ci.org/download/plugins/config-file-provider/  and loaded it to jenkins through the advanced plugin manager and it seems to have cleared up the 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-01 Thread nickbr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicholas Brown commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 This is the Pull-Request that introduced this code: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/145  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-01 Thread nickbr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicholas Brown commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 The NullPointerException exception is in the new file BitbucketGitSCMRevision.java introduced as part of JENKINS-53707  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread david.goate+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Goate updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54399  
 
 
  Configuration page no longer loads   
 

  
 
 
 
 

 
Change By: 
 David Goate  
 

  
 
 
 
 

 
 Every Since version 3.4 every  time I click the configure system link  (manage -> configure system)  I get an error page.  The error is: {code:java}org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.138.2.jar!/jenkins/model/Jenkins/configure.jelly:51:84:  No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at {code} currently I can't access any configuration page. I think today two plugins were updated but I can't find a way Downgrading  to  list which ones  3 . 3 fixes 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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread david.goate+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Goate updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54399  
 
 
  Configuration page no longer loads   
 

  
 
 
 
 

 
Change By: 
 David Goate  
 
 
Component/s: 
 config-file-provider-plugin  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-01 Thread david.goate+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Goate updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54399  
 
 
  Configuration page no longer loads   
 

  
 
 
 
 

 
Change By: 
 David Goate  
 
 
Environment: 
 jenkins 2.138.2 config fiel provider 3.4  
 

  
 
 
 
 

 
 
 

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


[JIRA] (JENKINS-54403) Job fail when GitHub tag was recreated

2018-11-01 Thread n.shchipac...@anchorfree.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikita Shchipachev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54403  
 
 
  Job fail when GitHub tag was recreated   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2018-11-01 16:04  
 
 
Environment: 
 Jenkins ver. 2.144  GitHub Authentication plugin 0.29  GitHub Branch Source Plugin 2.4.1  GitHub API Plugin 1.92  GitHub plugin 1.29.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nikita Shchipachev  
 

  
 
 
 
 

 
 Hi! I noticed that a job which based on some GitHub tag become broken after re-tag (deleting of the tag on GitHub, creation of a GitHub tag with the same name). After this related builds falls with messages like this: 

 

Started by user Some User
06:27:03 Connecting to https://api.github.com using some-user/** (Jenkins Global credentials)
java.io.FileNotFoundException: https://api.github.com/repos/Organization/repository/git/refs/tags/some-tag
	at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243)
	at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
	at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)
	at org.kohsuke.github.Requester.parse(Requester.java:617)
	at org.kohsuke.github.Requester.parse(Requester.java:599)
	at org.kohsuke.github.Requester._to(Requester.java:277)
Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/git/refs/#get-a-reference"}
	at org.kohsuke.github.Requester.handleApiError(Requester.java:691)
	at org.kohsuke

[JIRA] (JENKINS-54402) Pipeline Syntax page is missing the dropdown for supported parsers

2018-11-01 Thread gen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gennady Feldman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54402  
 
 
  Pipeline Syntax page is missing the dropdown for supported parsers   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ulli Hafner  
 
 
Attachments: 
 warnings-pipeline-syntax1.PNG  
 
 
Components: 
 warnings-ng-plugin  
 
 
Created: 
 2018-11-01 16:02  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Gennady Feldman  
 

  
 
 
 
 

 
 I am running warnings-ng-1.0.0beta1 and noticed that when I pull up Pipeline Syntax page the dropdown for supported parsers is missing. I'll attach a screenshot.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

   

  1   2   3   >