date:20181002

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-44869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Activity tabs Run id column should expand to fit value   
 

  
 
 
 
 

 
 James Dumay Any updates on this issue? I claim this little issue is really, really worth being solved, or at least a workaround could be potentially very cheap to implement? Naive workaround for calculation of table column width: 

 

int width = Math.max(, Math.min(maximumWidth that should not be exceeded which may be ~250>, for full display of latest build display name because that might be the biggest build number or in my use case just about as long as all the others>) 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53871) Consider waiting for lock in "timings" and build status overview?

Title: Message Title

Reinhold Füreder updated an issue

Jenkins / JENKINS-53871

Consider waiting for lock in "timings" and build status overview?

Change By:
Reinhold Füreder

When looking over build history or old builds I saw build durations of e.g. 21min, although I know it typically lasts about 6 to 12min. It turned out that there was a ~8min waiting period for a resource lock...The classic UI's "Stage View" actually shows this waiting in small: !image-2018-10-02-10-28-42-364.png|thumbnail! However I was wondering if this should be also reflected here: * !image-2018-10-02-10-29-49-549.png|thumbnail! * !image-2018-10-02-10-30-50-008.png|thumbnail! Log snippet:{code:java}...[Pipeline] lock10:00:30 Trying to acquire lock on [Label: PhpStorm, Quantity: 1]10:00:30 Found 0 available resource(s). Waiting for correct amount: 1.10:00:30 [Label: PhpStorm, Quantity: 1] is locked, waiting...10:08:31 Lock acquired on [Label: PhpStorm, Quantity: 1][Pipeline] {... {code}

Add Comment

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

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

[JIRA] (JENKINS-53881) aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs

2018-10-02 Thread malu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Grochowski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53881  
 
 
  aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Rik Turnbull  
 
 
Components: 
 aws-parameter-store-plugin  
 
 
Created: 
 2018-10-03 03:50  
 
 
Priority: 
  Major  
 
 
Reporter: 
 David Grochowski  
 

  
 
 
 
 

 
 When upgrading aws-parameter-store-plugin from 1.1.0 to 1.2.0, existing pipeline jobs break due to the addition of the namePrefixes parameter (specifically: Missing required parameter: "namePrefixes"). The parameter should be optional and all prefixes should be matched by default.   The change was introduced in https://github.com/jenkinsci/aws-parameter-store-plugin/pull/1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michel Zanini edited a comment on  JENKINS-53876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
 Its */bin/bash*.You are right, its doing the escaping , so . So  I don't  know  what it is then. Because it works ok on 1.39 and  if  I leave the same params and upgrade to 1.40  and  it stops working,  if  I move back to 1.39 it works again.What happens is that as soon as the  *  java -jar *  command is run, the slave is terminated.When I am tailing the logs on the web UI, because the slave just gets terminated immediately, I see a  *  404 error * .Logs do not show why it terminates, I was assuming  this was  the  change, maybe  reason to be the *cd tmp*. Maybe  I can checkout the project, revert that change and try with this and see if it fixes... I will attach some screen shots.!Screen Shot 2018-10-02 at 22.33.42.png|thumbnail!  !Screen Shot 2018-10-02 at 22.34.39.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michel Zanini updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53876  
 
 
  Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
Change By: 
 Michel Zanini  
 
 
Attachment: 
 Screen Shot 2018-10-02 at 22.33.42.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-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michel Zanini updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53876  
 
 
  Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
Change By: 
 Michel Zanini  
 
 
Attachment: 
 Screen Shot 2018-10-02 at 22.34.39.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-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michel Zanini commented on  JENKINS-53876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
 Its /bin/bash. You are right, its doing the escaping, so I don't what it is then. Because it works ok on 1.39 and I leave the same params and upgrade to 1.40 and it stops working, I move back to 1.39 it works again. What happens is that as soon as the java -jar command is run, the slave is terminated. When I am tailing the logs on the web UI, because the slave just gets terminated immediately, I see a 404 error. Logs do not show why it terminates, I was assuming this was the change, maybe I can checkout the project, revert that change and try with this and see if it fixes...  I will attach some screen shots.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53832) Jenkins 2.138.1 unable to start on CentOS 5

2018-10-02 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-53832  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins 2.138.1 unable to start on CentOS 5   
 

  
 
 
 
 

 
 https://en.wikipedia.org/wiki/CentOS#End-of-support_schedule Is it really newsworthy that Jenkins does not support an OS release that hasn't been supported by its vendor/project for 18 months? I'm not sure, but feel free to add it to our docs. No need to ping me here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53841) no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi started work on  JENKINS-53841  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 suren pi  
 
 
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-53841) no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi updated  JENKINS-53841  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53841  
 
 
  no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep   
 

  
 
 
 
 

 
Change By: 
 suren pi  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53841) no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi updated  JENKINS-53841  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53841  
 
 
  no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep   
 

  
 
 
 
 

 
Change By: 
 suren pi  
 
 
Status: 
 Resolved Fixed but Unreleased  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53841) no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53841  
 
 
  no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep   
 

  
 
 
 
 

 
Change By: 
 suren pi  
 
 
URL: 
 https://github.com/jenkinsci/badge-plugin/pull/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-53841) no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi updated  JENKINS-53841  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53841  
 
 
  no public field ‘link’ (or getter method) found in class com.jenkinsci.plugins.badge.dsl.AddShortTextStep   
 

  
 
 
 
 

 
