[JIRA] (JENKINS-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.

2019-05-06 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41805  
 
 
  Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Assignee: 
 Ryan Campbell  
 

  
 
 
 
 

 
 
 

 
 
 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-50715) Pipeline fails with NPE due to Blue Ocean favorites

2019-05-06 Thread christian.haeuss...@huk-coburg.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Häussler commented on  JENKINS-50715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline fails with NPE due to Blue Ocean favorites   
 

  
 
 
 
 

 
 We have the same issue with: Blue Ocean 1.9.1, Autofavorite 1.2.2 and Jenkins 2.138.41.0.1-fixed java.lang.NullPointerException at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:70)  
 

  
 
 
 
 

 
 
 

 
 
 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-57349) INFO: I/O error in channel Chunked connection to http://localhost:8080/

2019-05-06 Thread al...@twindb.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Kuzminsky created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57349  
 
 
  INFO: I/O error in channel Chunked connection to http://localhost:8080/   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 cli  
 
 
Created: 
 2019-05-07 04:38  
 
 
Environment: 
 {noformat}  jenkins 2.164.2, installed from https://pkg.jenkins.io/debian-stable by the jenkins Chef cookbook on Ubuntu 18.04.1 LTS.   No additional plugins (only those bundled with the package)  {noformat}  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Aleksandr Kuzminsky  
 

  
 
 
 
 

 
 My issue is very similar to previously filed JENKINS-23232 and JENKINS-34287. These issues were filed when Jenkins version was 1.something and say the bug has been fixed since then, however now it's the version 2.164.2 and the bug (same or similar) is come back. Besides, it looks like the suggested workaround with hudson.diyChunking=true doesn't work for this case. So, I'm filing this issue. I'm installing on a very fresh virtualbox machine Ubuntu 18.04 Jenkins 2.164.2. It is being installed by the jenkins chef cookbook. It is my understanding that the cookbook simply installs a jenkins repo (https://pkg.jenkins.io/debian-stable) and installs the jenkins package. It also installs openjdk-8-jdk:amd64, version 8u191-b12-2ubuntu0.18.04.1. There is no pretty much anything else on this box. No firewall, no other packages, nothing I can think of. The external network seems to be stable as well.  Jenkins runs as this command 

 
/usr/bin/java -Dhudson.diyChunking=false -Djenkins.install.runSetupWizard=false -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpListenAddress=0.0.0.0 

[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents

2019-05-06 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-57347  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance degradation running pipeline step sh on remote agents   
 

  
 
 
 
 

 
 Probably related to track credentials, you can disable it https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#threads-stuck-at-credentialsprovidertrackall  
 

  
 
 
 
 

 
 
 

 
 
 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-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes

2019-05-06 Thread median...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Jones commented on  JENKINS-53560  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Cannot stop sshd service" when provisioning Azure Windows nodes   
 

  
 
 
 
 

 
 Jie Shen I’d be happy to test a PR for a few days or weeks, if that would help. I can’t reproduce it consistently — it seems entirely random — so it would need to run for a little while to see if it solved 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-57337) Unable to install the updated plugin of OWASP Dependency Check

2019-05-06 Thread steve.spring...@owasp.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57337  
 
 
  Unable to install the updated plugin of OWASP Dependency Check   
 

  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
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-57337) Unable to install the updated plugin of OWASP Dependency Check

2019-05-06 Thread steve.spring...@owasp.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett commented on  JENKINS-57337  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install the updated plugin of OWASP Dependency Check   
 

  
 
 
 
 

 
 The stack trace doesn't have any packages/classes with org.owasp. This is a Jenkins issue and should be raised on the Jenkins mailing list.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and 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-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes

2019-05-06 Thread jie...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen commented on  JENKINS-53560  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Cannot stop sshd service" when provisioning Azure Windows nodes   
 

  
 
 
 
 

 
 Nick Jones I can draft a PR to add simple retry strategy for this. But I am not sure whether running the command "powershell -ExecutionPolicy Bypass Restart-Service sshd" several times would mitigate this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated

2019-05-06 Thread arun6...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arun Gupta created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57348  
 
 
  EC2 Plugin not working when AWS Keys are rotated   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 FABRIZIO MANFREDI  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2019-05-07 00:20  
 
 
Labels: 
 ec2-plugin aws rotate keys  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Arun Gupta  
 

  
 
 
 
 

 
   When we use EC2 Plugin and specify AWS credentials to use to spin up instances, the plugin doesn't work when the AWS Credentials are rotated. It works when we manually go to Manage Jenkins -> Configure System -> Click Save button.   ```   WARNING: SlaveTemplate{ami='ami-067c8970c0b9a2d12', labels='wcs-build-agent-ec2'}. Exception during provisioning com.amazonaws.services.ec2.model.AmazonEC2Exception: AWS was not able to validate the provided access credentials (Service: AmazonEC2; Status Code: 401; Error Code: AuthFailure; Request ID: a290fa76-f0fa-48ad-b9e8-2e2d41d5bb37) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1695) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1350) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1101) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:758) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:732) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:714) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:674) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:656) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:520) at 

[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch

2019-05-06 Thread m...@earthling.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mario Jauvin commented on  JENKINS-57324  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch   
 

  
 
 
 
 

 
 For all intents you can ignore the. I will remove them as they are not important to reproducing 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-57263) Java java.lang.ClassNotFoundException on Jenkins Startup

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57263  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Java java.lang.ClassNotFoundException on Jenkins Startup   
 

  
 
 
 
 

 
  Looks like a binary conflict somewhere.  
 

  
 
 
 
 

 
 
 

 
 
 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-57263) Java java.lang.ClassNotFoundException on Jenkins Startup

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57263  
 
 
  Java java.lang.ClassNotFoundException on Jenkins Startup   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 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-57263) Java java.lang.ClassNotFoundException on Jenkins Startup

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57263  
 
 
  Java java.lang.ClassNotFoundException on Jenkins Startup   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 build-timeout-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-53950) Support configuration as code

2019-05-06 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe assigned an issue to René Scheibe  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53950  
 
 
  Support configuration as code   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Assignee: 
 Aleksi Simell René Scheibe  
 

  
 
 
 
 

 
 
 

 
 
 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-53950) Support configuration as code

2019-05-06 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe started work on  JENKINS-53950  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
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-56666) maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'

2019-05-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc edited a comment on  JENKINS-5  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'   
 

  
 
 
 
 

 
 [~reitzmichnicht] can you please share the exact message you get? Can you give us details on the type of build agent that you are using? Can you confirm that you don't ue Windows build agents with cygwin (or equivalent)?  
 

  
 
 
 
 

 
 
 

 
 
 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-56666) maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'

2019-05-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc commented on  JENKINS-5  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'   
 

  
 
 
 
 

 
 Michael Düsterhus can you please share the exact message you get?  
 

  
 
 
 
 

 
 
 

 
 
 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-57199) java.io.IOException: Exception archiving {...list of files...}

2019-05-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc commented on  JENKINS-57199  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.IOException: Exception archiving {...list of files...}   
 

  
 
 
 
 

 
 Hello Robert Baker You run on a quite old version of Jenkins, 2.89 - 2018-02-14, coudl you upgrade to a more recent version and see if the problem is still there? Moreover, can you please give us details on the build environment and on the pipeline that causes the error: 
 
