[JIRA] (JENKINS-44376) Ability to set variables shared between stages

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada commented on  JENKINS-44376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to set variables shared between stages   
 

  
 
 
 
 

 
 Hi laurent perez,  have you tried to set the environment variables in the top level?    

 
pipeline {
environment {
FOO = "FOO"
}
agent any

stages {
stage("foo") {
steps {
echo " FOO-1 is ${env.FOO}"
}
}
stage("group") {
steps {
echo " FOO-2 is ${env.FOO}"
}
}
}
} 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-44376) Ability to set variables shared between stages

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada started work on  JENKINS-44376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jose Blas Camacho Taboada  
 
 
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-44376) Ability to set variables shared between stages

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada edited a comment on  JENKINS-44376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to set variables shared between stages   
 

  
 
 
 
 

 
 Hi [~laurentperez], have you tried to set the environment variables in the top level?  {noformat}pipeline {environment {FOO = "FOO"}agent anystages {stage("foo") {steps {echo " FOO-1 is ${env.FOO}"}}stage("group") {steps {echo " FOO-2 is ${env.FOO}"}} stage("Override"){environment {FOO = "BOO" } steps{echo " FOO-3 is ${env.FOO } "}}}} {noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-48661) Execute stage only after initial pipeline execution

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada commented on  JENKINS-48661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Execute stage only after initial pipeline execution   
 

  
 
 
 
 

 
 Hi Steven Foster there is a new feature that could be used for this triggeredBy, please see the following example where a build triggered by an user (vlinde in the example) executes the Stage Two 

 
pipeline {
agent any
stages {
stage("One") {
steps {
echo "Hello"
}
}
stage("Two") {
when {
triggeredBy cause: "UserIdCause", detail: "vlinde"
}
steps {
script {
echo "World"
echo "Heal it"
}

}
}
}
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-44376) Ability to set variables shared between stages

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada stopped work on  JENKINS-44376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jose Blas Camacho Taboada  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48661) Execute stage only after initial pipeline execution

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48661  
 
 
  Execute stage only after initial pipeline execution   
 

  
 
 
 
 

 
Change By: 
 Jose Blas Camacho Taboada  
 
 
Assignee: 
 Andrew Bayer Jose Blas Camacho Taboada  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55217) provide insecure connection with IdP meta URL

2018-12-17 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo closed an issue as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Disable security on an authentitication method is not a good idea, but you have enough alternatives to make it 
 
If you want to use an insecure connection use http not https 
Not use autosigned certificates, use public CA emitted certificates 
IIRC Java has some option to disable the certificates check 
You can configure an unsecure security provider to Java, google for it 
  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55217  
 
 
  provide insecure connection with IdP meta URL
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
  

[JIRA] (JENKINS-54898) ECS Plugin 1.18 cannot launch slaves

2018-12-17 Thread jenk...@garbe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Garbe updated  JENKINS-54898  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54898  
 
 
  ECS Plugin 1.18 cannot launch slaves   
 

  
 
 
 
 

 
Change By: 
 Philipp Garbe  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 v1.19  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55217) provide insecure connection with IdP meta URL

2018-12-17 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo edited a comment on  JENKINS-55217  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: provide insecure connection with IdP meta URL
 

  
 
 
 
 

 
 Disable security on an authentitication method is not a good idea, but you have enough alternatives to make it* If you want to use an insecure connection use http not https*  You can use an http proxy in the middle*  Not use autosigned certificates, use public CA emitted certificates* IIRC Java has some option to disable the certificates check* You can configure an unsecure security provider to Java, google for it  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54898) ECS Plugin 1.18 cannot launch slaves

2018-12-17 Thread jenk...@garbe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Garbe commented on  JENKINS-54898  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ECS Plugin 1.18 cannot launch slaves   
 

  
 
 
 
 

 
 See https://github.com/jenkinsci/amazon-ecs-plugin/pull/77  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55078) No longer able to start ECS slaves

2018-12-17 Thread jenk...@garbe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Garbe updated  JENKINS-55078  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 See https://github.com/jenkinsci/amazon-ecs-plugin/pull/78  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55078  
 
 
  No longer able to start ECS slaves   
 

  
 
 
 
 

 
Change By: 
 Philipp Garbe  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 v1.19  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-54893) Error provisioning slaves with ECS plugin 1.18

2018-12-17 Thread jenk...@garbe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Garbe closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54893  
 
 
  Error provisioning slaves with ECS plugin 1.18   
 

  
 
 
 
 

 
Change By: 
 Philipp Garbe  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52032) Replace slave occurrence by agent in the Amazon ECS plugin

2018-12-17 Thread jenk...@garbe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Garbe closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52032  
 
 
  Replace slave occurrence by agent in the Amazon ECS plugin   
 

  
 
 
 
 

 
Change By: 
 Philipp Garbe  
 
 
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-52032) Replace slave occurrence by agent in the Amazon ECS plugin

2018-12-17 Thread jenk...@garbe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Philipp Garbe updated  JENKINS-52032  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52032  
 
 
  Replace slave occurrence by agent in the Amazon ECS plugin   
 

  
 
 
 
 

 
Change By: 
 Philipp Garbe  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 v1.18  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55218) Lockable resources plugin does not always work

2018-12-17 Thread lazarstefa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lazar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55218  
 
 
  Lockable resources plugin does not always work   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 lockable-resources-plugin  
 
 
Created: 
 2018-12-17 09:19  
 
 
Environment: 
 Jenkins 2.138, lockable resources v 2.3  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Stefan Lazar  
 

  
 
 
 
 

 
 With version 2.3 of Lockable resources plugin we experience the same error described in JENKINS-43574:   09:59:21 Started by timer http://jenkinsaris:8080/view/__ALL_dev_U__trunk_/job/MS___ALL_dev_u__trunk__Team_SAP/44/console#L609:59:21 [lockable-resources] acquired lock on [] http://jenkinsaris:8080/view/__ALL_dev_U__trunk_/job/MS___ALL_dev_u__trunk__Team_SAP/44/console#L709:59:21 [EnvInject] - Loading node environment variables.   It was fixed in 2.2. Did it return with 2.3 version?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-55218) Lockable resources plugin does not always work

2018-12-17 Thread lazarstefa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lazar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55218  
 
 
  Lockable resources plugin does not always work   
 

  
 
 
 
 

 