Change By: 
 suren pi  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 https://github.com/jenkinsci/badge-plugin/pull/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-22700) Enhance plugin to capture and report errors like it does warnings

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-22700  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-22700  
 
 
  Enhance plugin to capture and report errors like it does warnings   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-45572) GitBlamer does not work if git workspace is in subfolder

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-45572  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm not sure if I'm missing something but one of my jobs works quite well in a sub directory now. (will be part of 5.0.0 beta 2).   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45572  
 
 
  GitBlamer does not work if git workspace is in subfolder   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-45750) GitBlamer causes OutOfMemoryError

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-45750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Should work better in the upcoming beta 2 of the warnings plugin. (Maybe upgrading the Git and Git client plugins to the latest betas will also help, since they now use EGit 5.1).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45750  
 
 
  GitBlamer causes OutOfMemoryError   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-47269) Option to disable logging doesn't work Git Blamer

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-47269  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47269  
 
 
  Option to disable logging doesn't work Git Blamer   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-47268) Warnings contain no filename

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-47268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47268  
 
 
  Warnings contain no filename   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-48302) gitblamer failed to parse relative file path

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-48302  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Absolute path resolving should be more robust in the latest beta.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48302  
 
 
  gitblamer failed to parse relative file path   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-49319) Old Prototype library causes problems with modern UI frameworks

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-49319  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Old Prototype library causes problems with modern UI frameworks
 

  
 
 
 
 

 
 Hmm, seems to be easier to switch a UI library in my plugins rather then replace this library in core Jenkins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49319) Old Prototype library causes problems with modern UI frameworks

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49319  
 
 
  Old Prototype library causes problems with modern UI frameworks
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Assignee: 
 Ulli Hafner  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-50065) Unit tests, Integration Tests and Acceptance Tests for Static Analysis Suite 2.0

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50065  
 
 
  Unit tests, Integration Tests and Acceptance Tests for Static Analysis Suite 2.0   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open 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-52755) Add view columns that show the number of issues

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52755  
 
 
  Add view columns that show the number of issues   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Summary: 
 Add  view  columns that show the number of issues  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53684) Provide links for all tabs in details page

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-53684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Will be part of beta2.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53684  
 
 
  Provide links for all tabs in details page   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-51394) Add Perforce Job (p4 fix) link for submitting/publishing

2018-10-02 Thread barn...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Barnish commented on  JENKINS-51394  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add Perforce Job (p4 fix) link for submitting/publishing   
 

  
 
 
 
 

 
 We would also like to see this feature implemented for both freestyle and pipeline jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-51394) Add Perforce Job (p4 fix) link for submitting/publishing

2018-10-02 Thread barn...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Barnish assigned an issue to Paul Allen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51394  
 
 
  Add Perforce Job (p4 fix) link for submitting/publishing   
 

  
 
 
 
 

 
Change By: 
 Andrew Barnish  
 
 
Assignee: 
 Paul Allen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53652) InterruptedException during slave workspace groovy clean up pipeline

2018-10-02 Thread jenk...@mrozekma.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mrozek commented on  JENKINS-53652  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: InterruptedException during slave workspace groovy clean up pipeline   
 

  
 
 
 
 

 
 I have the same problem while doing the same kind of operation. I ended up just wrapping the deleteRecursive in a try/catch block to catch and ignore the InterruptedException, with a loop around that to keep trying until it works. It makes progress before getting interrupted each time, so eventually everything gets deleted, but for large directories it can get interrupted dozens of times  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-47077) "Periodically if not otherwise run" interval does not trigger index scan

2018-10-02 Thread mslatt...@misoenergy.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Slattery commented on  JENKINS-47077  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Periodically if not otherwise run" interval does not trigger index scan   
 

  
 
 
 
 

 
 As a workaround, we created a pipeline job as follows: 

 

node {
   Jenkins.instance.getItemByFullName('My Job').indexing.run()
   Jenkins.instance.getItemByFullName('Your Job').indexing.run()
}
 

 I set it to trigger to build periodically, every two minutes: H/2 * * * * But, I had to do script approvals.  This is temporary for us until this bug gets fixed, after which I'll remove the script approvals.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-2111  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-2111  
 
 
  removing a job (including multibranch/org folder branches/repos) does not remove the workspace   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40

2018-10-02 Thread fabrizio.manfr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-53879  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 workers terminated before connection can be established, only on v1.40   
 

  
 
 
 
 

 
 The revert is ongoing, root cause is under investigation, it is not happen with all jenkins version. Can you upload on the connection log of the slave to  JENKINS-53876 What is the operating system of the slave node ? and what is the default shell of the user in the slave ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53880) Build step trigger pipeline job hangs when master node set to zero executors

2018-10-02 Thread totoroliu1...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53880  
 
 
  Build step trigger pipeline job hangs when master node set to zero executors   
 

  
 
 
 
 

 
Change By: 
 Rick Liu  
 

  
 
 
 
 

 
 When master node is set to zero exectuors,a matrix job triggers a pipeline job (with blocking) doesn't work.From Matrix job console, it would show:{{Waiting for the completion of "".}}But the pipeline job doesn't start and it doesn't have queue jobs either.It's just like the trigger was not sent,but the matrix job is waiting for return indefinitely.Only from Jenkins master jenkins.log, you can see:bq. Oct 02, 2018 1:27:29 PM hudson.model.Executor resetWorkUnitbq. WARNING: Executor #-1 for master grabbed hudson.model.queue.WorkUnit@2cbaff74[work=PIPELINE_JOB] from queue but master went off-line before the task's worker thread started. No termination trace available. Jenkins either should queued the job to wait for master executors to be available,or should returns trigger error back to the matrix jobinstead of letting the job wait for the return indefinitely.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53880) Build step trigger pipeline job hangs when master node set to zero executors

2018-10-02 Thread totoroliu1...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53880  
 
 
  Build step trigger pipeline job hangs when master node set to zero executors   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-10-02 20:57  
 
 
Environment: 
 Ubuntu 16.04  Jenkins Core v2.121.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Rick Liu  
 

  
 
 
 
 

 
 When master node is set to zero exectuors, a matrix job triggers a pipeline job (with blocking) doesn't work. From Matrix job console, it would show: Waiting for the completion of "". But the pipeline job doesn't start and it doesn't have queue jobs either. It's just like the trigger was not sent, but the matrix job is waiting for return indefinitely. Only from Jenkins master jenkins.log, you can see: 

Oct 02, 2018 1:27:29 PM hudson.model.Executor resetWorkUnit
 

WARNING: Executor #-1 for master grabbed hudson.model.queue.WorkUnit@2cbaff74[work=PIPELINE_JOB] from queue but master went off-line before the task's worker thread started. No termination trace available.

[JIRA] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs

2018-10-02 Thread mr.danielya...@yahoo.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Dan commented on  JENKINS-32866  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Log Parser Plugin does not parse Pipeline console outputs   
 

  
 
 
 
 

 
 Hi! Thx for answer. her is cod pipeline  { agent \{ label 'master'} triggers  { pollSCM('* * * * *') }  environment  { ANSIBLE_CONFIG = "Jenkins-LTS/ansible.cfg" }  stages{ stage('Checkout') { steps  { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'Jenkins-LTS'], [$class: 'WipeWorkspace']], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'fd864bf0-5e33-4cf1-a130-67ac2c22bf17', url: 'https://github.com/MRDO5/jenkins-lts.git']]]) }  } stage('Deploy') { parallel { stage('Syntax check') { steps { ansiColor('gnome-terminal')  { ansiblePlaybook become: true, colorized: true, credentialsId: '7980492c-7fa3-41b6-9c8e-b44d3f7ce236', extras: '--syntax-check' , inventory: 'Jenkins-LTS/inventory', playbook: 'Jenkins-LTS/main.yml' }  } } stage('Check provision for virtual machines') { steps { ansiColor('gnome-terminal')  { ansiblePlaybook become: true, colorized: true, credentialsId: '7980492c-7fa3-41b6-9c8e-b44d3f7ce236', installation: 'ansible', inventory: 'Jenkins-LTS/inventory', playbook: 'Jenkins-LTS/main.yml' }  } } } } stage('Log-parser') { steps  { logparser([$class: 'LogParserPublisher', parsingRulesPath: '/var/lib/jenkins/minimal-rules', useProjectRule: false, failBuildOnError: true, unstableOnWarning: false, Logparsergraphs: true ]) }  } }    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector

2018-10-02 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-40109  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixes released in Pipeline: Groovy version 2.57 and Pipeline: Shared Groovy Libraries version 2.12. Thanks Rudolf-Walter Kiss-Szakacs!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40109  
 
 
  Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 Pipeline: Groovy 2.57 and Pipeline: Shared Groovy Libraries 2.12  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40

2018-10-02 Thread siro...@uchicago.edu (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Rosen closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53879  
 
 
  EC2 workers terminated before connection can be established, only on v1.40   
 

  
 
 
 
 

 
Change By: 
 Stephen Rosen  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40

2018-10-02 Thread siro...@uchicago.edu (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Rosen commented on  JENKINS-53879  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 workers terminated before connection can be established, only on v1.40   
 

  
 
 
 
 

 
 It very well could be a duplicate; apologies if so. I didn't find that issue when looking at open issues, probably because I was looking for things about "premature termination" not "failure to connect".   Let's mark it as a dup and close, and if I find it persists after that bug is fixed, I'll reopen.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-39194) Honor SCM checkout retry count from CpsScmFlowDefinition

2018-10-02 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-39194  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39194  
 
 
  Honor SCM checkout retry count from CpsScmFlowDefinition   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 Pipeline Groovy 2.44  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40

2018-10-02 Thread gr...@yandex.ru (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Peace commented on  JENKINS-53879  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 workers terminated before connection can be established, only on v1.40   
 

  
 
 
 
 

 
 Isn't it a duplicate of JENKINS-53876?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-39203) All stages show up as UNSTABLE when only one stage should

2018-10-02 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Is any progress being made on this issue?I don't want to sound impatient but this is a pretty seriously debilitating issue!  Way beyond even just the graphical display of an entire pipeline of stages and steps looking like it's unstable, this issue completely defeats any and all \{{post { }}} block processing after the first stage failure.  Every stage block from the point of a failed stage on gets processed as unstable, preventing one from doing any kind of finer (than entire pipeline) granulated processing and/or reporting of pipelines.I now personally believe this issue to be higher than *Critical* and believe it to be an outright *Blocker* as it makes much of the usefulness of Pipelines void.  It makes me want to break my pipeline down into separate free-style jobs just so that I can get meaningful reporting and processing of jobs based on whether they are successful, unstable, failed, etc.  A bug serious enough to make one want to abandon Pipelines is by definition a *Blocker* to Pipelines. So, can we get a status update on this?  Is anyone actively working on it or has it been thrown back on the pile?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-39203) All stages show up as UNSTABLE when only one stage should

2018-10-02 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell edited a comment on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Is any progress being made on this issue?I don't want to sound impatient but this is a pretty seriously debilitating issue!  Way beyond even just the graphical display of an entire pipeline of stages and steps looking like it's unstable, this issue completely defeats any and all  \  {{post  \ { }}} block processing after the first stage failure.  Every stage block from the point of a failed stage on gets processed as unstable, preventing one from doing any kind of finer (than entire pipeline) granulated processing and/or reporting of pipelines.I now personally believe this issue to be higher than *Critical* and believe it to be an outright *Blocker* as it makes much of the usefulness of Pipelines void.  It makes me want to break my pipeline down into separate free-style jobs just so that I can get meaningful reporting and processing of jobs based on whether they are successful, unstable, failed, etc.  A bug serious enough to make one  wanting  want  to abandon Pipelines is by definition a *Blocker* to Pipelines.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-39203) All stages show up as UNSTABLE when only one stage should

2018-10-02 Thread brian.murr...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-39203  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: All stages show up as UNSTABLE when only one stage should   
 

  
 
 
 
 

 
 Is any progress being made on this issue? I don't want to sound impatient but this is a pretty seriously debilitating issue!  Way beyond even just the graphical display of an entire pipeline of stages and steps looking like it's unstable, this issue completely defeats any and all {{post { }}} block processing after the first stage failure.  Every stage block from the point of a failed stage on gets processed as unstable, preventing one from doing any kind of finer (than entire pipeline) granulated processing and/or reporting of pipelines. I now personally believe this issue to be higher than Critical and believe it to be an outright Blocker as it makes much of the usefulness of Pipelines void.  It makes me want to break my pipeline down into separate free-style jobs just so that I can get meaningful reporting and processing of jobs based on whether they are successful, unstable, failed, etc.  A bug serious enough to make one wanting to abandon Pipelines is by definition a Blocker to Pipelines.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53878) Can not script AWS code pipeline through Job dsl plugin

2018-10-02 Thread bhagyashri.sarbhu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bhagyashri Sarbhukan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53878  
 
 
  Can not script AWS code pipeline through Job dsl plugin   
 

  
 
 
 
 

 