Flavour of the build agent: it's a Windows agent, do you have more details? Do you have an antivirus running that could cause problems while compressing the generated artifact? 
Size and type of the generated Maven artifacts 
Sample of the pipeline code / Jenkinsfile 
  
 

  
 
 
 
 

 
 
 

 
 
 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-57199) java.io.IOException: Exception archiving {...list of files...}

2019-05-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc assigned an issue to Cyrille Le Clerc  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57199  
 
 
  java.io.IOException: Exception archiving {...list of files...}   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
Assignee: 
 Alvaro Lobato Cyrille Le Clerc  
 

  
 
 
 
 

 
 
 

 
 
 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-57199) java.io.IOException: Exception archiving {...list of files...}

2019-05-06 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57199  
 
 
  java.io.IOException: Exception archiving {...list of files...}   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 

  
 
 
 
 

 
 * {noformat} 23:11:56 *  ERROR: [withMaven] WARNING Exception executing Maven reporter 'Generated Artifacts Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/] * 23:11:56 *  java.io.IOException: Exception archiving \{...removed list of files...} * 23:11:56 *    at org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher.process(GeneratedArtifactsPublisher.java:122) * 23:11:56 *    at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118) * 23:11:56 *    at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050) * 23:11:56 *    at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366) * 23:11:56 *    at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73) * 23:11:56 *    at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166) * 23:11:56 *    at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) * 23:11:56 *    at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) * 23:11:56 *    at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) * 23:11:56 *    at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59) * 23:11:56 *    at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232) * 23:11:56 *    at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) * 23:11:56 *    at 

[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents

2019-05-06 Thread nancy.robert...@ca.ibm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nancy Robertson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57347  
 
 
  Performance degradation running pipeline step sh on remote agents   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Attachments: 
 issue-ssh-slaves-perf.groovy  
 
 
Components: 
 ssh-slaves-plugin  
 
 
Created: 
 2019-05-06 20:47  
 
 
Environment: 
 Jenkins ver. 2.150.2  ssh-slaves plugin version 1.27 to 1.29.4  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nancy Robertson  
 

  
 
 
 
 

 
 I noticed a severe performance degradation in the execution of the pipeline sh step when the agent is connected via the ssh-slaves plugin.  I performed extra testing on a standalone jenkins installed from docker image jenkins/jenkins:lts with a number of different versions of the ssh-slaves plugin. Attached is the Jenkinsfile I used to test this. With 10 iterations of the sh step, versions 1.26 takes 14-15 seconds while version 1.27 takes 24-27 seconds. That is without taking into account the first build after the agent has started which always takes longer (22 seconds in 1.26 and 40 seconds in 1.27)   I have also tried "Launch agent via execution of a command on the master" which performs in a way comparable to the ssh-slaves plugin in version before 1.27.   The only workaround I found is to keep the ssh-slaves plugin at version 1.26.  
 

  
 
 
 
 

 

[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164

2019-05-06 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: userContent *zip* (all files in zip) stopped working at 2.164   
 

  
 
 
 
 

 
 Me or one of my teammates will be following up on this ticket to fix the problem. I believe I've been able to isolate the issue down to a difference in behavior when using the escape hatch where you can view files that are links from outside userContent or are themselves descendants of a link, but the same files are skipped in the zip file output regardless of the escape hatch.  
 

  
 
 
 
 

 
 
 

 
 
 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-56249) userContent *zip* (all files in zip) stopped working at 2.164

2019-05-06 Thread glenn.herb...@hcl.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Herbert commented on  JENKINS-56249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: userContent *zip* (all files in zip) stopped working at 2.164   
 

  
 
 
 
 

 
 Thanks Matt Sicker for verification.  
 

  
 
 
 
 

 
 
 

 
 
 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-44729) Optimize git clones via shared reference repo for multi branch builds of same repository

2019-05-06 Thread tris...@techsoft3d.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tristan Lewis commented on  JENKINS-44729  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Optimize git clones via shared reference repo for multi branch builds of same repository   
 

  
 
 
 
 

 
 Liam Newman - I've hackily enabled this functionality to some degree via a shared pipeline plugin, but we've considered it a workaround until it was supported in the plugin itself. So yes, we're still interested in getting the PR moved forward and eventually integrated if possible. Let me know if I can do anything to help on that front. 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-44787) AWS Simple AD stopped working

2019-05-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This should be fixed as active-directory-2.14  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-44787  
 
 
  AWS Simple AD stopped working   
 

  
 
 
 
 

 
Change By: 
 Félix Belzunce Arcos  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 active-directory-2.14  
 

  
 
 
 
 

 
 
 

 
 
 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-56249) userContent *zip* (all files in zip) stopped working at 2.164

2019-05-06 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: userContent *zip* (all files in zip) stopped working at 2.164   
 

  
 
 
 
 

 
 Oh, and don't be confused by the double symbolic link thing going on there. This is still reproducible by simply linking to ../../config.xml  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164

2019-05-06 Thread boa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-56249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: userContent *zip* (all files in zip) stopped working at 2.164   
 

  
 
 
 
 

 
 Here is what I can reproduce which sound related to your problem: 
 
I run Jenkins with the -Dhudson.model.DirectoryBrowserSupport.allowSymlinkEscape=true flag set. (Or I modify it in the script console) 
In my userContent directory, I have one symbolic link to a file or directory outside of userContent such as ../../jobs/TestJob/lastSuccess/archive/ 
I download the zip generated by the directory browser and find that it did not include those files despite using the flag. 
 When I use Jenkins 2.163, the zip contains the data that I can also see in the browser. When I use Jenkins 2.164 or the latest release, the zip does not contain the files, though I can view the files in the browser still.  
 

  
 
 
 
 

 
 
 

 
 
 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-44787) AWS Simple AD stopped working

2019-05-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos edited a comment on  JENKINS-44787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS Simple AD stopped working   
 

  
 
 
 
 

 
 This issue should be fixed in: https://github.com/jenkinsci/active-directory-plugin/pull/ 92 93  
 

  
 
 
 
 

 
 
 

 
 
 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-44729) Optimize git clones via shared reference repo for multi branch builds of same repository

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


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-44729  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Optimize git clones via shared reference repo for multi branch builds of same repository   
 

  
 
 
 
 

 
 Tristan Lewis Chris Williams The submitted PR has been postponed by Mark Waite. If you are interested in making it happen, please say so and we'll figure out a way to loop you with folks working on the git 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-57264) accessing file credential in pipeline causes nullPointerException

2019-05-06 Thread michael.albergh...@keysight.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Alberghini updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57264  
 
 
  accessing file credential in pipeline causes nullPointerException   
 

  
 
 
 
 

 
Change By: 
 Mike Alberghini  
 

  
 
 
 
 

 
 After a plugin update, one of my pipelines stopped working.  It's a groovy script that kicks off packer, which uses ansible to configure an AWS system.  After a bit of pairing down, I determined that the pipeline was crashing at the withCredentials([file bit.  I stripped the code down to a simple pipeline that demonstrates the error. {quote}pipeline Unknown macro: \ {   agent   \  { label 'AWS-Pipeline-Executor' }    stages { stage('Build') {       steps   {                  withCredentials([file(credentialsId : 'ansible-vault', variable: 'VAULT_PASS_FILE')])Unknown macro: \{               echo "Inside creds loop"          }               }        }      }   }    {quote} The only output is:  [Pipeline] Start of Pipeline[Pipeline] nodeRunning on [AWS-Pipeline-Executor|http://woodhouse.atl.is.keysight.com:8080/computer/AWS-Pipeline-Executor/] in /home/asdc-jenkins/jenkins/workspace/.DevOps/MikeTest[Pipeline] {[Pipeline] stage[Pipeline]{ (Build)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.lang.NullPointerException Finished: FAILURE   Attached is the Jenkins log showing the error thrown.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   


