[JIRA] (JENKINS-59706) Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl

2020-04-08 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-59706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl   
 

  
 
 
 
 

 
 I've now seen JENKINS-56773 and we will uninstall the "Blue Ocean Executor Info" plugin and check.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202407.1570550825000.8194.1586346660198%40Atlassian.JIRA.

[JIRA] (JENKINS-59706) Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl

2020-04-08 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-59706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl   
 

  
 
 
 
 

 
 Hi, We're using version 1.21.0 of BlueOcean on Jenkins LTS 2.204.1 and the problem persists  Calls to /blue/rest/organizations/jenkins/computers/ are so heavy that they freeze the browsers when accessing BlueOcean. We had to disable those calls at firewall level but this makes some features of BlueOcean not working any longer (like triggering a build from the branch view). We do have an installation with up to 125 transient EC2 nodes and thousands of jobs running every day. What could I provide which helps fixing the issue? Thanks, Damien Coraboeuf  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202407.1570550825000.8097.1586346000280%40Atlassian.JIRA.

[JIRA] (JENKINS-59706) Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl

2020-04-08 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf edited a comment on  JENKINS-59706  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl   
 

  
 
 
 
 

 
 Hi,We're using version 1.21.0 of BlueOcean on Jenkins LTS 2.204.1 and the problem persists :(Calls to {{/blue/rest/organizations/jenkins/computers/}} are so heavy that they freeze the browsers when accessing BlueOcean. We had to disable those calls at  firewall  proxy  level but this makes some features of BlueOcean not working any longer (like triggering a build from the branch view).We do have an installation with up to 125 transient EC2 nodes and thousands of jobs running every day.What could I provide which helps fixing the issue?Thanks,Damien Coraboeuf  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202407.1570550825000.8099.1586346000310%40Atlassian.JIRA.

[JIRA] (JENKINS-59966) Prometheus Plugin: Causes StackOverFlowerError

2019-11-27 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-59966  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prometheus Plugin: Causes StackOverFlowerError   
 

  
 
 
 
 

 
 We have the same issue in my company: 
 
Jenkins LTS 2.190.1 
Prometheus plugin 2.0.6 
 Stacktrace overflow as mentioned above. However, we do have a second Jenkins instance, with same version, and no issue there. So this must be somehow linked to some kind of setup.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202770.1572283306000.7829.1574872440348%40Atlassian.JIRA.

[JIRA] (JENKINS-58063) Config File Provider plugin 3.6.1 not available

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


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58063  
 
 
  Config File Provider plugin 3.6.1 not available   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Dominik Bartholdi  
 
 
Components: 
 config-file-provider-plugin  
 
 
Created: 
 2019-06-18 07:24  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Damien Coraboeuf  
 

  
 
 
 
 

 
 Hi, The config-file-provider-plugin plugin 3.6.1 is supposed to have been delivered on June 5th, but its still not available in any mirror (here for example: http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/config-file-provider/) This impedes the delivery of the JENKINS-57417 fix. Can somebody have a look? Thanks, Damien  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-57345) Cannot install Java on DO agents any longer

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


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

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

  
 
 
 
 

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

 

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

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

 

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

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

[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled

2018-08-22 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-45719  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Description for a pipeline run is not compatible and cannot be disabled   
 

  
 
 
 
 

 
 Hi, Is there any plan to get this fixed in a future version of the Blue Ocean plugin(s)? Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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

[JIRA] (JENKINS-42673) NPE when deleting a job

2017-03-10 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42673  
 
 
  NPE when deleting a job   
 

  
 
 
 
 

 
Change By: 
 Damien Coraboeuf  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-42673) NPE when deleting a job

2017-03-10 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-42673  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPE when deleting a job   
 

  
 
 
 
 

 
 Hi, I've created the https://github.com/jenkinsci/pipeline-milestone-step-plugin/pull/11 PR to fix this issue. A bit more context: this happens at Jenkins startup. We have some Groovy scripts in init.groovy.d which delete and recreate some basic infrastructure jobs. The NPE appeared on deletion after we had installed all the pipeline plug-ins, including the milestone one.   Best regards, Damien. <
 /td> 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-42673) NPE when deleting a job