Change By: 
 Bhagyashri Sarbhukan  
 

  
 
 
 
 

 
 There is no Groovy explicit support for the AWS code pipeline, however Job DSL plugin manages to generate  dynamically  some from Java,https://<>/plugin/job-dsl/api-viewer/index.html#plugin/aws-codepipeline The generated API documentation is only for "[awsCodePipelineSCM|https://tco-test-jenkins-ext-elb-195224482.eu-west-1.elb.amazonaws.com/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.ScmContext.awsCodePipelineSCM]". It however does not generate any documentation for "*awsCodePipelinePublisher*".  This makes the plugin unusable via Groovy DSL.I appreciate if you can share even a work around for this.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53878) Can not script AWS code pipeline through Job dsl plugin

2018-10-02 Thread bhagyashri.sarbhu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bhagyashri Sarbhukan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53878  
 
 
  Can not script AWS code pipeline through Job dsl plugin   
 

  
 
 
 
 

 
Change By: 
 Bhagyashri Sarbhukan  
 
 
Summary: 
 Can not script AWS code pipeline through  Groovy DSL  Job dsl  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-53878) Can not script AWS code pipeline through Job dsl plugin

2018-10-02 Thread bhagyashri.sarbhu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bhagyashri Sarbhukan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53878  
 
 
  Can not script AWS code pipeline through Job dsl plugin   
 

  
 
 
 
 

 
Change By: 
 Bhagyashri Sarbhukan  
 

  
 
 
 
 

 
 There is no Groovy explicit support for the AWS code pipeline, however  Groovy  Job  DSL plugin manages to generate some from Java,https://<>/plugin/job-dsl/api-viewer/index.html#plugin/aws-codepipeline The generated API documentation is only for "[awsCodePipelineSCM|https://tco-test-jenkins-ext-elb-195224482.eu-west-1.elb.amazonaws.com/plugin/job-dsl/api-viewer/index.html#method/javaposse.jobdsl.dsl.helpers.ScmContext.awsCodePipelineSCM]". It however does not generate any documentation for "*awsCodePipelinePublisher*".  This makes the plugin unusable via Groovy DSL.I appreciate if you can share even a work around for this.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53878) Can not script AWS code pipeline through Groovy DSL plugin

2018-10-02 Thread bhagyashri.sarbhu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bhagyashri Sarbhukan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53878  
 
 
  Can not script AWS code pipeline through Groovy DSL plugin   
 

  
 
 
 
 

 
Change By: 
 Bhagyashri Sarbhukan  
 
 
Component/s: 
 job-dsl-plugin  
 
 
Component/s: 
 groovy-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53879) EC2 workers terminated before connection can be established, only on v1.40

2018-10-02 Thread siro...@uchicago.edu (JIRA)

Title: Message Title

Stephen Rosen created an issue

Jenkins / JENKINS-53879

EC2 workers terminated before connection can be established, only on v1.40

Issue Type:
Bug

Assignee:
FABRIZIO MANFREDI

Components:
ec2-plugin

Created:
2018-10-02 19:34

Environment:
Jenkins ver. 2.138.1 Ubuntu 14.04

Priority:
Major

Reporter:
Stephen Rosen

I just did my monthly round of plugin upgrades and found that EC2 workers were failing to connect. Downgrading this plugin, and only this plugin, to v1.39 resolved the issue, so I'm fairly confident this is the source of the behavior. When I watched the activity, I see worker nodes spinning up, correctly, based on our various labels and job requirements. They get to the running state in EC2, but shortly thereafter (< 1 minute) they are terminated. I believe that this is happening during the guest OS boot time, as I tried polling for connections on port 22 from the master node and never got a success – and our workers are all configured to run sshd open to the master on 22. All of our nodes are configured with Launch Timeout in Seconds = 300, but this failure was very consistent and the last time I measured our launch times, they were around 3.5 minutes. If I had to venture a guess, I would say that something has changed in terms of the leniency with which nodes are treated as they start, and their boot times are being counted differently. If someone can confirm that that's what changed, I'll probably just up my timeouts to 10 minutes and walk away, but I'm not confident that would work.

[JIRA] (JENKINS-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

2018-10-02 Thread fabrizio.manfr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI edited a comment on  JENKINS-53876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
 The command line is already quoted:String launchString = computer.getSlaveCommandPrefix() + "\"" + command + "\"";I tested with Jenkins  2.121.3 and Amazon linux :ssh -o StrictHostKeyChecking=no -i /tmp/ec2_3738884817655447223.pem x...@xxx.xxx.xxx.xxx -p 22 "cd /tmp && java -jar slave.jar"and works as expected.  Are you using What is  the  shell defined for the jenkins user    in the slave node ?       
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

2018-10-02 Thread fabrizio.manfr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-53876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
 The command line is already quoted: String launchString = computer.getSlaveCommandPrefix() + "\"" + command + "\""; I tested with Jenkins  2.121.3 and Amazon linux : ssh -o StrictHostKeyChecking=no -i /tmp/ec2_3738884817655447223.pem x...@xxx.xxx.xxx.xxx -p 22 "cd /tmp && java -jar slave.jar" and works as expected.   Are you using the     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-51644) EC2 Plugin doesn't support c5d Instance Types

2018-10-02 Thread boa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Merged in https://github.com/jenkinsci/ec2-plugin/pull/280 and released in 1.40.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51644  
 
 
  EC2 Plugin doesn't support c5d Instance Types   
 

  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.40  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52021) Spot instances not filtered by template description

2018-10-02 Thread boa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker updated  JENKINS-52021  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52021  
 
 
  Spot instances not filtered by template description   
 

  
 
 
 
 

 
Change By: 
 Matt Sicker  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 1.40  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53877) sshagent + git checkout on local agent: ssh key not found