[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException

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


 
 
 
 

 
 
 

 
   
 Liam Newman edited a comment on  JENKINS-57195  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scan organization fails with FileNotFoundException   
 

  
 
 
 
 

 
 [~giorgiosironi] This sound like some kind of condition where permissions haven't caught up with your settings.  Do you get it each time you create a new private repo?   
 

  
 
 
 
 

 
 
 

 
 
 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-57279) Github Organization PRs not building on agents

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


 
 
 
 

 
 
 

 
   
 Liam Newman updated  JENKINS-57279  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57279  
 
 
  Github Organization PRs not building on agents   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
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-54635) Add ability to specify auth path during login

2019-05-06 Thread jake.rem...@carlsonwagonlit.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jake Remitz commented on  JENKINS-54635  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ability to specify auth path during login   
 

  
 
 
 
 

 
 It looks like this was addressed with https://github.com/jenkinsci/hashicorp-vault-plugin/pull/22 however I still don't see the feature. I'm using v2.2.0 is it possible to get a minor release pushed to include this fix and any other recent fixes Peter Tierno?  
 

  
 
 
 
 

 
 
 

 
 
 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-44787) AWS Simple AD stopped working

2019-05-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos commented on  JENKINS-44787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS Simple AD stopped working   
 

  
 
 
 
 

 
 This issue should be fixed in: https://github.com/jenkinsci/active-directory-plugin/pull/92  
 

  
 
 
 
 

 
 
 

 
 
 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-44787) AWS Simple AD stopped working

2019-05-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44787  
 
 
  AWS Simple AD stopped working   
 

  
 
 
 
 

 
Change By: 
 Félix Belzunce Arcos  
 
 
URL: 
 https://github.com/jenkinsci/active-directory-plugin/pull/92  
 

  
 
 
 
 

 
 
 

 
 
 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-57346) plugins should not rely on help from jenkins core

2019-05-06 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57346  
 
 
  plugins should not rely on help from jenkins core   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Issue Type: 
 New Feature Task  
 

  
 
 
 
 

 
 
 

 
 
 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-57346) plugins should not rely on help from jenkins core

2019-05-06 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57346  
 
 
  plugins should not rely on help from jenkins core   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Bruno P. Kinoshita  
 
 
Components: 
 active-choices-plugin, app-detector-plugin, autocomplete-parameter-plugin, bulk-builder-plugin, copyartifact-plugin, credentials-plugin, crittercism-dsym-plugin, extensible-choice-parameter-plugin, git-parameter-plugin, hidden-parameter-plugin, inflectra-spira-integration-plugin, jobgenerator-plugin, mask-passwords-plugin, metadata-plugin, p4-plugin, packageversion-plugin, perfectomobile, persistent-parameter-plugin, promoted-builds-plugin, promoted-builds-simple-plugin, random-string-parameter-plugin, run-selector-plugin, stride-notification-plugin, validating-string-parameter-plugin, worksoft-certify-process-runner-plugin  
 
 
Created: 
 2019-05-06 17:49  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/pull/3921#issuecomment-489697493 

Of course plugins should not assume particular core resource paths exist.
 Three cases: 1. Plugins are clearly using jenkins resources: https://github.com/jenkinsci/copyartifact-plugin/search?q=%22help%2Fparameter%22_q=%22help%2Fparameter%22 

 

26  "${%Name}" field="name" help="/help/parameter/name.html">
…
31  "${%Description}" field="description" help="/help/parameter/description.html"> 

 https://github.com/jenkinsci/credentials-plugin/search?q=%22help%2Fparameter%22_q=%22help%2Fparameter%22 

  

[JIRA] (JENKINS-44787) AWS Simple AD stopped working

2019-05-06 Thread fbelz...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Félix Belzunce Arcos edited a comment on  JENKINS-44787  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AWS Simple AD stopped working   
 

  
 
 
 
 

 
 To debug this issue -  or any other in the active directory plugin you need to create a custom logger under *Manage Jenkins -> System Log* for {{hudson.plugins.active_directory}}. This particular issue seems to be related to the fact that StartTls option is not working properly. In case StartTls connection does not work correctly, the plugin should automatically fall back into the plain-text communication. The problem is that when StartTls fails with an Exception, then the fallback does not work in all the cases.I  think the problem is that when the  was able to reproduce this issue launching a  {{ Exception CertPathValidatorException }}  happens we should . In this case, it is not even a possibility to just  close the  StartTls channel for the plain  startTLS  connection  and  to  be able to work correctly  re-create the full {{LdapContext}} is needed .{code:java}2019-04-30 15:44:58.322+ [id=48] FINE h.p.a.ActiveDirectorySecurityRealm$DescriptorImpl#bind: Failed to start TLS. Authentication will be done via plain-text LDAPjava.security.cert.CertPathValidatorException: Algorithm constraints check failed on signature algorithm: 1.2.840.113549.1.1.10 at sun.security.provider.certpath.AlgorithmChecker.check(AlgorithmChecker.java:278) at sun.security.ssl.AbstractTrustManagerWrapper.checkAlgorithmConstraints(SSLContextImpl.java:1116)Caused: java.security.cert.CertificateException: Certificates do not conform to algorithm constraints at sun.security.ssl.AbstractTrustManagerWrapper.checkAlgorithmConstraints(SSLContextImpl.java:1120) at sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1044) at sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:986) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)Caused: javax.net.ssl.SSLHandshakeException at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:328) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:322) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1614) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052) at sun.security.ssl.Handshaker.process_record(Handshaker.java:987) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397) at com.sun.jndi.ldap.ext.StartTlsResponseImpl.startHandshake(StartTlsResponseImpl.java:353) at com.sun.jndi.ldap.ext.StartTlsResponseImpl.negotiate(StartTlsResponseImpl.java:217) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:658) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:628) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:575) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:358) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:341) at 

[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.

2019-05-06 Thread pgarr...@us.ibm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philip Garrett commented on  JENKINS-52750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dir step creates a @tmp directory at  level.   
 

  
 
 
 
 

 
 The behavior is both undocumented (as far as I can tell), and surprising, since normally "change current directory" would not be a mutating operation.   Also, using the name of the directory requested by the user compounds the confusion, because it's easy to miss the @tmp suffix, or think it's an artifact of the exception rendering. I didn't really notice the @tmp suffix until after I had been fighting with this problem for a while, believing Jenkins was trying to create a directory that already existed.  
 

  
 
 
 
 

 
 
 

 
 
 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-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes

2019-05-06 Thread median...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Jones commented on  JENKINS-53560  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Cannot stop sshd service" when provisioning Azure Windows nodes   
 

  
 
 
 
 

 
 Jie Shen could I get an update on this? We still get it every few days when provisioning Azure nodes. 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-57345) Cannot install Java on DO agents any longer

2019-05-06 Thread damien.corabo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57345  
 
 
  Cannot install Java on DO agents any longer   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 digitalocean-plugin  
 
 