2017-03-10 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42673  
 
 
  NPE when deleting a job   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Antonio Muñiz  
 
 
Components: 
 pipeline-milestone-step-plugin  
 
 
Created: 
 2017/Mar/10 4:41 PM  
 
 
Environment: 
 Jenkins 2.32.3, Pipeline Milestone Step plug-in 1.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Damien Coraboeuf  
 

  
 
 
 
 

 
 Hi,   When deleting a job programmatically, a non pipeline job, we have a NPE:   

 

Mar 10, 2017 4:23:21 PM hudson.model.listeners.ItemListener forAll
WARNING: failed to send event to listener of class org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete
java.lang.NullPointerException
at org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete.onDeleted(MilestoneStepExecution.java:348)
at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:205)
at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:203)
at hudson.model.listeners.ItemListener.forAll(ItemListener.java:167)
at hudson.model.listeners.ItemListener.fireOnDeleted(ItemListener.java:203)
at jenkins.model.Jenkins.onDeleted(Jenkins.java:2918)
at jenkins.model.Jenkins.onDeleted(Jenkins.java:324)
at hudson.model.AbstractItem.delete(AbstractItem.java:572)
at hudson.model.Job.delete(Job.java:683) 

   The getMilestonesByOrdinalByJob() method might return null and should be checked against this.   Best regards, Damien.

[JIRA] (JENKINS-31912) Extension point at the root of the DSL?

2017-01-17 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-31912  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extension point at the root of the DSL?   
 

  
 
 
 
 

 
 We imagined to use a script which does several activities: 
 
creation / update of jobs (and therefore using the DSL) 
doing other activities (like provisioning of Artifactory & Ontrack) 
 Of course, using a GroovyScriptEngine would make easy to run the last part, without any particular extension. Assuming the DSL JARs are in the classpath, plus all plugins contributing to it, would it work for the job generation part? Worth to test...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-31912) Extension point at the root of the DSL?

2017-01-17 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-31912  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extension point at the root of the DSL?   
 

  
 
 
 
 

 
 Hi Daniel, Yes, we would definitely need this. As such, it has nothing to do with the Seed plug-in, only with the fact that we need to run some code, as part of the pipeline (re)generation, to take care of other provisioning activities. So having the possibility to extend JobParent in our plugins, and to do our our business would definitely help. Now, I do not know how this would fit if we do not create any actual job.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-35232) Gradle JPI and JenkinsRule loading issues

2016-11-16 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Coraboeuf commented on  JENKINS-35232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gradle JPI and JenkinsRule loading issues   
 

  
 
 
 
 

 
 Hi Daniel, Indeed, I now work by listing all dependencies explicitly. You can close this ticket as a duplicate then. Thanks, Damien.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] [gradle-jpi-plugin] (JENKINS-35232) Gradle JPI and JenkinsRule loading issues

2016-05-31 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35232 
 
 
 
  Gradle JPI and JenkinsRule loading issues  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 gradle-jpi-plugin 
 
 
 

Created:
 

 2016/May/31 9:06 AM 
 
 
 

Environment:
 

 Gradle JPI 0.18.1  Jenkins 1.609.3 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Damien Coraboeuf 
 
 
 
 
 
 
 
 
 
 
Hi, 
I'm working on a plugin, the Seed plugin, and I'm using the Gradle JPI plugin for quite some time already. I've started to refactor my integration tests to use the JenkinsRule. 
My plugin depends on a number of plugins in order to work and I've the following configuration: 

 

jenkinsPlugins 'org.jenkins-ci.plugins:parameterized-trigger:2.26@jar'
jenkinsPlugins 'org.jenkins-ci.plugins:cloudbees-folder:4.7@jar'
jenkinsPlugins 'org.jenkins-ci.plugins:gradle:1.24@jar'
jenkinsPlugins 'org.jenkins-ci.plugins:envinject:1.92.1@jar'
jenkinsPlugins 'org.jenkins-ci.plugins:description-setter:1.10@jar'
jenkinsPlugins 'org.jenkins-ci.plugins:conditional-buildstep:1.3.3@jar'
jenkinsPlugins 'org.jenkins-ci.plugins:credentials:1.22@jar'
optionalJenkinsPlugins 'org.jenkins-ci.plugins:git:2.3.5@jar'
optionalJenkinsPlugins

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