2018-10-02 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-53877  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: sshagent + git checkout on local agent: ssh key not found   
 

  
 
 
 
 

 
 I don't understand what you're trying to accomplish. Can you explain further why you're not passing a Jenkins credential to the `git` Pipeline step rather than passing an empty string as the argument to ssh-agent and then adding the default private key? Doesn't the ssh-add technique that you're using require that you place the private key into the ~/.ssh directory of each user that runs an agent? Passing a Jenkins credential will avoid that agent-specific configuration and will simplify the build script. If you truly need fine-grained control of the git command, you might choose to place the git command inside an `sh` step that is wrapped by the ssh-agent command. If you've decided that you're not using Jenkins credentials to manage credentials, you can probably just as readily decide that you won't use the git plugin to manage checkout. Note that I have not attempted the steps you've described, so I don't know if there is a way to accomplish what you're describing. I won't duplicate the bug report until later. I wanted to ask the clarifying questions before I invest the time to duplicate what you've described.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53864) CasC compatibility with Log Parser Plugin

2018-10-02 Thread nicolas.del...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas De Loof commented on  JENKINS-53864  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CasC compatibility with Log Parser Plugin   
 

  
 
 
 
 

 
 see https://github.com/jenkinsci/configuration-as-code-plugin/issues/565 for guidance on fixing 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-53864) CasC compatibility with Log Parser Plugin

2018-10-02 Thread nicolas.del...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas De Loof updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53864  
 
 
  CasC compatibility with Log Parser Plugin   
 

  
 
 
 
 

 
Change By: 
 Nicolas De Loof  
 
 
Component/s: 
 configuration-as-code-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-53748) SAML plugin skips Jenkins Proxy Configuration

2018-10-02 Thread it.carlosrod...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Rodríguez López commented on  JENKINS-53748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SAML plugin skips Jenkins Proxy Configuration
 

  
 
 
 
 

 
 Thanks Ivan Fernandez Calvo I have used this test proxy on localhost for validation. Configuring Jenkins Proxy as 127.0.0.1: 3128 

 

root@d60683407a97:/# tail /var/log/squid3/access.log
1538503645.778 5422 172.17.0.1 TCP_MISS/200 22391 CONNECT federation.basf.com:443 - HIER_DIRECT/141.6.3.178 -
1538503662.775 5408 172.17.0.1 TCP_MISS/200 22391 CONNECT federation.basf.com:443 - HIER_DIRECT/141.6.3.178 -
 

 Note that running Jenkins as 

 

501 10306 10168   0  8:22PM ttys0020:27.06 /usr/bin/java -Djenkins.model.Jenkins.slaveAgentPort=24438 -Djenkins.install.runSetupWizard=false -Djenkins.model.Jenkins.logStartupPerformance=true -Dhudson.TcpSlaveAgentListener.hostName=oss.example.crl -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=3128 -Djava.security.egd=file:/dev/./urandom -Xdebug -Xrunjdwp:transport=dt_socket,suspend=n,server=y,address=0.0.0.0:8194 -Xms256m -Dhudson.DNSMultiCast.disabled=true -jar /Users/carlosrodlop/Support/labs/jenkins-home-oss/jenkins.war --httpPort=8184 --httpListenAddress=0.0.0.0
 

 It is also working as expected, so you were right too by using a mock proxy out the range `999.999.999.999`  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53878) Can not script AWS code pipeline through Groovy DSL plugin

2018-10-02 Thread bhagyashri.sarbhu...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bhagyashri Sarbhukan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53878  
 
 
  Can not script AWS code pipeline through Groovy DSL plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David Nasi  
 
 
Components: 
 aws-codepipeline-plugin, groovy-plugin  
 
 
Created: 
 2018-10-02 17:36  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Bhagyashri Sarbhukan  
 

  
 
 
 
 

 
 There is no Groovy explicit support for the AWS code pipeline, however Groovy DSL plugin manages to generate some from Java, https://<>/plugin/job-dsl/api-viewer/index.html#plugin/aws-codepipeline   The generated API documentation is only for "awsCodePipelineSCM". It however does not generate any documentation for "awsCodePipelinePublisher".  This makes the plugin unusable via Groovy DSL. I appreciate if you can share even a work around for this.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-53877) sshagent + git checkout on local agent: ssh key not found

2018-10-02 Thread tho...@deepomatic.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Riccardi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53877  
 
 
  sshagent + git checkout on local agent: ssh key not found   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin, ssh-agent-plugin  
 
 
Created: 
 2018-10-02 17:24  
 
 
Environment: 
 Jenkins 2.138.1 (from docker)  plugins up-to-date as of 2018-10-02 17:00:00 UTC  
 
 
Labels: 
 sshagent git checkout  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Thomas Riccardi  
 

  
 
 
 
 

 
 sshagent + git checkout doesn't seem to work: the `SSH_AUTH_SOCK` env var disappears from the git process environment, and thus the ssh-agent is not available to ssh started by git...   Scenario: 
 
create a ssh key credentials `ssh-key` 
create a pipeline job with Jenkinsfile: 

 

node {
stage('Preparation') {
sshagent (['']) {
sh 'printenv'
sh 'ssh-add -l'
git 'g...@github.com:foo/bar.git'
}
}
}
 

 
run created job 
 Expected result: ssh started by git finds the correct ssh key via the

[JIRA] (JENKINS-53873) events listeners failures cause build to fail

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yuri Guller closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53873  
 
 
  events listeners failures cause build to fail   
 

  
 
 
 
 

 
Change By: 
 Yuri Guller  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53873) events listeners failures cause build to fail

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yuri Guller resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 All Octane's related logic, which is running on the Jenkins' main events thread, was wrapped in exception catch to prevent interfering with the build continuity.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53873  
 
 
  events listeners failures cause build to fail   
 

  
 
 
 
 

 
Change By: 
 Yuri Guller  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53858) Deadlock on EC2 resources

2018-10-02 Thread fabrizio.manfr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI commented on  JENKINS-53858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on EC2 resources   
 

  
 
 
 
 

 
 Yes, with the 1.40 should not needed anymore the pre warming the instances, the plugin is able to raise  40 nodes per minutes (if you don't reach the AWS api limits). Anyway I started to investigate the deadlock.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53397) ChannelClosedException when using kafka nodes

2018-10-02 Thread phamvutua...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pham Vu Tuan commented on  JENKINS-53397  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ChannelClosedException when using kafka nodes   
 

  
 
 
 
 

 
 Btw, are you using this remoting-kafka-plugin in production? Federico Naum  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53858) Deadlock on EC2 resources