Created: 
 2019-05-06 17:00  
 
 
Environment: 
 Jenkins 2.164.2  Digital Ocean plugin 1.0  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Damien Coraboeuf  
 

  
 
 
 
 

 
 Hi, For quite some time already, the creation of Digital Ocean agents has become quite brittle and barely usable. I'm using the "Ubuntu Docker 18.09.2~3 on 18.04" image as a base, and the installation of the Java JVM for bootstrapping the agent fails (almost all the time, but not always) with: 

 

WARNING: Installing java failed.
java.lang.Exception: Installing java failed.
	at com.dubture.jenkins.digitalocean.DigitalOceanComputerLauncher.launch(DigitalOceanComputerLauncher.java:184)
 

 In the agent log, one of the last messages we see is: 

 

E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
 

 Any idea what could be causing this? Thanks for any feedback, Damien  
 
   

[JIRA] (JENKINS-57279) Github Organization PRs not building on agents

2019-05-06 Thread jo...@subtlemedical.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorge Guzman updated  JENKINS-57279  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57279  
 
 
  Github Organization PRs not building on agents   
 

  
 
 
 
 

 
Change By: 
 Jorge Guzman  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57279) Github Organization PRs not building on agents

2019-05-06 Thread jo...@subtlemedical.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorge Guzman commented on  JENKINS-57279  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Organization PRs not building on agents   
 

  
 
 
 
 

 
 That worked!!! 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-56595) Regression: higher than usual CPU usage with 2.164.1

2019-05-06 Thread kerrhome (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shannon Kerr edited a comment on  JENKINS-56595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression: higher than usual CPU usage with 2.164.1   
 

  
 
 
 
 

 
 Pretty sure we are now seeing this or something very similar after our recent upgrade to 2.150.3. We had nothing like this back when we were on 2.138.1.  I spread out some of our jobs and multibranch scans to try and mitigate the load. (fyi: running in Jenkins docker container)  Of course this doesn't match up with the original reporter who said it wasn't seen until an upgrade from 2.150.3.  I'm considering rolling back to 2.138.x at this point as it is disrupting my team.  
 

  
 
 
 
 

 
 
 

 
 
 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-56595) Regression: higher than usual CPU usage with 2.164.1

2019-05-06 Thread kerrhome (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shannon Kerr commented on  JENKINS-56595  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression: higher than usual CPU usage with 2.164.1   
 

  
 
 
 
 

 
 Pretty sure we are now seeing this or something very similar after our recent upgrade to 2.150.3. We had nothing like this back when we were on 2.138.1.  I spread out some of our jobs and multibranch scans to try and mitigate the load. (fyi: running in Jenkins docker container)  
 

  
 
 
 
 

 
 
 

 
 
 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-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError

2019-05-06 Thread h.kay...@pilz.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hannes Kayser commented on  JENKINS-52966  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError   
 

  
 
 
 
 

 
 We face the same issue. It causes builds to fail, the executor is stuck afterwards, but the stage seems to be null (displays only "part" instead of the current stage name).   Pipeline console output is java.lang.StackOverflowError at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040) [...] at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040)   The Jenkins error log contains the following: Mai 03, 2019 7:05:54 PM org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem WARNUNG: Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[/]] java.lang.StackOverflowError at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:114) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019) [...] I suspected the HTTP Request Plugin to be responsible for the failure and removed it from the Pipeline code. The removal reduced the occurance, but did not remove it completely. Any idea how to process with this issue?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message 