2016-02-02 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
Since the org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro#evaluate(hudson.model.AbstractBuild, hudson.model.TaskListener, java.lang.String, java.util.Map, com.google.common.collect.ListMultimap) method is synchronised (since version 1.11), we have indeed a bottleneck when several builds need to resolve the token.  
It seems to be necessary because this class has some instance variables and cannot be shared between different threads. 
So in the end, this seems more a problem with the token-macro plugin than with the BFA or the email-ext plugin. I'll go and see if there is already an issue about this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

2016-02-02 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
Moving this issue to the token-macro-plugin component. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

2016-02-02 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
I've created the https://github.com/jenkinsci/token-macro-plugin/pull/21 pull request in an attempt to solve this bottleneck issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [job-dsl-plugin] (JENKINS-32742) Make environment contributors extensible

2016-02-02 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32742 
 
 
 
  Make environment contributors extensible  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 03/Feb/16 6:10 AM 
 
 
 

Environment:
 

 1.42 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Damien Coraboeuf 
 
 
 
 
 
 
 
 
 
 
Hi, 
The environmentVariables / contributors section should be made extensible in order to facilitate the inclusion of extensions. 
This is a simple update to do and I'm preparing the pull request. 
Damien. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

2016-02-02 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32331 
 
 
 
  Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 

Change By:
 
 Damien Coraboeuf 
 
 
 

Component/s:
 
 token-macro-plugin 
 
 
 

Component/s:
 
 build-failure-analyzer-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

2016-02-02 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
When analysing the stack traces, we see a lock between the email-ext token resolution and the BFA: 

 

"Executor #4 for be-bld-jen-02 : executing xxx #936" prio=10 tid=0x7fc45edfb000 nid=0x2040 waiting for monitor entry [0x7fc439f05000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:167)
	- waiting to lock <0x0006c58d5888> (a com.sonyericsson.jenkins.plugins.bfa.tokens.Token)
	at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:190)
	at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:242)
	at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:63)
	at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:698)
 

 
Upon BFA token resolution, the code asks the build to be scanned again, but this checks only if it the BFA action is there. It seems that there is a kind of a conflict here. 
We use email-ext 2.36 and token-macro 1.11. 
When we remove the BFA token from the mail generator, it's OK. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

2016-02-02 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32331 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 
 
We have reduced the number of concurrent scans per build from 3 to 1. It seems better now, but we're monitoring the situation. Especially, it could now cause the analysis to be longer than before. 
It would be nice to have a BFA dashboard showing the number of concurrent scans currently running. I'll try to work on this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances

2016-01-07 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32331 
 
 
 
  Performance problems on scan on huge Jenkins instances  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Tomas Westling 
 
 
 

Components:
 

 build-failure-analyzer-plugin 
 
 
 

Created:
 

 07/Jan/16 2:33 PM 
 
 
 

Environment:
 

 Jenkins 1.584  Build Failure Analyser 1.12.1 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Damien Coraboeuf 
 
 
 
 
 
 
 
 
 
 
Hi, 
On a Jenkins 1.584, using Build Failure Analyser 1.12.1, we host more than 2600 jobs, and we have 123 different BFA rules. 
Our log files can be fairly big (ranging from 5Mb to 100 Mb in some exceptional cases) and we have started to have serious performance issues, where the BFA scan on a failing build can take up to 15 minutes. This is of course a big issue. 
By looking at the code, I've seen that the scan of a log is performed once per rule being defined, and then line by line. This is of course very costly in our case. 
Do you have any suggestion about this kind of situation? 
Thanks, Damien.

[JIRA] [job-dsl-plugin] (JENKINS-32285) Consider BuildParametersContext to be extensible

2016-01-05 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf started work on  JENKINS-32285 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Damien Coraboeuf 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [job-dsl-plugin] (JENKINS-32285) Consider BuildParametersContext to be extensible