2018-10-02 Thread fabrizio.manfr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 FABRIZIO MANFREDI started work on  JENKINS-53858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 FABRIZIO MANFREDI  
 
 
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-53397) ChannelClosedException when using kafka nodes

2018-10-02 Thread phamvutua...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pham Vu Tuan commented on  JENKINS-53397  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ChannelClosedException when using kafka nodes   
 

  
 
 
 
 

 
 Hi Jeff Thompson, Im getting this error log when connecting master with kafka agent in remoting 3.26, which doesn't happen when I use 3.25. 

 

java.util.concurrent.CancellationExceptionjava.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at io.jenkins.plugins.remotingkafka.KafkaComputerLauncher.launch(KafkaComputerLauncher.java:119) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) 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)
Oct 02, 2018 3:28:58 PM hudson.slaves.ChannelPinger installSEVERE: Failed to set up a ping for testjava.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.Channel.call(Channel.java:954) at hudson.slaves.ChannelPinger.install(ChannelPinger.java:112) at hudson.slaves.ChannelPinger.preOnline(ChannelPinger.java:95) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:660) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:465) at io.jenkins.plugins.remotingkafka.KafkaComputerLauncher$1.call(KafkaComputerLauncher.java:88) at io.jenkins.plugins.remotingkafka.KafkaComputerLauncher$1.call(KafkaComputerLauncher.java:74) 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)
 

 Is there any special changed thing in 3.26 related to this? And cc Oleg Nenashev, I still can connect Kafka agent to master and do the build when having this exception, seem like another plugin issue   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michel Zanini updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53876  
 
 
  Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
Change By: 
 Michel Zanini  
 
 
Attachment: 
 Screen Shot 2018-10-02 at 12.38.58.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-53876) Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michel Zanini created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53876  
 
 
  Linux slaves are not starting anymore after upgrade to 1.40 of ec2-plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 FABRIZIO MANFREDI  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2018-10-02 15:37  
 
 
Environment: 
 Master and slave are on Amazon Linux, Jenkins 2.144 and ec2-plugin on 1.40  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Michel Zanini  
 

  
 
 
 
 

 
 The change below has introduced a major bug: https://github.com/jenkinsci/ec2-plugin/pull/276 Now slaves are not starting anymore on Linux. The problem relies on changing the command from: java -jar /tmp/slave.jar to cd /tmp && java -jar slave.jar. SSH needs the command to be escaped when using &&. Please read https://unix.stackexchange.com/questions/80821/why-does-cd-command-not-work-via-ssh. Another solution could potentially be run different commands for linux / windows (if that's possible). Or otherwise we need to find something that works for both. More details can be found in comments here: https://github.com/jenkinsci/ec2-plugin/pull/276 Reverting back to 1.39 has solved the issue.

[JIRA] (JENKINS-53875) JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov edited a comment on  JENKINS-53875  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows   
 

  
 
 
 
 

 
 Sorry, I just realized that the bat file is part of groovy, not groovy-plugin (thought it was a temporary file).  I'll  [  bug them next |https  : //issues.apache.org/jira/browse/GROOVY-8821] : )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53875) JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53875  
 
 
  JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows   
 

  
 
 
 
 

 
Change By: 
 Alexander Komarov  
 
 
Status: 
 Reopened 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-53875) JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov updated  JENKINS-53875  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53875  
 
 
  JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows   
 

  
 
 
 
 

 
Change By: 
 Alexander Komarov  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53875) JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov updated  JENKINS-53875  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Sorry, I just realized that the bat file is part of groovy, not groovy-plugin (thought it was a temporary file). I'll bug them next   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53875  
 
 
  JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows   
 

  
 
 
 
 

 
Change By: 
 Alexander Komarov  
 
 
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-53875) JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53875  
 
 
  JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows   
 

  
 
 
 
 

 
Change By: 
 Alexander Komarov  
 
 
Environment: 
 Jenkins 2.144Groovy  plugin  2.0Docker  plugin  1.1.5 Windows 2016 with Docker 17.06.2-ee-16  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53875) JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53875  
 
 
  JAVA_HOME is set to an invalid directory when using Groovy in Docker on Windows   
 

  
 
 
 
 

 
Change By: 
 Alexander Komarov  
 
 
Summary: 
 JAVA_HOME is set to an invalid directory when using Groovy  and  in  Docker on Windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-46725) [JDK9] Detach JNR-Posix from core

2018-10-02 Thread dnusb...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-46725  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [JDK9] Detach JNR-Posix from core   
 

  
 
 
 
 

 
 Oleg Nenashev Even though we updated to the latest version of JNR to fix some warnings at startup, I think we still want to detach this at some point, so maybe it makes sense to leave the ticket open?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53875) JAVA_HOME is set to an invalid directory when using Groovy and Docker on Windows

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53875  
 
 
  JAVA_HOME is set to an invalid directory when using Groovy and Docker on Windows   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 vjuranek  
 
 
Components: 
 groovy-plugin  
 
 
Created: 
 2018-10-02 14:48  
 
 
Environment: 
 Jenkins 2.144  Groovy 2.0  Docker 1.1.5  Windows 2016 with Docker 17.06.2-ee-16  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alexander Komarov  
 

  
 
 
 
 

 
 

 
[fbce260c] $ c:\jenkinswork\tools\hudson.plugins.groovy.GroovyInstallation\Groovy_2.4.3\groovy-2.4.3\bin\groovy.bat c:\jenkinswork\workspace\infra\test-jdk-installs-docker\fbce260c\hudson6050613090235584392.groovy
find: '/I': No such file or directory
find: '/C': No such file or directory

ERROR: JAVA_HOME is set to an invalid directory: c:\jenkins\jdk\JDK_1.6
Please set the JAVA_HOME variable in your environment
to match the location of your Java installation.
 

 In fact, JAVA_HOME is set correctly (in my case), and other steps (eg maven) work fine. The problem is that the batch script that invokes groovy uses "c:\windows\system32\find.exe", which is not part of the microsoft/nanoserver docker image that is fairly standard.  Once I manually added the host's copy of find.exe, groovy step worked. Also, my custom docker image has cygwin, which means that due to the absence of the microsoft find.exe, it's invoking cygwin's.

[JIRA] (JENKINS-53659) support for parallel Stages nested in stages for ressource locking

2018-10-02 Thread andrew.ba...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53659  
 
 
  support for parallel Stages nested in stages for ressource locking   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53815) several threads looping in TreeMap.put()

2018-10-02 Thread artem.fedo...@blazemeter.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-53815  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: several threads looping in TreeMap.put()   
 

  
 
 
 
 

 
 I changed TreeMap to Hashtable and rebuilt plugin. Could you please recheck that it works for you?performance.hpi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53815) several threads looping in TreeMap.put()

2018-10-02 Thread artem.fedo...@blazemeter.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53815  
 
 
  several threads looping in TreeMap.put()   
 

  
 
 
 
 

 
Change By: 
 Artem Fedorov  
 
 
Attachment: 
 performance.hpi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53745) Multiple JUnit reports recordings analyses at the same time

2018-10-02 Thread artem.fedo...@blazemeter.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-53745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multiple JUnit reports recordings analyses at the same time   
 

  
 
 
 
 

 
 I think that you use very general pattern as source path ("*/report//.xml"). If you will use more simple pattern you'll have less file results and performance plugin will analyze them  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-19103) ghprb slows Jenkins startup to a crawl

2018-10-02 Thread pjano...@redhat.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Janoušek commented on  JENKINS-19103  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ghprb slows Jenkins startup to a crawl   
 

  
 
 
 
 

 
 This issue might be fixed by proposed fix for JENKINS-19123. GitHub API uses WAIT policy (indefinitely) by default, but can be orchestrated to use FAIL -> fast fail in that case occurs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-51667) Missing Jenkins API support for reading fingerprints of pipeline build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara commented on  JENKINS-51667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing Jenkins API support for reading fingerprints of pipeline build   
 

  
 
 
 
 

 
 Duh! I read 2.128 as 2.12.8 and assumed that mine is newer. Thanks for pointing out and sorry about the confusion.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53874) ZipArchiver should set the type bits when setting the Unix mode

2018-10-02 Thread roman.donche...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Donchenko created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53874  
 
 
  ZipArchiver should set the type bits when setting the Unix mode   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-10-02 12:22  
 
 
Environment: 
 Jenkins 2.138.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roman Donchenko  
 

  
 
 
 
 

 
 When ZipArchiver sets the Unix mode for files and directories in the archive, it only sets the permission part of the mode, and not the type part. This causes some problems: 
 
If you run zipinfo on such an archive, it shows the mode as ?rw-r--r-- - which is harmless, but confusing. 
Old versions of libarchive can't extract such files (see https://github.com/libarchive/libarchive/issues/441). There might be other extractors that have similar problems. 
 FIxing this should be simple enough - just OR the mode with S_IFREG (010) for files and S_IFDIR (004) for directories.

[JIRA] (JENKINS-53740) Introduce a way how to disable deferred Wipeout

2018-10-02 Thread pjano...@redhat.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Janoušek commented on  JENKINS-53740  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Introduce a way how to disable deferred Wipeout   
 

  
 
 
 
 

 
 PR sent.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53740) Introduce a way how to disable deferred Wipeout

2018-10-02 Thread pjano...@redhat.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Janoušek updated  JENKINS-53740  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53740  
 
 
  Introduce a way how to disable deferred Wipeout   
 

  
 
 
 
 

 
Change By: 
 Pavel Janoušek  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-51667) Missing Jenkins API support for reading fingerprints of pipeline build

2018-10-02 Thread matthias.schm...@sap.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthias Schmalz commented on  JENKINS-51667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing Jenkins API support for reading fingerprints of pipeline build   
 

  
 
 
 
 

 
 Just read above: The fix has been released with 2.128. So the easy answer is that your Jenkins version is too old.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-51667) Missing Jenkins API support for reading fingerprints of pipeline build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara edited a comment on  JENKINS-51667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing Jenkins API support for reading fingerprints of pipeline build   
 

  
 
 
 
 

 
 I am using [archiveArtifacts|https://jenkins.io/doc/pipeline/steps/core/#-archiveartifacts-%20archive%20the%20artifacts] with {{fingerprint: true}} option and I can see the "See Fingerprints" link on the build page and I can see the dump of "Recorded Fingerprints" when I click on that. However when I follow the REST API link at the bottom and click on the JSON API, I get a full dump of the build that has no fingerprints. I then appended the parameters from the above and just get this response  {{  \{  "_class" : "org.jenkinsci.plugins.workflow.job.WorkflowRun" \}  }} . What could be different in my case? I am running Jenkins ver. 2.73.3 with all updated plugins as of now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-51667) Missing Jenkins API support for reading fingerprints of pipeline build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara commented on  JENKINS-51667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing Jenkins API support for reading fingerprints of pipeline build   
 

  
 
 
 
 

 
 I am using archiveArtifacts with fingerprint: true option and I can see the "See Fingerprints" link on the build page and I can see the dump of "Recorded Fingerprints" when I click on that. However when I follow the REST API link at the bottom and click on the JSON API, I get a full dump of the build that has no fingerprints. I then appended the parameters from the above and just get this response {{{ "_class" : "org.jenkinsci.plugins.workflow.job.WorkflowRun" }}}. What could be different in my case? I am running Jenkins ver. 2.73.3 with all updated plugins as of now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-51667) Missing Jenkins API support for reading fingerprints of pipeline build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara edited a comment on  JENKINS-51667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing Jenkins API support for reading fingerprints of pipeline build   
 

  
 
 
 
 

 
 I am using [archiveArtifacts|https://jenkins.io/doc/pipeline/steps/core/#-archiveartifacts-%20archive%20the%20artifacts] with {{fingerprint: true}} option and I can see the "See Fingerprints" link on the build page and I can see the dump of "Recorded Fingerprints" when I click on that. However when I follow the REST API link at the bottom and click on the JSON API, I get a full dump of the build that has no fingerprints. I then appended the parameters from the above and just get this response {{\{  "_class" : "org.jenkinsci.plugins.workflow.job.WorkflowRun" \}}}. What could be different in my case? I am running Jenkins ver. 2.73.3 with all updated plugins as of now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-51667) Missing Jenkins API support for reading fingerprints of pipeline build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hari Dara edited a comment on  JENKINS-51667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing Jenkins API support for reading fingerprints of pipeline build   
 

  
 
 
 
 

 
 How are the fingerprints made accessible with this fix? I tried the API mentioned in JENKINS-10481 (i.e., appending {{depth=2=fingerprint[fileName,hash]\{0,\}}}, see  [  this comment |https://issues.jenkins-ci.org/browse/JENKINS-10481?focusedCommentId=241054=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-241054] ) and it didn'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-53860) Actions from com.github.jenkins.lastchanges.LastChangesProjectAction$LastChangesActionFactory@72b8d345 for hudson.model.FreeStyleProject@40fdcb64[testing/limit-hosts] included n

2018-10-02 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53860  
 
 
  Actions from com.github.jenkins.lastchanges.LastChangesProjectAction$LastChangesActionFactory@72b8d345 for hudson.model.FreeStyleProject@40fdcb64[testing/limit-hosts] included null not assignable to interface hudson.model.Action   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Released As: 
 Last Changes 2.6.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53873) events listeners failures cause build to fail

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yuri Guller started work on  JENKINS-53873  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Yuri Guller  
 
 
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-53873) events listeners failures cause build to fail

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yuri Guller created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53873  
 
 
  events listeners failures cause build to fail   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Yuri Guller  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-10-02 11:52  
 
 
Environment: 
 any  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Yuri Guller  
 

  
 
 
 
 

 
 MF plugin (specifically most of the Octane CI integration logic) has several Jenkins' events listeners - on builds, on workflow, on SCM and on item changes. Those listeners are running on the mail thread, and therefore any uncaught failure in them will cause the whole build to fail. This is not correct. Correct way to do it, is that any non-mission critical failure (which is none of the Octane's plugin provided functionalities as of now) should handle any failure silently, log it to its own log and let the build to continue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-3627) Add separate permission to view build logs