[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records

2019-05-06 Thread msollan...@dwavesys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Sollanych commented on  JENKINS-57173  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Issue with Darcs SCM plugin saving build records   
 

  
 
 
 
 

 
 Thanks for looking into this. I'm a bit new to Darcs myself, so I'm not sure how to determine what commands the Darcs SCM plugin is running to get the xml output. I have used simple xml output commands from Darcs for other purposes unrelated to this issue and have parsed the output with no issue, so there must be some particular command that would reveal where this weird byte is coming from, so I can track its origin down.   We do have a variety of bits of older non-Jenkins build automation around that might be automatically adding comments or similar that may be causing an issue with this, so I'll definitely be following up internally with those who know more, but if you have any pointers let me know.  
 

  
 
 
 
 

 
 
 

 
 
 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-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11

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


 
 
 
 

 
 
 

 
   
 Mark Waite started work on  JENKINS-57341  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
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-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11

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


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Mark Waite  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits

2019-05-06 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz edited a comment on  JENKINS-23606  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits   
 

  
 
 
 
 

 
 The [eight new tests|https://github.com/jenkinsci/git-plugin/blob/master/src/test/java/hudson/plugins/git/GitSCMTest.java#L358-L654] have been [merged to master](https://github.com/jenkinsci/git-plugin/pull/716). They include, in the form of "top level directory of the repo" and "inside a subdirectory" test, the following:* Merge commits inside of excluded regions get ignored ([file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L368], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L404])* Merge commits inside of included regions get processed as new changes ([file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L440], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L477] ) * Merge commits outside of included regions get ignored  (  [file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L515], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L552] ) * Merge commits outside of excluded regions get processed  (  [file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L590], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L628] )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received 

[JIRA] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits

2019-05-06 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz edited a comment on  JENKINS-23606  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits   
 

  
 
 
 
 

 
 The [eight new tests|https://github.com/jenkinsci/git-plugin/blob/master/src/test/java/hudson/plugins/git/GitSCMTest.java#L358-L654] have been [merged to master ]( | https://github.com/jenkinsci/git-plugin/pull/716 ) ] . They include, in the form of "top level directory of the repo" and "inside a subdirectory"  test  tests , the following:* Merge commits inside of excluded regions get ignored ([file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L368], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L404])* Merge commits inside of included regions get processed as new changes ([file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L440], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L477])* Merge commits outside of included regions get ignored ([file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L515], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L552])* Merge commits outside of excluded regions get processed ([file|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L590], [directory|https://github.com/jenkinsci/git-plugin/blob/0d7b5ab0fbd23aec73570f7b0693424360295993/src/test/java/hudson/plugins/git/GitSCMTest.java#L628])  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You 

[JIRA] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits

2019-05-06 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-23606  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits   
 

  
 
 
 
 

 
 The eight new tests have been [merged to master](https://github.com/jenkinsci/git-plugin/pull/716). They include, in the form of "top level directory of the repo" and "inside a subdirectory" test, the following: 
 
Merge commits inside of excluded regions get ignored (file, directory) 
Merge commits inside of included regions get processed as new changes (file, directory 
Merge commits outside of included regions get ignored file, directory 
Merge commits outside of excluded regions get processed file, directory 
  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-06 Thread mat...@mathin.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Ebert commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 I think Jesse already created a bug for the scoverage 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-57171) Permissive script security plugin is broken after updating to script security 1.58

2019-05-06 Thread julienduche...@live.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Julien Duchesne commented on  JENKINS-57171  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permissive script security plugin is broken after updating to script security 1.58   
 

  
 
 
 
 

 
 I can confirm what Brian says. Also, trying to approve the rejected methods froze our Jenkins instance (Actually, two of us made the same mistake on different instances).   
 

  
 
 
 
 

 
 
 

 
 
 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-21942) Unreliable defaulting of Jenkins.workspaceDir

2019-05-06 Thread kerrhome (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shannon Kerr edited a comment on  JENKINS-21942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unreliable defaulting of Jenkins.workspaceDir   
 

  
 
 
 
 

 
 [~batmat] I'm seeing the same.  Do we know what needs to be done to correct this?  Per [~jglick] on JENKINS-2111 this is not something we should ignore.  
 

  
 
 
 
 

 
 
 

 
 
 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-42192) permissive-security-script plugin should not log full stacktrace

2019-05-06 Thread sharkan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Herd edited a comment on  JENKINS-42192  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: permissive-security-script plugin should not log full stacktrace
 

  
 
 
 
 

 
 I believe one of the most recent plugin changes to Jenkins has changed this behavior since this used to work just fine but in the last week or so.  Unfortunatly I'm not sure which plugin may be conflicting with the permissive script plugin. Verisons:Jenkins: 1.164.2 LTSPermissive Script Security Plugin: 0.3Script Security Plugin: 1.58 We have about 30 other plugins as well, just thought these would be the most relavent.  
 

  
 
 
 
 

 
 
 

 
 
 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-21942) Unreliable defaulting of Jenkins.workspaceDir

2019-05-06 Thread kerrhome (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shannon Kerr commented on  JENKINS-21942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unreliable defaulting of Jenkins.workspaceDir   
 

  
 
 
 
 

 
 I'm seeing the same.  Do we know what needs to be done to correct this?  Per Jesse Glick on JENKINS-2111 this is not something we should ignore.  
 

  
 
 
 
 

 
 
 

 
 
 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-42192) permissive-security-script plugin should not log full stacktrace

2019-05-06 Thread sharkan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Herd commented on  JENKINS-42192  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: permissive-security-script plugin should not log full stacktrace
 

  
 
 
 
 

 
 I believe one of the most recent plugin changes to Jenkins has changed this behavior since this used to work just fine but in the last week or so.  Unfortunatly I'm not sure which plugin may be conflicting with the permissive script plugin.   Verisons: Jenkins: 1.164.2 LTS Permissive Script Security Plugin: 0.3 Script Security Plugin: 1.58  
 

  
 
 
 
 

 
 
 

 
 
 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-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 java11  java11 -devtools-compatibility  
 

  
 
 
 
 

 
 
 

 
 
 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-57342) Java Array .length is incorrectly determined as a call on the array type

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57342  
 
 
  Java Array .length is incorrectly determined as a call on the array type   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57273) NodeListener.onCreated was called when Jenkins.addNode or Nodes.addNode actually replaced an existing node

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57273  
 
 
  NodeListener.onCreated was called when Jenkins.addNode or Nodes.addNode actually replaced an existing node   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-57273) NodeListener.onCreated was called when Jenkins.addNode or Nodes.addNode actually replaced an existing node

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-57273  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It was fixed in Jenkins 2.176. LTS Candidate if 2.175 is selected as a baseline (unlikely)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57273  
 
 
  NodeListener.onCreated was called when Jenkins.addNode or Nodes.addNode actually replaced an existing node   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 Jenkins 2.176  
 

  
 
 
 
 

 
 
 

 
 
 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-46515) Launcher will retry connections forever under some irrecoverable status

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46515  
 
 
  Launcher will retry connections forever under some irrecoverable status   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Released As: 
 Remoting 3.30 , Jenkins 2.176  
 

  
 
 
 
 

 
 
 

 
 
 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-46515) Launcher will retry connections forever under some irrecoverable status

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46515  
 
 
  Launcher will retry connections forever under some irrecoverable status   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-57107) SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57107  
 
 
  SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-51004) slave.jar -loggingConfig argument not working as documented

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51004  
 
 
  slave.jar -loggingConfig argument not working as documented   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 diagnostics  lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 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-57107) SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57107  
 
 
  SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Released As: 
 Remoting 3.30 , , Jenkins 2.176  
 

  
 
 
 
 

 
 
 

 
 
 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-51004) slave.jar -loggingConfig argument not working as documented

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51004  
 
 
  slave.jar -loggingConfig argument not working as documented   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Released As: 
 Remoting 3.30 , Jenkins 2.176  
 

  
 
 
 
 

 
 
 

 
 
 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-11888) Jenkins CLI does not supports stopping jobs

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-11888  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released in 2.176 Thanks Ilia Zasimov!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-11888  
 
 
  Jenkins CLI does not supports stopping jobs   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 Jenkins 2.167  
 

  
 
 
 
 

 
 
 

 
 
 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-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
 The core regression was fixed in Jenkins 2.166. Now it is up to plugins to implement a proper fix on their side to avoid legitimate warnings in system logs. Norbert Weiß Dan Ebert could you please create follow-up tickets for that to the plugins?  
 

  
 
 
 
 

 
 
 

 
 
 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-57343) RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir

2019-05-06 Thread zichuan....@viavisolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zichuan Zou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57343  
 
 
  RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir   
 

  
 
 
 
 

 
Change By: 
 Zichuan Zou  
 

  
 
 
 
 

 
 RTC version: 6.0.4 Jenkins version: 2.150.1The component used to be checked out by Jenkins as a whole dir. Don't know why it starts to check it out as separate subdirs.For example: it should've checked out the componnet as:{quote}{{/component}}{quote}(it has sub dirs like {{/src}}, {{/include}}, etc)instead, it checks it out as:{quote}{{/src}} {{/include}} {{/doc}} {quote} Observations: 1. This only happens to this specific component, not seen it happens on other components. 2. I've tried removing the component from the workspace and add it back, doesn't work. 3. I've tried creating another jenkins job and use the same workspace, doesn't work. 4. I've tried using another workspace with same components, doesn't work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-06 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 

  
 
 
 
 

 
  after a  successfull  successful  Execution we get the following stacktrace: (rollback to jenkins 2.172 fixes the problem) {code:none}INFO: EXECUTION SUCCESS INFO:  INFO: Total time: 1:16.948s INFO: Final Memory: 88M/6409M INFO:  FATAL: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenBuild#projectActionReporters for class hudson.maven.MavenBuild java.io.NotSerializableException: The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /data/jenkins/jobs/.../javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath.writeObject(FilePath.java:2989) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel  Debugging information  message : Could not call hudson.FilePath.writeObject() cause-exception : java.io.NotSerializableException cause-message : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel --- at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at 

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-06 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 

  
 
 
 
 

 
  after a successfull  Excecution  Execution  we get the following stacktrace: (rollback to jenkins 2.172 fixes the problem)   {code:none}INFO: EXECUTION SUCCESS INFO:  INFO: Total time: 1:16.948s INFO: Final Memory: 88M/6409M INFO:  FATAL: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenBuild#projectActionReporters for class hudson.maven.MavenBuild java.io.NotSerializableException: The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /data/jenkins/jobs/.../javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath.writeObject(FilePath.java:2989) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel  Debugging information  message : Could not call hudson.FilePath.writeObject() cause-exception : java.io.NotSerializableException cause-message : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel --- at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at 

[JIRA] (JENKINS-54340) CWP throws error if pom.xml is used for plugins and casc for configuration

2019-05-06 Thread xase...@googlemail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Werner commented on  JENKINS-54340  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CWP throws error if pom.xml is used for plugins and casc for configuration   
 

  
 
 
 
 

 
 I tried it with https://github.com/jenkinsci/ci.jenkins.io-runner and the problem still persists even if i bump the CWP version to 1.6   

 