Change By: 
 Stefan Lazar  
 

  
 
 
 
 

 
 With version 2.3 of Lockable resources plugin we experience the same error described in JENKINS-43574: *09:59:21*   Started by timer [|http://jenkinsaris:8080/view/__ALL_dev_U__trunk_/job/MS___ALL_dev_u__trunk__Team_SAP/44/console#L6] {color:# FF ff }*09:59:21* [lockable-resources] acquired lock on []{color}[|http://jenkinsaris:8080/view/__ALL_dev_U__trunk_/job/MS___ALL_dev_u__trunk__Team_SAP/44/console#L7]*09:59:21* [EnvInject] - Loading node environment variables. It was fixed in 2.2. Did it return with 2.3 version?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55218) Lockable resources plugin does not always work

2018-12-17 Thread lazarstefa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lazar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55218  
 
 
  Lockable resources plugin does not always work   
 

  
 
 
 
 

 
Change By: 
 Stefan Lazar  
 

  
 
 
 
 

 
 With version 2.3 of Lockable resources plugin we experience the same error described in JENKINS-43574:  *09:59:21* Started by timer{color:#ff}*09:59:21* [lockable-resources] acquired lock on []{color} [|http://jenkinsaris:8080/view/__ALL_dev_U__trunk_/job/MS___ALL_dev_u__trunk__Team_SAP/44/console#L7] *09:59:21* [EnvInject] - Loading node environment variables. It was fixed in 2.2. Did it return with 2.3 version?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-54637) Create a servlet filter to prepopulate audit log attributes

2018-12-17 Thread lathagunaase...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Latha Sekar started work on  JENKINS-54637  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Latha Sekar  
 
 
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-54089) Create an audit log destination global configuration

2018-12-17 Thread lathagunaase...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Latha Sekar updated  JENKINS-54089  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54089  
 
 
  Create an audit log destination global configuration   
 

  
 
 
 
 

 
Change By: 
 Latha Sekar  
 
 
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-55219) Memory leak in logfilesizechecker-plugin due to its multi-instantiation of SafeTimerTasks

2018-12-17 Thread p...@devconsoft.se (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Per Böhlin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55219  
 
 
  Memory leak in logfilesizechecker-plugin due to its multi-instantiation of SafeTimerTasks   
 

  
 
 
 
 

 
Change By: 
 Per Böhlin  
 

  
 
 
 
 

 
 The log file size checker plugin uses an internal class LogSizeTimerTask that inherits from SafeTimerTask. The LogSizeTimerTask have references to {{build}} and {{ lister listener }}.Unfortunantly, the LogSizeTimerTask is only cancelled, never completely cleaned up, resulting in one instance of the LogSizeTimerTask being present in the thread pool execution queue for every build that make use of the plugin.Due to the reference to the build and the listener, those objects are never garbage collected, resulting in every build that was ever built with this plugin active will be kept in memory.This becomes even more problematic if the build has references to other large objects preventing them as well from being GCed.Our jenkins master had +10GB of objects that could not be GCed due to this issue, with hundred of thousands of LogSizeTimerTasks in the thread pool execution queue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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 o

[JIRA] (JENKINS-55219) Memory leak in logfilesizechecker-plugin due to its multi-instantiation of SafeTimerTasks

2018-12-17 Thread p...@devconsoft.se (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Per Böhlin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55219  
 
 
  Memory leak in logfilesizechecker-plugin due to its multi-instantiation of SafeTimerTasks   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Stefan Brausch  
 
 
Components: 
 logfilesizechecker-plugin  
 
 
Created: 
 2018-12-17 10:14  
 
 
Environment: 
 build log file size checker: 1.4  Jenkins ver. 2.121.2 (latest probably affected as well)  Free-style job  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Per Böhlin  
 

  
 
 
 
 

 
 The log file size checker plugin uses an internal class LogSizeTimerTask that inherits from SafeTimerTask. The LogSizeTimerTask have references to build and lister. Unfortunantly, the LogSizeTimerTask is only cancelled, never completely cleaned up, resulting in one instance of the LogSizeTimerTask being present in the thread pool execution queue for every build that make use of the plugin. Due to the reference to the build and the listener, those objects are never garbage collected, resulting in every build that was ever built with this plugin active will be kept in memory. This becomes even more problematic if the build has references to other large objects preventing them as well from being GCed. Our jenkins master had +10GB of objects that could not be GCed due to this issue, with hundred of thousands of LogSizeTimerTasks in the thread pool execution queue.  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-55219) Memory leak in logfilesizechecker-plugin due to its multi-instantiation of SafeTimerTasks

2018-12-17 Thread p...@devconsoft.se (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Per Böhlin commented on  JENKINS-55219  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Memory leak in logfilesizechecker-plugin due to its multi-instantiation of SafeTimerTasks   
 

  
 
 
 
 

 
 I believe that the root cause of this issue is that the plugin instantiate SafeTimerTask (LogSizeTimerTask) for every build. The SafeTimerTask was probably not designed for that usecase since it is never completely cleaned up. The quick fix is to remove the references to build and listener once the task is cancelled, minimizing the damage, but the correct fix would be to rewrite the plugin to only use one global instance of the SafeTimerTask and in that loop over all affected builds and check for log-size.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55220) Multibranch Pipeline jobs get randomly lost

2018-12-17 Thread jenk...@cornr.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Büth updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55220  
 
 
  Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
Change By: 
 Jonas Büth  
 
 
Attachment: 
 bitbucketwebhooks.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-55220) Multibranch Pipeline jobs get randomly lost

2018-12-17 Thread jenk...@cornr.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Büth updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55220  
 
 
  Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
Change By: 
 Jonas Büth  
 
 
Attachment: 
 branchsources.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-55220) Multibranch Pipeline jobs get randomly lost

2018-12-17 Thread jenk...@cornr.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Büth commented on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 Our workaround for this: 
 
shutdown jenkins 
copy job config.xml from working branch to missing branch 
rename branch in copied config.xml 
start 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55221  
 
 
  Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ulli Hafner  
 
 
Components: 
 warnings-ng-plugin  
 
 
Created: 
 2018-12-17 10:33  
 
 
Environment: 
 1.0.0-beta8  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 David Aldrich  
 

  
 
 
 
 

 
 Warnings NG plugin fails to resolve absolute path for gcc4 warning. Error message in console log: 

 
Ubuntu 18.04] Parsing console log (workspace: '/data/hudsonuser/workspace/Regression_test_SystemC_gcc') [Ubuntu 18.04] [ERROR] Can't resolve absolute paths for some files: [Ubuntu 18.04] [ERROR] - AlterafpCompiler.cpp [Ubuntu 18.04] [ERROR] ... skipped logging of 8 additional errors ... [Ubuntu 18.04] [ERROR] Can't create fingerprints for some files: [Ubuntu 18.04] [ERROR] - 'AlterafpCompiler.cpp', IO exception has been thrown: java.nio.file.NoSuchFileException: AlterafpCompiler.cpp [Ubuntu 18.04] [ERROR] - 'AlterafpCompiler.cpp', IO exception has been thrown: java.nio.file.NoSuchFileException: AlterafpCompiler.cpp [Ubuntu 18.04] [ERROR] - 'StarUlPhyRxCommonCamelot.h', IO exception has been thrown: java.nio.file.NoSuchFileException: StarUlPhyRxCommonCamelot.h [Ubuntu 18.04] [ERROR] - 'StarUlPhyRxCommonCamelot.h', IO exception has been thrown: java.nio.file.NoSuchFileException: StarUlPhyRxCommonCamelot.h [Ubuntu 18.04] [ERROR] - 'StarUlPhyRxCommonCamelot.h', IO exception has been thrown: java.nio.file.NoSuchFileException: StarUlPhyRxCommonCamelot.h 

 Related warning in console log: 
 

[JIRA] (JENKINS-51700) Cannot run command on other agent/master when global agent is kubernetes

2018-12-17 Thread yoanli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yo-An Lin commented on  JENKINS-51700  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot run command on other agent/master when global agent is kubernetes   
 

  
 
 
 
 

 
 same here. I wanted to have a default k8s agent, and in the sub-stage I want to allocate a node for isolating the tests. However, it shows "can not cd into {workspace}" error.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-43802) Shared Library using folder-scoped credential fails to authenticate

2018-12-17 Thread gregory.picot....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gregory PICOT commented on  JENKINS-43802  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shared Library using folder-scoped credential fails to authenticate   
 

  
 
 
 
 

 
 Also waiting on this issue to be resolved. The 'Legacy SCM' doesn't work for us, because it doesn't able us to use 'system' scoped credentials. The goal for us is to able people using exposed shared library without having the access to the repository itself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55214) NullPointerException when starting a pipeline in a multibranch project

2018-12-17 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-55214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when starting a pipeline in a multibranch project   
 

  
 
 
 
 

 
 It seems that the Path is invalid? I didn't think that was possible... Please can you provide some detail to help us reproduce the issue. (1) I presume you are using 'Helix Streams' for the source? (2) Do you use a custom name or location for your Jenkinsfile (3) Is your Jenkinsfile 'Pipeline' (Declarative) or 'node' (Script)? (4) Do you use Libraries (5) Do you use 'p4sync' or 'checkout' steps in the Jenkinsfile (6) When referring to 'Starting a pipeline in a MultiBranch project' do you simply mean clicking on 'Scan Multibranch Pipeline Now' or some other feature?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55214) NullPointerException when starting a pipeline in a multibranch project

2018-12-17 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-55214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when starting a pipeline in a multibranch project   
 

  
 
 
 
 

 
 (7) Do you use any variables e.g. ${streams}?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55214) NullPointerException when starting a pipeline in a multibranch project

2018-12-17 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth assigned an issue to Karl Wirth  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55214  
 
 
  NullPointerException when starting a pipeline in a multibranch project   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Assignee: 
 Karl Wirth  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55214) NullPointerException when starting a pipeline in a multibranch project

2018-12-17 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55214  
 
 
  NullPointerException when starting a pipeline in a multibranch project   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Labels: 
 P4_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-45843) Unable to use system credentials for global pipeline library

2018-12-17 Thread gregory.picot....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gregory PICOT commented on  JENKINS-45843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to use system credentials for global pipeline library   
 

  
 
 
 
 

 
 I am also greatly interested in this feature. We want to expose shared library to our users without giving them the git repository access.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs

2018-12-17 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52679  
 
 
  p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Issue Type: 
 Bug New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Are you running the build with make? Can you also paste the make output that shows the current directory? See example log.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner edited a comment on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Are you running the build with make? Can you also paste the make output that shows the current directory? See [example log|https://github.com/jenkinsci/analysis-model/blob/master/src/test/resources/edu/hm/hafner/analysis/parser/absolute-paths.txt#L3].  If the compiler creates no absolute links I need at least the absolute links from make.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-52590) p4-plugin sets client root to null

2018-12-17 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth assigned an issue to Paul Allen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52590  
 
 
  p4-plugin sets client root to null   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Assignee: 
 Karl Wirth 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-52590) p4-plugin sets client root to null

2018-12-17 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth assigned an issue to paul allen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52590  
 
 
  p4-plugin sets client root to null   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Assignee: 
 Paul Allen 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-52590) p4-plugin sets client root to null

2018-12-17 Thread kwi...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Wirth assigned an issue to Paul Allen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52590  
 
 
  p4-plugin sets client root to null   
 

  
 
 
 
 

 
Change By: 
 Karl Wirth  
 
 
Assignee: 
 paul allen 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 I am running with make. 

 
make[1]: Leaving directory '/data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/BitTrue' make[1]: Entering directory '/data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue' 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Interesting, seems that make sometime uses ' and sometimes `.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11

2018-12-17 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-55202  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Signature Plugin: JAXB API is missing with Java 11   
 

  
 
 
 
 

 
 FTR, I just started a fresh container using jenkins/jenkins:jdk11 image, and docker exec shows the following: 

 
ps aux | grep java
jenkins  9  131 14.2 9939268 2280448 ? Sl   11:25   0:59 java -p /usr/share/jenkins/ref/java_cp/jaxb-api.jar:/usr/share/jenkins/ref/java_cp/javax.activation.jar: --add-modules java.xml.bind,java.activation -cp /usr/share/jenkins/ref/java_cp/jaxb-impl.jar:/usr/share/jenkins/ref/java_cp/jaxb-core.jar -Duser.home=/var/jenkins_home -jar /usr/share/jenkins/jenkins.war --enable-future-java
 

 Raphael Pionke in addition to Oleg's question, could you please do the same inside your container and show us what your ps aux | grep java looks like? Thank you!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52744) Using not existing environment variables in environment GString expression causes strange error message

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada started work on  JENKINS-52744  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jose Blas Camacho Taboada  
 
 
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-52744) Using not existing environment variables in environment GString expression causes strange error message

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52744  
 
 
  Using not existing environment variables in environment GString _expression_ causes strange error message   
 

  
 
 
 
 

 
Change By: 
 Jose Blas Camacho Taboada  
 
 
Assignee: 
 Andrew Bayer Jose Blas Camacho Taboada  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55221  
 
 
  Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 analysis-model-api-1.0.0-beta19  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-54767) Global variables are overriding local variables

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54767  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Global variables are overriding local variables   
 

  
 
 
 
 

 
 fisnik hajredini sorry, I am busy with other personal topics. I cannot provide any ETA for my response in this ticket, see https://groups.google.com/d/msg/jenkinsci-dev/XToix3QpL_k/j2k0xeXvCQAJ . You can use other community channels, like IRC or user/developer mailing lists  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55084) Cloud Statistics does not show EC2 instance information

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55084  
 
 
  Cloud Statistics does not show EC2 instance information   
 

  
 
 
 
 

 
Change By: 
 Oliver Gondža  
 
 
Component/s: 
 cloud-stats-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-55084) Cloud Statistics does not show EC2 instance information

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža assigned an issue to FABRIZIO MANFREDI  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55084  
 
 
  Cloud Statistics does not show EC2 instance information   
 

  
 
 
 
 

 
Change By: 
 Oliver Gondža  
 
 
Assignee: 
 Oliver Gondža FABRIZIO MANFREDI  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55084) Cloud Statistics does not show EC2 instance information

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-55084  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cloud Statistics does not show EC2 instance information   
 

  
 
 
 
 

 
 I am removing the cloud-stats component so this gets a proper assignee on ec2 maintainers side. Note that there are some changes to do to have the provisioning visualized: https://github.com/jenkinsci/cloud-stats-plugin/#integrating-cloud-plugin-with-cloud-stats-plugin   Feel free to reach to me in case of questions or problems.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync

2018-12-17 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-53723  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync   
 

  
 
 
 
 

 
 Use double quotes for the variable (I called it `change` but any unused name will do): 

 

node() {
p4sync(
charset: 'none', 
credential: 'phooey', 
populate: autoClean(
delete: true, 
modtime: false, 
pin: "${change}", 
quiet: true, 
replace: true, 
tidy: false), 
source: streamSource('//streams/main-t')
)
}  

 Select 'This project is parameterized' and add a 'String parameter' and set the default to "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-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync

2018-12-17 Thread pal...@perforce.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen closed an issue as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing - the build with parameterized option with 'pin' covers most use cases.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53723  
 
 
  [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55222) JDK Installer certificate expiry

2018-12-17 Thread javapr...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 javapress created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55222  
 
 
  JDK Installer certificate expiry   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 docklog.log  
 
 
Components: 
 core  
 
 
Created: 
 2018-12-17 11:48  
 
 
Environment: 
 Docker Jenkins 2.155 and 2.156 seems to affect all variants (jdk11, alpine, etc)  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 javapress  
 

  
 
 
 
 

 
 First start of new installation generates an error during the installation of the default plugin set: 

 

WARNING: signature check failed for https://updates.jenkins.io/updates/hudson.tools.JDKInstaller.json

Exception: NotAfter: Sat Dec 15 16:54:02 GMT 2018 

 Install seems to complete but creating jobs results in exceptions.  
 

  
 
 
 
 

 
 
 


[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11

2018-12-17 Thread raphael.pio...@t-systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael Pionke commented on  JENKINS-55202  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Signature Plugin: JAXB API is missing with Java 11   
 

  
 
 
 
 

 
 Oleg Nenashev Baptiste Mathus i got the following from docker top: 

 

{
  "Titles" : [ "PID", "USER", "TIME", "COMMAND" ],
  "Processes" : [ [ "7189", "1000", "0:00", "/sbin/tini -- /usr/local/bin/jenkins.sh" ], [ "7227", "1000", "1:47", "java -p /usr/share/jenkins/ref/java_cp/jaxb-api.jar:/usr/share/jenkins/ref/java_cp/javax.activation.jar: --add-modules java.xml.bind,java.activation -cp /usr/share/jenkins/ref/java_cp/jaxb-impl.jar:/usr/share/jenkins/ref/java_cp/jaxb-core.jar -Duser.home=/var/jenkins_home -jar /usr/share/jenkins/jenkins.war --enable-future-java" ] ]
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11

2018-12-17 Thread raphael.pio...@t-systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael Pionke edited a comment on  JENKINS-55202  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Signature Plugin: JAXB API is missing with Java 11   
 

  
 
 
 
 

 
 [~oleg_nenashev] [~batmat] i got the following from docker top:{code :json }{  "Titles" : [ "PID", "USER", "TIME", "COMMAND" ],  "Processes" : [ [ "7189", "1000", "0:00", "/sbin/tini -- /usr/local/bin/jenkins.sh" ], [ "7227", "1000", "1:47", "java -p /usr/share/jenkins/ref/java_cp/jaxb-api.jar:/usr/share/jenkins/ref/java_cp/javax.activation.jar: --add-modules java.xml.bind,java.activation -cp /usr/share/jenkins/ref/java_cp/jaxb-impl.jar:/usr/share/jenkins/ref/java_cp/jaxb-core.jar -Duser.home=/var/jenkins_home -jar /usr/share/jenkins/jenkins.war --enable-future-java" ] ]} I uploaded sample plugin code based on the hello-world-plugin: https://github.com/rpionke/jaxb-test {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-55202) Performance Signature Plugin: JAXB API is missing with Java 11

2018-12-17 Thread raphael.pio...@t-systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael Pionke edited a comment on  JENKINS-55202  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Signature Plugin: JAXB API is missing with Java 11   
 

  
 
 
 
 

 
 [~oleg_nenashev] [~batmat] i got the following from docker top:{code:java}{  "Titles" : [ "PID", "USER", "TIME", "COMMAND" ],  "Processes" : [ [ "7189", "1000", "0:00", "/sbin/tini -- /usr/local/bin/jenkins.sh" ], [ "7227", "1000", "1:47", "java -p /usr/share/jenkins/ref/java_cp/jaxb-api.jar:/usr/share/jenkins/ref/java_cp/javax.activation.jar: --add-modules java.xml.bind,java.activation -cp /usr/share/jenkins/ref/java_cp/jaxb-impl.jar:/usr/share/jenkins/ref/java_cp/jaxb-core.jar -Duser.home=/var/jenkins_home -jar /usr/share/jenkins/jenkins.war --enable-future-java" ] ]}{code} I uploaded sample plugin code based on the hello-world-plugin: [https://github.com/rpionke/jaxb-test]The unit tests  fail  and the builder inside hpi:run with the jenkins/jenkins:jdk11 image  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55202) Performance Signature Plugin: JAXB API is missing with Java 11

2018-12-17 Thread raphael.pio...@t-systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael Pionke edited a comment on  JENKINS-55202  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Signature Plugin: JAXB API is missing with Java 11   
 

  
 
 
 
 

 
 [~oleg_nenashev] [~batmat] i got the following from docker top:{code :java }{  "Titles" : [ "PID", "USER", "TIME", "COMMAND" ],  "Processes" : [ [ "7189", "1000", "0:00", "/sbin/tini -- /usr/local/bin/jenkins.sh" ], [ "7227", "1000", "1:47", "java -p /usr/share/jenkins/ref/java_cp/jaxb-api.jar:/usr/share/jenkins/ref/java_cp/javax.activation.jar: --add-modules java.xml.bind,java.activation -cp /usr/share/jenkins/ref/java_cp/jaxb-impl.jar:/usr/share/jenkins/ref/java_cp/jaxb-core.jar -Duser.home=/var/jenkins_home -jar /usr/share/jenkins/jenkins.war --enable-future-java" ] ]} {code}    I uploaded sample plugin code based on the hello-world-plugin:  [  https://github.com/rpionke/jaxb-test {code} ]The unit tests fail and the builder inside hpi:run with the jenkins/jenkins:jdk11 image  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55179) Ws-cleanup plugin: PCT test fails when running with JDK11

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža started work on  JENKINS-55179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oliver Gondža  
 
 
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-54767) Global variables are overriding local variables

2018-12-17 Thread jan.bot...@rail.bombardier.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jan Bottek commented on  JENKINS-54767  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Global variables are overriding local variables   
 

  
 
 
 
 

 
 we have the same problem that our global env variables from jenkins configuration will overwrite our job parameters, but only in Pipeline jobs - freestyle jobs are not affected. EnvInject Plugin is not installed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55179) Ws-cleanup plugin: PCT test fails when running with JDK11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ws-cleanup plugin: PCT test fails when running with JDK11   
 

  
 
 
 
 

 
 A recommended fix it to update to the latest plugin POM with JENKINS-55098 . It should bump Mockito/PowerMock versions to proper ones  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55179) Ws-cleanup plugin: PCT test fails when running with JDK11

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-55179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ws-cleanup plugin: PCT test fails when running with JDK11   
 

  
 
 
 
 

 
 I did not get that running that way. This was needed too: https://github.com/jenkinsci/ws-cleanup-plugin/pull/44/commits/15058b24597d8b0d64e2a0d7ac57b8b0fb097b21#diff-164ca95d06b15de9cdf57e5e93bfc782R52   Now when I look at it, the dependency on powermock can be removed as test can be written without relying on it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline

2018-12-17 Thread jtabo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jose Blas Camacho Taboada updated  JENKINS-49142  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49142  
 
 
  Be able to customize checkout as "options" in declarative pipeline   
 

  
 
 
 
 

 
Change By: 
 Jose Blas Camacho Taboada  
 
 
Status: 
 In  Review  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-55179) Ws-cleanup plugin: PCT test fails when running with JDK11

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-55179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ws-cleanup plugin: PCT test fails when running with JDK11   
 

  
 
 
 
 

 
 Oleg Nenashev, I took the path to least resistance. You can have a look at https://github.com/olivergondza/ws-cleanup-plugin/blob/powermock/pom.xml if you are interested: 

 
$ mvn clean package -Djenkins.version=2.155 -Dtest=CleanupPowermockTest -Denforcer.skip
...
[INFO] Running hudson.plugins.ws_cleanup.CleanupPowermockTest
Dec 17, 2018 1:35:01 PM jenkins.model.Jenkins 
SEVERE: Failed to load Jenkins.class
com.thoughtworks.xstream.InitializationException: Could not instantiate converter : com.thoughtworks.xstream.converters.extended.DurationConverter : null
	at com.thoughtworks.xstream.XStream.registerConverterDynamically(XStream.java:904)
	at com.thoughtworks.xstream.XStream.setupConverters(XStream.java:867)
	at com.thoughtworks.xstream.XStream.(XStream.java:574)
	at com.thoughtworks.xstream.XStream.(XStream.java:496)
	at com.thoughtworks.xstream.XStream.(XStream.java:465)
	at com.thoughtworks.xstream.XStream.(XStream.java:411)
	at com.thoughtworks.xstream.XStream.(XStream.java:378)
	at hudson.util.XStream2.(XStream2.java:113)
	at jenkins.model.Jenkins.(Jenkins.java:5209)
	at hudson.PluginManager.(PluginManager.java:2089)
	at org.jvnet.hudson.test.JenkinsRule.(JenkinsRule.java:329)
	at hudson.plugins.ws_cleanup.CleanupPowermockTest.(CleanupPowermockTest.java:59)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.createTestInstance(PowerMockJUnit44RunnerDelegateImpl.java:197)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.createTest(PowerMockJUnit44RunnerDelegateImpl.java:182)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.invokeTestMethod(PowerMockJUnit44RunnerDelegateImpl.java:204)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.runMethods(PowerMockJUnit44RunnerDelegateImpl.java:160)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl$1.run(PowerMockJUnit44RunnerDelegateImpl.java:134)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44)
	at org.powermock.modules.junit4.internal.impl.PowerMockJUnit44RunnerDelegateImpl.run(PowerMockJUnit44RunnerDelegateImpl.java:136)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:117)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:57)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
	at org.apache.maven.

[JIRA] (JENKINS-55179) Ws-cleanup plugin: PCT test fails when running with JDK11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55179  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ws-cleanup plugin: PCT test fails when running with JDK11   
 

  
 
 
 
 

 
 Yes, it's same as https://github.com/jenkinsci/jenkins/pull/3651  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55179) Ws-cleanup plugin: PCT test fails when running with JDK11

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in https://github.com/jenkinsci/ws-cleanup-plugin/pull/44. Changes released as 0.37.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55179  
 
 
  Ws-cleanup plugin: PCT test fails when running with JDK11   
 

  
 
 
 
 

 
Change By: 
 Oliver Gondža  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 0.37  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55223) unable to create a metricskey via the api

2018-12-17 Thread arnold.matig...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 arnold matignon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55223  
 
 
  unable to create a metricskey via the api   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 metrics-plugin  
 
 
Created: 
 2018-12-17 12:54  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 arnold matignon  
 

  
 
 
 
 

 
 Hello, I am unable to use the dedicated method setAccessKeys() to add a new metric key. -> the goal is to define the key via the code instead of overriding the generated xml file.   def monitoringKey = new jenkins.metrics.api.MetricsAccessKey ("jenkins_metrics", "monitoring", true, false, true, true, null) List metricKeys = new ArrayList () metricKeys.add (monitoringKey) jenkins.metrics.api.MetricsAccessKey.DescriptorImpl.setAccessKeys (metricKeys)   result: groovy.lang.MissingMethodException: No signature of method: static jenkins.metrics.api.MetricsAccessKey$DescriptorImpl.setAccessKeys() is applicable for argument types: (java.util.ArrayList) values: [[MetricsAccessKey\{key='monitoring', description='jenkins_metrics', canPing=true, canHealthCheck=true, canMetrics=true, canThreadDump=false, origins='null'}]] Possible solutions: setAccessKeys(java.util.List), getAccessKeys(), getAccessKey(java.lang.String)    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
   

[JIRA] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)

2018-12-17 Thread smoljo.anto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Smoljo commented on  JENKINS-27457  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)   
 

  
 
 
 
 

 
 Hi Greg,   I have a problem when deploying EAR on WAS server form Jenkins job. Application is installed without any problems , but it won't start. Error from WAS SystemOut.log is below in red text. If I deploy same EAR from WAS admin console everything is OK (application is normaly installed and started). I tried to remove ibm-*.xml files from EAR file and applied other steps as you suggested, and tried deploy, but the problem is still present. I also have other EAR file with ibm-*.xml files inside, but deploy and start by Jenkins goes without any problems!  at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:522) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:522) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)Caused by: com.ibm.ws.exception.RuntimeWarning: SRVE0303E: Servlet name for the servlet mapping /xyz/abc could not be found. at com.ibm.ws.webcontainer.webapp.WebAppConfigurationHelper.constructServletMappings(WebAppConfigurationHelper.java:838) at com.ibm.ws.webcontainer.webapp.WebAppConfigurationHelper.createConfiguration(WebAppConfigurationHelper.java:267) at com.ibm.ws.webcontainer.metadata.WebMetaDataFactory.createMetaData(WebMetaDataFactory.java:204)   WebSphere version is WAS v9.0.0.9 WDP version is 1.6.1          
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11

2018-12-17 Thread raphael.pio...@t-systems.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raphael Pionke edited a comment on  JENKINS-55202  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Signature Plugin: JAXB API is missing with Java 11   
 

  
 
 
 
 

 
 [~oleg_nenashev] [~batmat] i got the following from docker top:{code:java}{  "Titles" : [ "PID", "USER", "TIME", "COMMAND" ],  "Processes" : [ [ "7189", "1000", "0:00", "/sbin/tini -- /usr/local/bin/jenkins.sh" ], [ "7227", "1000", "1:47", "java -p /usr/share/jenkins/ref/java_cp/jaxb-api.jar:/usr/share/jenkins/ref/java_cp/javax.activation.jar: --add-modules java.xml.bind,java.activation -cp /usr/share/jenkins/ref/java_cp/jaxb-impl.jar:/usr/share/jenkins/ref/java_cp/jaxb-core.jar -Duser.home=/var/jenkins_home -jar /usr/share/jenkins/jenkins.war --enable-future-java" ] ]}{code} I uploaded sample plugin code based on the hello-world-plugin: [https://github.com/rpionke/jaxb-test]The unit tests and the builder  are failing  inside hpi:run with the jenkins/jenkins:jdk11 image  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-53098) Gitea Plugin documentation missing

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


 
 
 
 

 
 
 

 
   
 Stephen Connolly updated  JENKINS-53098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53098  
 
 
  Gitea Plugin documentation missing   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53098) Gitea Plugin documentation missing

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


 
 
 
 

 
 
 

 
   
 Stephen Connolly updated  JENKINS-53098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53098  
 
 
  Gitea Plugin documentation missing   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55224) Artifactory plugin reports class not found exception with git client 3.0.0 beta

2018-12-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55224  
 
 
  Artifactory plugin reports class not found exception with git client 3.0.0 beta   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Eyal Ben Moshe  
 
 
Components: 
 artifactory-plugin  
 
 
Created: 
 2018-12-17 13:33  
 
 
Environment: 
 Jenkins 2.150.1  Git client plugin 3.0.0-beta6  Artifactory plugin from master branch  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Mark Waite  
 

  
 
 
 
 

 
 Git client plugin 3.0.0 updates the bundled JGit from 4.5.4 to 5.2. JGit 5.2 replaces the Repository.getRef(String) call with two calls, Repository.exactRef(String) and Repository.findRef(String). Rather than use the JGit Repository method, switch to using the git client plugin API that will then call the correct JGit method based on the installed version of JGit.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-48160) Support for choosing BitBucket mirror for checkout in Team/Organization project

2018-12-17 Thread askalsk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arkadiusz Skalski commented on  JENKINS-48160  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for choosing BitBucket mirror for checkout in Team/Organization project   
 

  
 
 
 
 

 
 Hi guys, could you provide some feedback on this? Lack of mirror support is a big performance issue for all pipelines. I can't imagine configuring the whole Bitbucket project just by myself and not using this awesome plugin only because its not supporting smart mirrors.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55218) Lockable resources plugin does not always work

2018-12-17 Thread lazarstefa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Lazar commented on  JENKINS-55218  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lockable resources plugin does not always work   
 

  
 
 
 
 

 
 As temporary solution we will switch back to version 2.2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55225) Dead link for WS-Cleanup version 0.37

2018-12-17 Thread hub...@9h.pl (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hubert Nodzak created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55225  
 
 
  Dead link for WS-Cleanup version 0.37   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 ws-cleanup-plugin  
 
 
Created: 
 2018-12-17 13:56  
 
 
Environment: 
 Jenkins Ubuntu 2.150.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Hubert Nodzak  
 

  
 
 
 
 

 
 Hello, the file for WS-Cleanup Plugin (version 0.37) is dead: http://updates.jenkins-ci.org/download/plugins/ws-cleanup/0.37/ws-cleanup.hpi This link can be found here: https://updates.jenkins.io/current/update-center.json 

 

(...)
"excerpt": "This plugin deletes the project workspace when invoked.","gav": "org.jenkins-ci.plugins:ws-cleanup:0.37","labels": ["post-build","buildwrapper"],"name": "ws-cleanup","previousTimestamp": "2018-10-17T06:52:13.00Z","previousVersion": "0.36","releaseTimestamp": "2018-12-17T12:53:35.00Z","requiredCore": "1.642.1","scm": "https://github.com/jenkinsci/ws-cleanup-plugin","sha1": "VMfs4eMvWrCt3vnogV5YObZtmyE=","sha256": "nXStzJEeGwjHQSwjqlX2qm0BbwAFh9JVWYzhZ1TYqQ0=","title": "Workspace Cleanup","url": "http://updates.jenkins-ci.org/download/plugins/ws-cleanup/0.37/ws-cleanup.hpi","version": "0.37","wiki": "https://plugins.jenkins.io/ws-cleanup"
(..)
 

 Please remove this broken link, thank you.  
 

  
 
 
 
  

[JIRA] (JENKINS-55113) Constructor, using other methods of the class, causes "hudson.remoting.ProxyException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation"

2018-12-17 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-55113  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55113  
 
 
  Constructor, using other methods of the class, causes "hudson.remoting.ProxyException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation"   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Resolution: 
 Fixed 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-55113) Constructor, using other methods of the class, causes "hudson.remoting.ProxyException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation"

2018-12-17 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-55113  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55113  
 
 
  Constructor, using other methods of the class, causes "hudson.remoting.ProxyException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation"   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
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-55225) Dead link for WS-Cleanup version 0.37

2018-12-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-55225  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dead link for WS-Cleanup version 0.37   
 

  
 
 
 
 

 
 Hmm, I can download this file and the content is correct. Can you recheck on your end? Use wget or similar to let us know what mirror you use.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55222) JDK Installer certificate expiry

2018-12-17 Thread nathan.lindshi...@lockpath.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nathan Lindshield commented on  JENKINS-55222  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK Installer certificate expiry   
 

  
 
 
 
 

 
 Applicable portion of the log extracted 
 WARNING: signature check failed for http://updates.jenkins-ci.org/updates/hudson.tools.JDKInstaller.json ERROR: Signature verification failed in downloadable 'hudson.tools.JDKInstaller' (show details)java.security.cert.CertificateExpiredException: NotAfter: Sat Dec 15 10:54:02 CST 2018  at sun.security.x509.CertificateValidity.valid(Unknown Source)  at sun.security.x509.X509CertImpl.checkValidity(Unknown Source)  at sun.security.provider.certpath.BasicChecker.verifyValidity(Unknown Source)  at sun.security.provider.certpath.BasicChecker.check(Unknown Source) Caused: java.security.cert.CertPathValidatorException: validity check failed  at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(Unknown Source)  at sun.security.provider.certpath.PKIXCertPathValidator.validate(Unknown Source)  at sun.security.provider.certpath.PKIXCertPathValidator.validate(Unknown Source)  at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(Unknown Source)  at java.security.cert.CertPathValidator.validate(Unknown Source)  at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93)  at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:85)  at hudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:416)  at jenkins.model.DownloadSettings$DailyCheck.execute(DownloadSettings.java:121)  at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101)  at java.lang.Thread.run(Unknown Source)  at hudson.util.FormValidation._errorWithMarkup(FormValidation.java:266) at hudson.util.FormValidation._error(FormValidation.java:198) at hudson.util.FormValidation.error(FormValidation.java:188) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:134) at hudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:416) at jenkins.model.DownloadSettings$DailyCheck.execute(DownloadSettings.java:121) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Unknown Source)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[JIRA] (JENKINS-20922) Progress bar links to nonexistant console

2018-12-17 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated  JENKINS-20922  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-20922  
 
 
  Progress bar links to nonexistant console   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-20922) Progress bar links to nonexistant console

2018-12-17 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated  JENKINS-20922  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-20922  
 
 
  Progress bar links to nonexistant console   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
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-55226) Deadlock while running tests

2018-12-17 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55226  
 
 
  Deadlock while running tests   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Alex Earl  
 
 
Components: 
 token-macro-plugin  
 
 
Created: 
 2018-12-17 14:19  
 
 
Environment: 
 Jenkins 2.155  PCT  Java 1.8 && Java 11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Adrien Lecharpentier  
 

  
 
 
 
 

 
 While I was running token-macro against PCT and Jenkins 2.155, I noticed that deadlocks are happening during the plugin tests. 

 
[INFO] Running org.jenkinsci.plugins.tokenmacro.PipelineTest[INFO] Running org.jenkinsci.plugins.tokenmacro.PipelineTest=== Starting testException(org.jenkinsci.plugins.tokenmacro.PipelineTest)   0.084 [id=175] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: Running on http://localhost:35227/jenkins/   0.236 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization   0.279 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins   0.704 [id=181] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins   0.713 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins   0.716 [id=186] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions   0.719 [id=186] INFO h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component org.jenkinsci.plugins.workflow.steps.scm.SubversionStep$DescriptorImpl; skipping   1.234 [id=184] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs   1.268 [id=186] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 180.000 [id=1] WARNING o.j.hudson.test.JenkinsRule$2#evaluate: Test timed out (after 180

[JIRA] (JENKINS-54980) Jobs are stopped being triggered - java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=myo

2018-12-17 Thread liyati...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 liyatikal updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54980  
 
 
  Jobs are stopped being triggered - java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=myorgname,repository=myreponame]   
 

  
 
 
 
 

 
Change By: 
 liyatikal  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-54980) Jobs are stopped being triggered - java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=myo

2018-12-17 Thread liyati...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 liyatikal updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54980  
 
 
  Jobs are stopped being triggered - java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=myorgname,repository=myreponame]   
 

  
 
 
 
 

 
Change By: 
 liyatikal  
 
 
Component/s: 
 github-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-54767) Global variables are overriding local variables

2018-12-17 Thread jan.bot...@rail.bombardier.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jan Bottek commented on  JENKINS-54767  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Global variables are overriding local variables   
 

  
 
 
 
 

 
 after downgrading the 3 plugins it was working again   
 

 
 
name 
from 
to 
 
 
Pipeline: Declarative 
1.3.4 
1.3.2 
 
 
Pipeline: Declarative Extension Points API 
1.3.4 
1.3.2 
 
 
Pipeline: Job 
 2.31 
 2.25 
 

 
 so it seems it only belongs to the plugins and not to Jenkins core   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[JIRA] (JENKINS-54767) Global variables are overriding local variables

2018-12-17 Thread jan.bot...@rail.bombardier.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jan Bottek edited a comment on  JENKINS-54767  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Global variables are overriding local variables   
 

  
 
 
 
 

 
 after downgrading the 3 plugins it was working again |name|from|to||Pipeline: Declarative|1.3.4|1.3.2||Pipeline: Declarative Extension Points API|1.3.4|1.3.2||Pipeline: Job| 2.31| 2.25|  so it seems it only belongs to the plugins and not to Jenkins core   . So we are not using depclarative pipeline, i assume it is related to Pipeline: Job, but we downgraded the other two due to dependencies  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Many warnings paths are now correctly provided but some are still not provided. For example, there is a warning for: post_steps.h:105 The make output is: 

 

make[1]: Leaving directory '/data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue'
make[1]: Entering directory '/data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue'

g++ -c -Wall -m64 -DSYSTEMC -Wno-unused-variable -Wno-unused-function -I../../../Kernel -I../../../StarLibs/StdStars -I../../../StarLibs/LinkSim/ChannelModels/TML -I../../../StarLibs/LinkSim/LTE -I../../../StarLibs/Camelot/BitTrue -I../../../StarLibs/Camelot/ScBitTrue/Altera80 -I../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT -I/net/simdata/Hudson_OpenSourceLibs/SystemC/rel-2.3.3/src -I/usr/include/ -fpic -O3 vfft_fft_core_VFFT1_CModel.cpp -o _gnuRelease/vfft_fft_core_VFFT1_CModel.o
In file included from ../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/csl.h:6:0,
 from vfft_fft_core_VFFT1_CModel.h:2,
 from vfft_fft_core_VFFT1_CModel.cpp:2:
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h: In instantiation of ‘bool csl::StimulusFile::Get(int64_t&) [with long unsigned int bit_width = 1; int64_t = long int]’:
vfft_fft_core_VFFT1_CModel.h:27:30:   required from here
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h:168:21: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
 GetUInt((uint32_t&)result);
 ^
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h: In instantiation of ‘bool csl::StimulusFile::Get(int64_t&) [with long unsigned int bit_width = 8; int64_t = long int]’:
vfft_fft_core_VFFT1_CModel.h:28:30:   required from here
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h:168:21: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h: In instantiation of ‘bool csl::StimulusFile::Get(int64_t&) [with long unsigned int bit_width = 4; int64_t = long int]’:
vfft_fft_core_VFFT1_CModel.h:29:33:   required from here
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h:168:21: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h: In instantiation of ‘bool csl::StimulusFile::Get(int64_t&) [with long unsigned int bit_width = 16; int64_t = long int]’:
vfft_fft_core_VFFT1_CModel.h:30:36:   required from here
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h:168:21: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h: In instantiation of ‘bool csl::StimulusFile::Get(int64_t&) [with long unsigned int bit_width = 26; int64_t = long int]’:
vfft_fft_core_VFFT1_CModel.h:56:37:   required from here
../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h:168:21: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
In file included from ../../../StarLibs/Camelot/ScBitTr

[JIRA] (JENKINS-50033) Method code too large using declarative pipelines

2018-12-17 Thread amai...@redhat.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Amnon Maimon commented on  JENKINS-50033  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Method code too large using declarative pipelines   
 

  
 
 
 
 

 
 Ruud P - Is it really resolved? On which version? Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 The relative path is: ../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h The make path is: /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue From my understanding, the absolute path should be /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h, see test case. What do you expect?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-31866) Attempts to restrict Pipeline jobs from running on master result in job hanging

2018-12-17 Thread ace_11...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrian Vlad commented on  JENKINS-31866  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Attempts to restrict Pipeline jobs from running on master result in job hanging   
 

  
 
 
 
 

 
 I have a similar problem. I have a pipeline called "test_pipeline" and inside it does: 

 

node('some_node') {
...
} 

 On "some_node" I use Restrict jobs execution at node -> Regular _expression_ (Job Name) with value test_pipeline. This configuration doesn't work (the build hangs). But if I change the value to test_pipeline.* then it works. What is the problem? Is job-restrictions using different pipeline names with some suffix? (test_pipeline/.* also works)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 And what is with the other errors like /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp. Are these paths correct?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-50033) Method code too large using declarative pipelines

2018-12-17 Thread amai...@redhat.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Amnon Maimon edited a comment on  JENKINS-50033  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Method code too large using declarative pipelines   
 

  
 
 
 
 

 
 [~ruudp] , [~abayer]   - Is it really resolved? On which version?Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55221  
 
 
  Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
Change By: 
 David Aldrich  
 
 
Attachment: 
 screenshot-1.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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55221  
 
 
  Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
Change By: 
 David Aldrich  
 
 
Attachment: 
 screenshot-2.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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread david.aldr...@emea.nec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Aldrich commented on  JENKINS-55221  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
 Your expected absolute path is correct, but there is no link to post_steps.h:The warnings for AlterafpCompiler.cpp are ok: 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)

2018-12-17 Thread smoljo.anto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Antonio Smoljo edited a comment on  JENKINS-27457  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)   
 

  
 
 
 
 

 
 Hi Greg, I have a problem when deploying EAR on WAS server form Jenkins job. Application is installed without any problems , but it won't start. Error from WAS SystemOut.log is below in red text. If I deploy same EAR from WAS admin console everything is OK (application is normaly installed and started). I tried to remove ibm-*.xml files from EAR file and applied other steps as you suggested, and tried deploy, but the problem is still present.I also have other EAR file with ibm-*.xml files inside, but deploy and start by Jenkins goes without any problems! _{color:#de350b}at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:522) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:522) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)*Caused by: com.ibm.ws.exception.RuntimeWarning: SRVE0303E: Servlet name for the servlet mapping /xyz/abc could not be found*. at com.ibm.ws.webcontainer.webapp.WebAppConfigurationHelper.constructServletMappings(WebAppConfigurationHelper.java:838) at com.ibm.ws.webcontainer.webapp.WebAppConfigurationHelper.createConfiguration(WebAppConfigurationHelper.java:267) at com.ibm.ws.webcontainer.metadata.WebMetaDataFactory.createMetaData(WebMetaDataFactory.java:204){color}_ {color:#172b4d}WebSphere version is WAS v9.0.0.9{color}{color:#172b4d}WDP version is 1.6.1{color}   *It's worth mentioning that if deploy is done by Jenkins all  parts from web.xml file are missing.*   For example :  __ _ name _ _ com.some.XYZ ___     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-50033) Method code too large using declarative pipelines

2018-12-17 Thread ruud.pr...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ruud P commented on  JENKINS-50033  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Method code too large using declarative pipelines   
 

  
 
 
 
 

 
 my bug was a duplicate bug, but it is not solved and so far as i know it will also not happen, I change my code and using script blocks. see https://issues.jenkins-ci.org/browse/JENKINS-37984    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-45411) Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System

2018-12-17 Thread murali.ra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Murali R commented on  JENKINS-45411  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System   
 

  
 
 
 
 

 
 Hi All, We are also facing similar issue. Any solution to this issue ? Please let us know if we have any workaround or solution to this issue.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54840) UnsupportedOperationException getLogFile

2018-12-17 Thread jenk...@mockies.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Vogtländer commented on  JENKINS-54840  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: UnsupportedOperationException getLogFile   
 

  
 
 
 
 

 
 Torsten Reinhard: you should be able to replace "manager.logContains()" with 

 

if (currentBuild.rawBuild.log ==~ /(?s).*project allows check:.*\\*\\*\\* NOT \\*\\*\\* allowed.*/) {
 

 Note that this is somewhat different from using "manager.logContains()", as the manager objects internal getMatcher() method matches line after line. Access to getLog() must be approved by an administrator when running in a sandbox. Btw, the usage of "manager" to add badges/summary is deprecated and should be replaced by the badge plug-in: https://jenkins.io/doc/pipeline/steps/badge/ and https://github.com/jenkinsci/badge-plugin/blob/master/README.md Setting the build result without "manager" can be done by using 

 

currentBuild.result = "UNSTABLE"
 

 See pipeline-syntax/globals reference.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google 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-45411) Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System

2018-12-17 Thread poppsalw...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Poojaa Sudhakaran commented on  JENKINS-45411  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to run UFT script on a locked remote host by Jenkins plugin HPE Test from File System   
 

  
 
 
 
 

 
 Hello Team, We are also trying to establish a similar setup. Could you please let us know if you've any solution for 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55221  
 
 
  Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Attachment: 
 image.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-55221) Warnings NG plugin can't resolve absolute paths with gcc4

2018-12-17 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55221  
 
 
  Warnings NG plugin can't resolve absolute paths with gcc4   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Attachment: 
 image.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.


  1   2   >