2018-10-02 Thread pjdar...@gmail.com (JIRA)

Title: Message Title

pjdarton commented on JENKINS-3627

Re: Add separate permission to view build logs

I've just found this issue after a "real-world lesson" in why console access should be more strongly secured than mere "general read access"... While I agree with Daniel Beck that a plugin exposing a password would be a bug in the plugin, bugs do happen and Jenkins' core security model should help mitigate this. More importantly, these days a lot of jobs will be using pipelines, and pipelines don't necessarily use plugins the way the plugin author intended, thus allowing mere "user error" to expose passwords in plain text by accident that a plugin cannot reasonably prevent. As a Jenkins administrator, I can't bugfix my users, so I need to be able to configure my Jenkins server so that such errors can't cause a big security issue. TL;DR: Jenkins allows us to secure access to the workspace as a separate permission - IMO console access should be similarly controllable and the lack of such control is a security weakness.

Add Comment

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

[JIRA] (JENKINS-53872) Provide Customized Squashed Commit Message

2018-10-02 Thread a...@sense-os.nl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aldo Christian assigned an issue to Praqma Support  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53872  
 
 
  Provide Customized Squashed Commit Message   
 

  
 
 
 
 

 
Change By: 
 Aldo Christian  
 
 
Assignee: 
 Aldo Christian Praqma Support  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52021) Spot instances not filtered by template description

2018-10-02 Thread julienduche...@live.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julien Duchesne updated  JENKINS-52021  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52021  
 
 
  Spot instances not filtered by template description   
 

  
 
 
 
 

 
Change By: 
 Julien Duchesne  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Assignee: 
 Francis Upton Julien Duchesne  
 
 
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-53872) Provide Customized Squashed Commit Message

2018-10-02 Thread a...@sense-os.nl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aldo Christian created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53872  
 
 
  Provide Customized Squashed Commit Message   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Aldo Christian  
 
 
Components: 
 pretested-integration-plugin  
 
 
Created: 
 2018-10-02 10:49  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Aldo Christian  
 

  
 
 
 
 

 
 Can we have dedicated field on this plugin, so we can modify commit message when PR merged ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-46231) hidden parameter type is not supported by Blue Ocean

2018-10-02 Thread dcro...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Roche commented on  JENKINS-46231  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hidden parameter type is not supported by Blue Ocean   
 

  
 
 
 
 

 
 As the PR has been closed and not implemented - Has the suggestion from sophistifunk (list of inputs that can be ignored) been ticketed? https://github.com/jenkinsci/blueocean-plugin/pull/1721#issuecomment-383259538  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53201) Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.

2018-10-02 Thread k0rbendal...@bk.ru (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Korben Dallas commented on  JENKINS-53201  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
 

  
 
 
 
 

 
 Subversion Plug-in 2.12.2, the problem is still relevant. Jenkins 2.121.2 OS Linux Started on Oct 2, 2018 7:40:00 AM Received SCMpoll call on master for Build-Trunk on Oct 2, 2018 7:40:00 AM Using sole credentials  in realm ‘ svn’ ERROR: Failed to check repository revision for https://repo/libs/code-libs org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:66) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:702) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:113) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1035) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:164) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:178) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:43) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:47) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2535) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1279) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:79) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:27) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1476) at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:631) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:603) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:649) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) 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) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide

[JIRA] (JENKINS-53871) Consider waiting for lock in "timings" and build status overview?

Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53871  
 
 
  Consider waiting for lock in "timings" and build status overview?   
 

  
 
 
 
 

 
Change By: 
 Reinhold Füreder  
 

  
 
 
 
 

 
 When looking over build history or old builds I saw build durations of e.g. 21min, although I know it typically lasts about 6 to 12min. It turned out that there was a ~8min waiting period for a resource lock...The classic UI's "Stage View" actually shows this waiting in small:  !image-2018-10-02-10-28-42-364.png |thumbnail !However I was wondering if this should be also reflected here: * !image-2018-10-02-10-29-49-549.png |thumbnail ! * !image-2018-10-02-10-30-50-008.png |thumbnail !  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-53871) Consider waiting for lock in "timings" and build status overview?