% make build 
java -jar .build/cwp-cli-1.6.jar \
 -configPath packager-config.yml -version 256.0-test 
May 06, 2019 5:09:41 PM io.jenkins.tools.warpackager.lib.impl.Builder build
INFO: Cleaning up the temporary directory tmp
Exception in thread "main" java.io.IOException: CasC section is declared, but CasC plugin is not declared in the plugins list
	at io.jenkins.tools.warpackager.lib.impl.Builder.verifyConfig(Builder.java:66)
	at io.jenkins.tools.warpackager.lib.impl.Builder.build(Builder.java:97)
	at io.jenkins.tools.warpackager.cli.Main.main(Main.java:53)
make: *** [Makefile:38: build] Error 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-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49588  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)   
 

  
 
 
 
 

 
 Correction: 2.163  
 

  
 
 
 
 

 
 
 

 
 
 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-48825) EC2 Node pem Permmissions incorrect

2019-05-06 Thread ashwini.y.lan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashwini L edited a comment on  JENKINS-48825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Node pem Permmissions incorrect   
 

  
 
 
 
 

 
 Even I am facing the same issue. I am unable to launch  ubuntu  UBUNTU  EC2 instance using EC2 plugin from  window  WINDOWS  machine. Getting error "Warning: Identity file C:\Windows\TEMP\ec2_471045675295473131.pem not accessible: No such file or directory. ubuntu@'public ip address': Permission denied (publickey)."Please help me in resolving this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57340) Trigger build with branch name as a parameter not working

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


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-57340  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Trigger build with branch name as a parameter not working   
 

  
 
 
 
 

 
 I believe that behavior is a bug, but it is a bug that is unlikely to be fixed. It has already been reported in Jira. I assume based on your description that you have a single Jenkins Pipeline job that is switching from one branch to another. That is a viable way to do things and is exactly how we would do things with Freestyle jobs.  However, multibranch Pipeline jobs are a much better way of handling that same condition. Multibranch Pipeline automatically creates and destroys jobs to match the branches in the source master. Review the Jenkins documentation on Branches and Pull Requests for more information about multibranch Pipeline and how it can manage jobs for 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-57344) Whitelist requests for some java.io and other misc calls

2019-05-06 Thread harid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara commented on  JENKINS-57344  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Whitelist requests for some java.io and other misc calls   
 

  
 
 
 
 

 
 PR: https://github.com/jenkinsci/script-security-plugin/pull/249  
 

  
 
 
 
 

 
 
 

 
 
 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-57344) Whitelist requests for some java.io and other misc calls

2019-05-06 Thread harid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57344  
 
 
  Whitelist requests for some java.io and other misc calls   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Hari Dara  
 
 
Components: 
 script-security-plugin  
 
 
Created: 
 2019-05-06 14:36  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Hari Dara  
 

  
 
 
 
 

 
 The following is a sample of some of the methods that are safe to be whitelisted and are quite useful: 
 
StringReader.read 
StringWriter.append 
new PrintWriter(Writer) (useful for capturing stacktraces as strings) 
List.add 
reverse() on List 
new LinkedHashSet() 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[JIRA] (JENKINS-51291) 'new view' wrong url - not relative

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-51291  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 'new view' wrong url - not relative   
 

  
 
 
 
 

 
 UPD: it's not   
 

  
 
 
 
 

 
 
 

 
 
 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-51291) 'new view' wrong url - not relative

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-51291  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 'new view' wrong url - not relative   
 

  
 
 
 
 

 
 Likely it is fixed by JENKINS-48447  
 

  
 
 
 
 

 
 
 

 
 
 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-53800) Whitelisting misc. methods

2019-05-06 Thread harid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara commented on  JENKINS-53800  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Whitelisting misc. methods   
 

  
 
 
 
 

 
 This was addressed in this PR: https://github.com/jenkinsci/script-security-plugin/pull/226  
 

  
 
 
 
 

 
 
 

 
 
 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-57343) RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir

2019-05-06 Thread zichuan....@viavisolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zichuan Zou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57343  
 
 
  RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir   
 

  
 
 
 
 

 
Change By: 
 Zichuan Zou  
 
 
Attachment: 
 confg_edited.png  
 
 
Attachment: 
 log_edited.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-57343) RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir

2019-05-06 Thread zichuan....@viavisolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zichuan Zou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57343  
 
 
  RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir   
 

  
 
 
 
 

 
Change By: 
 Zichuan Zou  
 

  
 
 
 
 

 
 RTC version: 6.0.4Jenkins version: 2.150.1The component used to be checked out by Jenkins as a whole dir. Don't know why it starts to check it out as separate subdirs.For example:it should've checked out the componnet as:  { quote} { { /component}} {quote} (it has sub dirs like {{/src}}, {{/include}}, etc)instead, it checks it out as: bq. { quote} { { /src}} bq. {{/include}} bq. {{/doc}}   (etc...)  {quote}   1. This only happens to this specific component, not seen it happens on other components.2. I've tried removing the component from the workspace and add it back, doesn't work.3. I've tried creating another jenkins job and use the same workspace, doesn't work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-57343) RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir

2019-05-06 Thread zichuan....@viavisolutions.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zichuan Zou created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57343  
 
 
  RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Deluan Quintão  
 
 
Components: 
 rtc-plugin  
 
 
Created: 
 2019-05-06 14:27  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Zichuan Zou  
 

  
 
 
 
 

 
 RTC version: 6.0.4 Jenkins version: 2.150.1 The component used to be checked out by Jenkins as a whole dir. Don't know why it starts to check it out as separate subdirs. For example: it should've checked out the componnet as: /component (it has sub dirs like /src, /include, etc) instead, it checks it out as: 

/src
 

/include
 

/doc (etc...)
 1. This only happens to this specific component, not seen it happens on other components. 2. I've tried removing the component from the workspace and add it back, doesn't work. 3. I've tried creating another jenkins job and use the same workspace, doesn't work.  
 

  
 
 
 
 

 
 
 

   

[JIRA] (JENKINS-57342) Java Array .length is incorrectly determined as a call on the array type

2019-05-06 Thread harid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57342  
 
 
  Java Array .length is incorrectly determined as a call on the array type   
 

  
 
 
 
 

 
Change By: 
 Hari Dara  
 
 
Summary: 
 Java Array .length is incorrectly determined as a call on the  array  type  
 

  
 
 
 
 

 
 
 

 
 
 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-57342) Java Array .length is incorrectly determined as a call on the type

2019-05-06 Thread harid...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57342  
 
 
  Java Array .length is incorrectly determined as a call on the type   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 script-security-plugin  
 
 
Created: 
 2019-05-06 14:26  
 
 