2016-01-05 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-32285 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Consider BuildParametersContext to be extensible  
 
 
 
 
 
 
 
 
 
 
Hi, 
I have created the https://github.com/jenkinsci/job-dsl-plugin/pull/713 pull request to help making this happen. 
Best regards, Damien. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [job-dsl-plugin] (JENKINS-32285) Consider BuildParametersContext to be extensible

2016-01-04 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32285 
 
 
 
  Consider BuildParametersContext to be extensible  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 04/Jan/16 8:01 PM 
 
 
 

Environment:
 

 1.41 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Damien Coraboeuf 
 
 
 
 
 
 
 
 
 
 
Hi, 
It would be a plus to allow some plugins to contribute to the parameters section of the job DSL, in case they provide additional types of parameters. 
Looking at the code (1.41), I see that the BuildParametersContext class stores the nodes to be created as a map (in order to guarantee uniqueness of parameter names I assume). This does make this easy to make this class extend the AbstractExtensibleContext and to implement the addExtensionNode method. 
Can we safely assume that the node would have a name field, so we can index it? That would allow for an easy implementation. 
Best regards, Damien.

[JIRA] [job-dsl-plugin] (JENKINS-31912) Extension point at the root of the DSL?

2015-12-04 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31912 
 
 
 
  Extension point at the root of the DSL?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 04/Dec/15 7:53 PM 
 
 
 

Labels:
 

 extension 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Damien Coraboeuf 
 
 
 
 
 
 
 
 
 
 
Hi, 
Would it be possible to have an extension point, through a dedicated ExtensibleContext, which allows to add some code at the root of a DSL, at the same level than job and co? 
The use case is as follows: among activities we want to achieve when generating the jobs of a pipeline, we want to perform other tasks, like creating branches in Ontrack or initialising some repositories in Artifactory. 
The current way we do it is to generate a setup job which is queued automatically at the end of the pipeline generation, but that's a bit heavy. 
It would be neat if we could call some plugin's code, through an extension or directly.

[JIRA] [workflow-plugin] (JENKINS-31152) 2.0: Pipeline as code in front & center

2015-10-29 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-31152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 2.0: Pipeline as code in front & center  
 
 
 
 
 
 
 
 
 
 
FYI, we manage more than 1500 jobs at my client today and we have designed the Seed plugin to go even further in the simplification of the job generation and management, by providing development teams a way to provide at SCM level a shopping list (a property file) which refers to a versioned pipeline library maintained by a core team. 
This pipeline library uses the Job DSL plugin but could also use the Workflow plugin. The idea behind the Seed plugin is to manage branches and projects on a very large scale, for people who do not know very well Jenkins. 
Feel free to check it at https://wiki.jenkins-ci.org/display/JENKINS/Seed+Plugin 
I'm very interested in the development of this new core integration of the pipeline as code, and see how I could in the future integrate it with this concept of shopping list. 
Damien. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [core] (JENKINS-21930) Jobs fail due to node went offline during the build

2015-06-05 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-21930 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Jobs fail due to node went offline during the build  
 
 
 
 
 
 
 
 
 
 
Hi, 
We experiment this issue on Jenkins 1.584. 
The scenario is the following: 
 

we have a job which puts a node offline in order to run some maintenance on it, using the computer.setTemporarilyOffline(true, new OfflineCause.UserCause(User.current(), Putting the slave offline for maintenance purpose)) code
 

some jobs are still running on this node
 

some of those still running jobs are then failing because of the error mentioned in this issue - not always, but time to time
 
 
Do you know if a workaround or solution has been found for this problem? 
Thanks, Damien. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [core] (JENKINS-21930) Jobs fail due to node went offline during the build

2015-06-05 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-21930 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Jobs fail due to node went offline during the build  
 
 
 
 
 
 
 
 
 
 
It seems the code mentioned above does not exist any longer. Might it be that it has been solved for another ticket? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [core] (JENKINS-21930) Jobs fail due to node went offline during the build

2015-06-05 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-21930 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Jobs fail due to node went offline during the build  
 
 
 
 
 
 
 
 
 
 
After analysis of the stack trace and of the code of 1.584, it happens after the run is complete, when the AbstractBuildRunner attempts to write the annotated log. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build