Environment: 
 Jenkins ver. 2.89.3  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Hari Dara  
 

  
 
 
 
 

 
 When .length is called on, an array (say, [Ljava.lang.String; ), it is treated as a call on String itself and caused the below error: 

 
No such field found: field java.lang.String length. Administrators can decide whether to approve or reject this signature.  

   The workaround is to convert the array to list and use .size(), but this becomes an ugly workaround if it needs to be converted only for this purpose (i.e., the working type needs to be an array for some reason). Here is a sample pipeline code to show this issue in action: 

 
pipeline {
agent "any"stages {
stage('Init') {
steps {
script {
echo "a b\nb\nc d\n".split("\n").collect {it.split()}.findAll {it.length == 2}
}
}
}
}
}  

 If you simply make the below change, it will start working: 
  

[JIRA] (JENKINS-57340) Trigger build with branch name as a parameter not working

2019-05-06 Thread v352...@nwytg.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 v352179 nwytg commented on  JENKINS-57340  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Trigger build with branch name as a parameter not working   
 

  
 
 
 
 

 
 We set the BRANCH as specified  

 

// Use BRANCH as a variable inside a groovy string
checkout([ $class: 'GitSCM', 
 branches: [[name: "${BRANCH}"]], 
 extensions: [[$class: 'LocalBranch', localBranch: "${BRANCH}"]]]) 

   Now the behavior is a little-bit different, Whenever we build the develop branch manually, the trigger on every commit to develop is working and the job can run also automatically on every commit to develop branch, But once we manually build another branch i.e release/* or feature/* the trigger stop working. When we again build the develop branch manually, the trigger again start working.   Looks like the trigger is influenced by the last build branch is there a reason for this behavior ?    
 

  
 
 
 
 

 
 
 

 
 
 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-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)

2019-05-06 Thread fjfernan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández commented on  JENKINS-49588  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)   
 

  
 
 
 
 

 
 Issue already fixed in 2.166  
 

  
 
 
 
 

 
 
 

 
 
 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-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)

2019-05-06 Thread fjfernan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández updated  JENKINS-49588  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49588  
 
 
  java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)   
 

  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


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

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Labels: 
 java11-devtools-compatibility  
 

  
 
 
 
 

 
 
 

 
 
 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-48825) EC2 Node pem Permmissions incorrect

2019-05-06 Thread ashwini.y.lan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashwini L commented on  JENKINS-48825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Node pem Permmissions incorrect   
 

  
 
 
 
 

 
 Even I am facing the same issue.  I am unable to launch ubuntu EC2 instance using EC2 plugin from window machine. Getting error "Warning: Identity file C:\Windows\TEMP\ec2_471045675295473131.pem not accessible: No such file or directory. ubuntu@'public ip address': Permission denied (publickey)."  
 

  
 
 
 
 

 
 
 

 
 
 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-48825) EC2 Node pem Permmissions incorrect

2019-05-06 Thread ashwini.y.lan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ashwini L edited a comment on  JENKINS-48825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Node pem Permmissions incorrect   
 

  
 
 
 
 

 
 Even I am facing the same issue. I am unable to launch ubuntu EC2 instance using EC2 plugin from window machine. Getting error "Warning: Identity file C:\Windows\TEMP\ec2_471045675295473131.pem not accessible: No such file or directory.ubuntu@'public ip address': Permission denied (publickey)." Please help me in resolving this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56975) writeMavenPom / java.lang.ClassCastException when adding a new plugin

2019-05-06 Thread kethud...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 alperen kethudaoğlu commented on  JENKINS-56975  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: writeMavenPom / java.lang.ClassCastException when adding a new plugin   
 

  
 
 
 
 

 
 I have a similar problam;   My code as below ; stage("StaticAnalysis"){  steps{  script { Plugin p= new Plugin(); p.setGroupId("org.apache.maven.plugins"); p.setArtifactId("maven-pmd-plugin"); p.setVersion("3.12.0"); def pom= readMavenPom file: '' pom.getBuild().getPlugins().add(p); writeMavenPom(pom); }   The result of the executed pipeline as below   [Pipeline] End of Pipelinejava.lang.ClassCastException: org.apache.maven.model.Plugin cannot be cast to org.apache.maven.model.Plugin at org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeBuild(MavenXpp3Writer.java:343) at org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeModel(MavenXpp3Writer.java:1134) at org.apache.maven.model.io.xpp3.MavenXpp3Writer.write(MavenXpp3Writer.java:134) at org.jenkinsci.plugins.pipeline.utility.steps.maven.WriteMavenPomStep$Execution.run(WriteMavenPomStep.java:160) at org.jenkinsci.plugins.pipeline.utility.steps.maven.WriteMavenPomStep$Execution.run(WriteMavenPomStep.java:130) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)  
 

  
 
 
 
 

 
 
 

 
 
 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-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 The Jenkins.io "[Create a plugin|https://jenkins.io/doc/developer/tutorial/create/]" tutorial uses the maven archetype to generate the "HelloWorld" plugin.  The resulting plugin won't compile with Java 11 because it is configured with {{java.version=7}}, {{jenkins.version=2.7.3}} and {{parent pom=3.4}}.  Since Jenkins officially supports Java 8 and Java 11, the archetype should be updated to support Java 8 and Java 11 compilation.It should be configured with {{java.version=8}}, {{jenkins.version=2.164.1}} and {{parent pom=3.43}} so that the resulting plugin can be compiled with either Java 8 or Java 11.The example page also shows the wrong set of choices available when generating the archetype.{noformat}[INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)Choose archetype:1: remote -> io.jenkins.archetypes:empty-plugin (-)2: remote -> io.jenkins.archetypes:hello-world-plugin (Skeleton of a Jenkins plugin with a POM and an example build step.)3: remote -> io.jenkins.archetypes:global-configuration-plugin (Skeleton of a Jenkins plugin with a POM and an example piece of global configuration.)4: remote -> io.jenkins.archetypes:global-shared-library (Uses the Jenkins Pipeline Unit mock library to test the usage of a Global Shared Library)5: remote -> io.jenkins.archetypes:scripted-pipeline (Uses the Jenkins Pipeline Unit mock library to test the logic inside a Pipeline script.)Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): : 2Choose io.jenkins.archetypes:hello-world-plugin version:1: 1.12: 1.23: 1.34: 1.4Choose a number: 4: 4[INFO] Using property: groupId = unusedDefine value for property 'artifactId': demoDefine value for property 'version' 1.0-SNAPSHOT: :[INFO] Using property: package = io.jenkins.plugins.sampleConfirm properties configuration:groupId: unusedartifactId: demoversion: 1.0-SNAPSHOTpackage: io.jenkins.plugins.sample Y: : y{noformat}The tutorial should also be updated to refer to {{spotbugs}} rather than {{findbugs}}.  The project has switched static analysis to {{spotbugs}}. The preceding tutorial, "[Preparing for Plugin Development|https://jenkins.io/doc/developer/tutorial/prepare/]" should use the Java 8 download from the AdoptOpenJDK project rather than using the Oracle JDK.  Oracle JDK 8 is no longer free for commercial use, while AdoptOpenJDK is free for commercial use.  
 

  
 
 
 
 

 
 
   

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

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 Plugin archetype and tutorial do Java 7 , not  and  Java 8  or  but not  Java 11  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


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

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 The Jenkins.io "[Create a plugin|https://jenkins.io/doc/developer/tutorial/create/]" tutorial uses the maven archetype to generate the "HelloWorld" plugin.  The resulting plugin won't compile with Java 11 because it is configured with {{java.version=7}}, {{jenkins.version=2.7.3}} and {{parent pom=3.4}}.      Since Jenkins officially support Java 8 and Java 11, the archetype should be updated to support Java 8 and Java 11 compilation.   It should be configured with {{java.version=8}}, {{jenkins.version=2.164.1}} and {{parent pom=3.43}} so that the resulting plugin can be compiled with either Java 8 or Java 11.The example page also shows the wrong set of choices available when generating the archetype.{noformat}[INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)Choose archetype:1: remote -> io.jenkins.archetypes:empty-plugin (-)2: remote -> io.jenkins.archetypes:hello-world-plugin (Skeleton of a Jenkins plugin with a POM and an example build step.)3: remote -> io.jenkins.archetypes:global-configuration-plugin (Skeleton of a Jenkins plugin with a POM and an example piece of global configuration.)4: remote -> io.jenkins.archetypes:global-shared-library (Uses the Jenkins Pipeline Unit mock library to test the usage of a Global Shared Library)5: remote -> io.jenkins.archetypes:scripted-pipeline (Uses the Jenkins Pipeline Unit mock library to test the logic inside a Pipeline script.)Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): : 2Choose io.jenkins.archetypes:hello-world-plugin version:1: 1.12: 1.23: 1.34: 1.4Choose a number: 4: 4[INFO] Using property: groupId = unusedDefine value for property 'artifactId': demoDefine value for property 'version' 1.0-SNAPSHOT: :[INFO] Using property: package = io.jenkins.plugins.sampleConfirm properties configuration:groupId: unusedartifactId: demoversion: 1.0-SNAPSHOTpackage: io.jenkins.plugins.sample Y: : y{noformat}The tutorial should also be updated to refer to {{spotbugs}} rather than {{findbugs}}.  The project has switched static analysis to {{spotbugs}}.  
 

  
 
 
 
 

 
 
 

 
 

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

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 The Jenkins.io "[Create a plugin|https://jenkins.io/doc/developer/tutorial/create/]" tutorial uses the maven archetype to generate the "HelloWorld" plugin.  The resulting plugin won't compile with Java 11 because it is configured with {{java.version=7}}, {{jenkins.version=2.7.3}} and {{parent pom=3.4}}.  Since Jenkins officially  support  supports  Java 8 and Java 11, the archetype should be updated to support Java 8 and Java 11 compilation.It should be configured with {{java.version=8}}, {{jenkins.version=2.164.1}} and {{parent pom=3.43}} so that the resulting plugin can be compiled with either Java 8 or Java 11.The example page also shows the wrong set of choices available when generating the archetype.{noformat}[INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)Choose archetype:1: remote -> io.jenkins.archetypes:empty-plugin (-)2: remote -> io.jenkins.archetypes:hello-world-plugin (Skeleton of a Jenkins plugin with a POM and an example build step.)3: remote -> io.jenkins.archetypes:global-configuration-plugin (Skeleton of a Jenkins plugin with a POM and an example piece of global configuration.)4: remote -> io.jenkins.archetypes:global-shared-library (Uses the Jenkins Pipeline Unit mock library to test the usage of a Global Shared Library)5: remote -> io.jenkins.archetypes:scripted-pipeline (Uses the Jenkins Pipeline Unit mock library to test the logic inside a Pipeline script.)Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): : 2Choose io.jenkins.archetypes:hello-world-plugin version:1: 1.12: 1.23: 1.34: 1.4Choose a number: 4: 4[INFO] Using property: groupId = unusedDefine value for property 'artifactId': demoDefine value for property 'version' 1.0-SNAPSHOT: :[INFO] Using property: package = io.jenkins.plugins.sampleConfirm properties configuration:groupId: unusedartifactId: demoversion: 1.0-SNAPSHOTpackage: io.jenkins.plugins.sample Y: : y{noformat}The tutorial should also be updated to refer to {{spotbugs}} rather than {{findbugs}}.  The project has switched static analysis to {{spotbugs}}.  
 

  
 
 
 
 

 
 
 

 
 
   

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

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


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 The Jenkins.io "[Create a plugin|https://jenkins.io/doc/developer/tutorial/create/]" tutorial uses the maven archetype to generate the "HelloWorld" plugin.  The resulting plugin won't compile with Java 11 because it is configured with {{java.version=7}}, {{jenkins.version=2.7.3}} and {{parent pom=3.4}}.  It should be configured with {{java.version=8}}, {{jenkins.version=2.164.1}} and {{parent pom=3.43}} so that the resulting plugin can be compiled with either Java 8 or Java 11.The example page also shows the wrong set of choices available when generating the archetype.{noformat}[INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0)Choose archetype:1: remote -> io.jenkins.archetypes:empty-plugin (-)2: remote -> io.jenkins.archetypes:hello-world-plugin (Skeleton of a Jenkins plugin with a POM and an example build step.)3: remote -> io.jenkins.archetypes:global-configuration-plugin (Skeleton of a Jenkins plugin with a POM and an example piece of global configuration.)4: remote -> io.jenkins.archetypes:global-shared-library (Uses the Jenkins Pipeline Unit mock library to test the usage of a Global Shared Library)5: remote -> io.jenkins.archetypes:scripted-pipeline (Uses the Jenkins Pipeline Unit mock library to test the logic inside a Pipeline script.)Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): : 2Choose io.jenkins.archetypes:hello-world-plugin version:1: 1.12: 1.23: 1.34: 1.4Choose a number: 4: 4[INFO] Using property: groupId = unusedDefine value for property 'artifactId': demoDefine value for property 'version' 1.0-SNAPSHOT: :[INFO] Using property: package = io.jenkins.plugins.sampleConfirm properties configuration:groupId: unusedartifactId: demoversion: 1.0-SNAPSHOTpackage: io.jenkins.plugins.sample Y: : y{noformat} The tutorial should also be updated to refer to {{spotbugs}} rather than {{findbugs}}.  The project has switched static analysis to {{spotbugs}}.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-57334) "Run on planned host" from Build section not working

2019-05-06 Thread gsur...@ups.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Govind Sureka commented on  JENKINS-57334  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Run on planned host" from Build section not working   
 

  
 
 
 
 

 
 Here is the Console output Started by user unknown or anonymous Building on master in workspace D:\X\Jenkins_Home\workspace\TEST_Test [TEST_Test] $ D:\XXJ\Jenkins_Home\workspace\TEST_Test\HpToolsLauncher.exe -paramfile props06052019040802183.txt "Started..." Timeout is set to: -1 Run mode is set to: RUN_PLANNED_HOST  Starting test set execution Test set name: XXX, Test set id: 1402 "Number of tests in set: "1 Test 1: [1]0TEST_test will run on host:  log4net:ERROR [RollingFileAppender] Unable to acquire lock on file D:\XXJ\Jenkins_Home\workspace\TEST_Test\. Could not find a part of the path 'D:\XXJ\Jenkins_Home\workspace\TEST_Test\'. Problem while running TestSet: Exception from HRESULT: 0x80040459 "Scheduler started at:06/05/2019 04:08:05 --- Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, Double timeout, QcRunMode runMode, String runHost) at HpToolsLauncher.AlmTestSetsRunner.Run() at HpToolsLauncher.Launcher.RunTests(IAssetRunner runner, String resultsFile) at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args) FATAL: HTTP host may not be null java.lang.IllegalArgumentException: HTTP host may not be null at org.apache.http.util.Args.notNull(Args.java:54) at org.apache.http.nio.client.methods.HttpAsyncMethods.create(HttpAsyncMethods.java:72) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:76) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:92) at com.ibm.devops.connect.CloudPublisher.postToSyncAPI(CloudPublisher.java:219) at com.ibm.devops.connect.CloudPublisher.uploadJobStatus(CloudPublisher.java:159) at com.ibm.devops.connect.CloudBuildStepListener.finished(CloudBuildStepListener.java:57) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1810) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
   

  1   2   >