2015-05-04 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf commented on  JENKINS-28188 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: StringIndexOutOfBoundsException when no root cause for the build  
 
 
 
 
 
 
 
 
 
 
Hi Daniel, 
I'm using the following piece of code: 

 

final AbstractProject job = ...
ListParameterValue parameterValues = ...
Jenkins.getInstance().getQueue()
.schedule2(
job,
0,
new ParametersAction(parameterValues),
new CauseAction(getCause(channel))
);
 

 
where getCause returns a custom cause. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build

2015-05-04 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf edited a comment on  JENKINS-28188 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: StringIndexOutOfBoundsException when no root cause for the build  
 
 
 
 
 
 
 
 
 
 HiDaniel,I'musingthefollowingpieceofcode:{code}finalAbstractProjectjob=...ListParameterValueparameterValues=...Jenkins.getInstance().getQueue().schedule2(job,0,newParametersAction(parameterValues),newCauseAction(getCause(channel)));{code}where{{getCause}}returnsacustomcause. Myinitialcodein{{getCause}}wasactuallyananonymousclassforthe{{Cause}}implementation,andthatcausesactuallytheproblem.Byreplacingtheanonymous{{Cause}}implementationbyatoplevelclassfixedtheproblemonmyside. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build

2015-05-04 Thread damien.corabo...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damien Coraboeuf edited a comment on  JENKINS-28188 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: StringIndexOutOfBoundsException when no root cause for the build  
 
 
 
 
 
 
 
 
 
 HiDaniel,I'musingthefollowingpieceofcode:{code}finalAbstractProjectjob=...ListParameterValueparameterValues=...Jenkins.getInstance().getQueue().schedule2(job,0,newParametersAction(parameterValues),newCauseAction(getCause(channel)));{code}where{{getCause}}returnsacustomcause.Myinitialcodein{{getCause}}wasactually returning ananonymousclassforthe{{Cause}}implementation,andthat causesactually caused theproblem.Byreplacingtheanonymous{{Cause}}implementationbyatoplevelclassfixedtheproblemonmyside. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build

2015-05-02 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 created  JENKINS-28188


StringIndexOutOfBoundsException when no root cause for the build















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


envinject-plugin



Created:


02/May/15 9:44 PM



Description:


When a build has no root cause (possible when firing the job programmatically), the code at org.jenkinsci.plugins.envinject.service.BuildCauseRetriever#buildCauseEnvironmentVariables produces a StringIndexOutOfBoundsException because the substring method is applied to an empty string.




Environment:


EnvInject 1.91.2




Project:


Jenkins



Priority:


Major



Reporter:


Damien Coraboeuf

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build

2015-05-02 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 started work on  JENKINS-28188


StringIndexOutOfBoundsException when no root cause for the build
















Change By:


Damien Coraboeuf
(02/May/15 9:53 PM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build

2015-05-02 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-28188


StringIndexOutOfBoundsException when no root cause for the build















There is a pull request at https://github.com/jenkinsci/envinject-plugin/pull/49 to fix this issue.

Best regards,
Damien.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-28171) Missing lookupStrategy configuration for the DSL step

2015-04-30 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 created  JENKINS-28171


Missing lookupStrategy configuration for the DSL step















Issue Type:


Improvement



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


30/Apr/15 12:37 PM



Description:


Hi,

In the version 1.32, there is no way to configure the lookupStrategy property using the dsl closures.

Is that foreseen to add?

Thanks,
Damien.




Environment:


job-dsl 1.32




Project:


Jenkins



Priority:


Major



Reporter:


Damien Coraboeuf

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-28171) Missing lookupStrategy configuration for the DSL step

2015-04-30 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-28171


Missing lookupStrategy configuration for the DSL step















Pull request created at https://github.com/jenkinsci/job-dsl-plugin/pull/465

Current workaround is to not use the dsl block, but to configure it using the configure block.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-28171) Missing lookupStrategy configuration for the DSL step

2015-04-30 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 started work on  JENKINS-28171


Missing lookupStrategy configuration for the DSL step
















Change By:


Damien Coraboeuf
(30/Apr/15 1:00 PM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests

2015-04-29 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-27994


The Manifest of the job-dsl JAR is empty, making it unuseable for tests















Thanks Daniel. Do I create a PR for the Job DSL plugin to take this version into account, or do you do it?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-28048) Allow DslScriptLoader classloading customisation for reuse in other plug-ins

2015-04-23 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-28048


Allow DslScriptLoader classloading customisation for reuse in other plug-ins















In order to add more context, I'd like to be able to call the Job DSL from within another plug-in. In the DSL scripts, I want to refer to classes and methods which are in my plug-in.

As of version 1.32, the class loader for the DslScriptLoader does not allow to look for those classes.

I have fiddled around with passing variables in the scope (see this commit - no pull request yet) but this does not resolve the class loading issues.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-28048) Allow DslScriptLoader classloading customisation for reuse in other plug-ins

2015-04-22 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 created  JENKINS-28048


Allow DslScriptLoader classloading customisation for reuse in other plug-ins















Issue Type:


Improvement



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


22/Apr/15 6:54 PM



Description:


The DslScriptLoader class can be used from other plug-ins in order to bring the benefits of using the Job DSL capabilities.

However, in the current state (version 1.32), the DslScriptLoader does not allow further configuration about the class loader, making impossible to inject helpers and other classes in the DSL script being run.

The DslScriptLoader.runDslEngineForParent could be refactored in order to allow for further configuration.

I'll try to propose a pull request for this - but I'd like to have some additional opinion on this.

The context remains the reuse of the Job DSL capabilities from within another plug-in.

Best regards,
Damien.




Environment:


job-dsl 1.32




Project:


Jenkins



Priority:


Major



Reporter:


Damien Coraboeuf

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests

2015-04-17 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 created  JENKINS-27994


The Manifest of the job-dsl JAR is empty, making it unuseable for tests















Issue Type:


Bug



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


17/Apr/15 1:02 PM



Description:


Hi,

I'm using the Job DSL plug-in from another plug-in, and need to use it for my integration tests as well:


dependencies {
...
jenkinsPlugins 'org.jenkins-ci.plugins:job-dsl:1.32@jar'
...
}


I'm using the JenkinsRule and it fails because it cannot resolve job-dsl:1.32. After looking into the code of JenkinsRule, I've seen that the JAR location is fetched using Manifest information, in the Short-Name attribute.

Although this information is filled in correctly in the JPI file, it is absent in the JAR file. I had a look at other plug-ins, and the manifest information is generated for both the JAR and the HPI/JPI file. So it might have something to do with the Gradle JPI plug-in.

In order to make the Job DSL plug-in useable from other plug-ins, especially in their integration tests using the JenkinsRule, the JAR needs the Manifest information.

Best regards,
Damien.




Project:


Jenkins



Priority:


Major



Reporter:


Damien Coraboeuf

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests

2015-04-17 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 updated  JENKINS-27994


The Manifest of the job-dsl JAR is empty, making it unuseable for tests
















Change By:


Damien Coraboeuf
(17/Apr/15 2:50 PM)




Component/s:


gradle-jpi-plugin



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test

2015-04-17 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-27826


Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test















I confirm that adding the matrix-project fixes the problem:


dependencies {
   ...
   jenkinsPlugins 'org.jenkins-ci.plugins:matrix-project:1.4@jar'
   ...
}




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests

2015-04-17 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-27994


The Manifest of the job-dsl JAR is empty, making it unuseable for tests















Hi,

I've created a pull request which solves this problem:

https://github.com/jenkinsci/gradle-jpi-plugin/pull/50

If accepted, the new version of the gradle-jpi-plugin should be applied to job-dsl and new version of the plug-in created.

Best regards,
Damien.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-26746) Very slow when there are many folders and projects.

2015-02-03 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-26746


Very slow when there are many folders and projects.















We are facing the same issue in our Jenkins production environment, which contains many folders and jobs. Looking forward to a new release containing this fix.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [delivery-pipeline-plugin] (JENKINS-25607) Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed

2014-11-14 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-25607


Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed















Error shows:


java.lang.NoSuchMethodError: au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.init(Ljava/lang/String;Ljava/lang/String;Lau/com/centrumsystems/hudson/plugin/buildpipeline/ProjectGridBuilder;Ljava/lang/String;ZLjava/lang/String;Z)V




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [disk-usage-plugin] (JENKINS-25382) Support for the Folder plug-in

2014-10-30 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 created  JENKINS-25382


Support for the Folder plug-in















Issue Type:


Improvement



Assignee:


Lucie Votypkova



Components:


disk-usage-plugin



Created:


30/Oct/14 5:37 PM



Description:


The disk usage plug-in (v 0.23) does not display disk usage for the items created with the Folder plug-in (v 4.6.1 - https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin).

For normal jobs, everything is fine.




Project:


Jenkins



Priority:


Major



Reporter:


Damien Coraboeuf

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [swarm] (JENKINS-7543) Set tool locations from Swarm plugin CLI

2014-10-02 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-7543


Set tool locations from Swarm plugin CLI















Great news. Thanks!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [envinject] (JENKINS-18595) Uncaught TypeError when opening configuration of project (Jenkins 1.521)

2013-07-03 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-18595


Uncaught TypeError when opening configuration of project (Jenkins 1.521)















Will it be fixed asap for the 1.522?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-flow] (JENKINS-16135) Build Flow dependency graph doesn't render on job status page

2013-04-16 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-16135


Build Flow dependency graph doesnt render on job status page















Hi,

We will definitely install version 0.9 (waiting for a restart window in our heavy build schedule, not so easy). I'll then test and hopefully close this ticket.

Regards,
Damien.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-flow] (JENKINS-16135) Build Flow dependency graph doesn't render on job status page

2013-04-16 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-16135


Build Flow dependency graph doesnt render on job status page















Version 0.9 installed. It looks OK for me and this issue can be closed as far as I am concerned.

Thanks,
Damien.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] (JENKINS-15900) A build failure in a parallel section does not mark it as failed

2013-02-28 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-15900


A build failure in a parallel section does not mark it as failed















I'll plan an upgrade of our company Jenkins to version 0.8, and I'll give feedback here.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] (JENKINS-16135) Build Flow dependency graph doesn't render on job status page

2013-02-27 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-16135


Build Flow dependency graph doesnt render on job status page















The https://github.com/jenkinsci/build-flow-plugin/pull/20 pull request looks very promising, but I'm waiting a new 0.9 version before trying it out.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] (JENKINS-16135) Build Flow dependency graph doesn't render on job status page

2012-12-19 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-16135


Build Flow dependency graph doesnt render on job status page















Same issue with Jenkins 1.487. We plan to revert to 0.5, waiting for a correction or any work-around.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15900) A build failure in a parallel section does not mark it as failed

2012-11-22 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 created  JENKINS-15900


A build failure in a parallel section does not mark it as failed















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


build-flow



Created:


22/Nov/12 1:53 PM



Description:


Using version 0.5, I still get this problem. Using the following flow:


guard {
   build ("test-a")
   parallel (
  { build("test-b") },
  { build("test-c") }
   )
   parallel (
  { build("test-d") },
  { build("test-e") }
   )
} rescue {
   build ("test-f")
}



Whenever "test-b" job fails (for example), "test-d" and "test-e" will be executed still. Is there something wrong with the syntax?




Project:


Jenkins



Priority:


Critical



Reporter:


Damien Coraboeuf

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15900) A build failure in a parallel section does not mark it as failed

2012-11-22 Thread damien.corabo...@gmail.com (JIRA) 














































Damien Coraboeuf
 commented on  JENKINS-15900


A build failure in a parallel section does not mark it as failed















I have found a workaround:


guard {
   build ("test-a")
   // Fast running jobs
   def fast = parallel (
  { build("test-b") },
  { build("test-c") }
   )
   // Slow running jobs
   def fastFailed = fast*.getResult()*.toString().any { result - !"SUCCESS".equals(result) }
   if (!fastFailed) {
  parallel (
 { build("test-d") },
 { build("test-e") }
  )
   }
} rescue {
   build ("test-f")
}



It is not very nice but it does the trick...

Damien.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira