[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones

2018-11-08 Thread mgau...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin commented on  JENKINS-35708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Plugin: Ability to round robin EC2 availability zones   
 

  
 
 
 
 

 
 Hi Francis Upton, I guess the status does not reflect the reality. If I'm not wrong, the fix has been delivered into the 1.41 release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones

2018-10-08 Thread mgau...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin commented on  JENKINS-35708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Plugin: Ability to round robin EC2 availability zones   
 

  
 
 
 
 

 
 Hi David Fluck, we have a good chance to see your PR #295 reviewed soon since new maintainers work actively on this plugin! \o/ Did you see Matt Sicker 's comment on your PR?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-35708) EC2 Plugin: Ability to round robin EC2 availability zones

2018-08-28 Thread mgau...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin commented on  JENKINS-35708  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Plugin: Ability to round robin EC2 availability zones   
 

  
 
 
 
 

 
 Hi Francis Upton, any chance to review David Fluck's PR (#295) soon?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud

2018-04-10 Thread mgau...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin commented on  JENKINS-47254  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for building tags for Bitbucket Server/Cloud   
 

  
 
 
 
 

 
 Eduard Weiss, can you review Antonio's feedback on your PR #113 please? It will be nice if we succeed to have this feature ready. Thanks for your involvement.  
 

  
 
 
 
 

 
 
 

 
 
 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-49404) A way to force some settings on all jobs in the instance

2018-02-12 Thread mgau...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49404  
 
 
  A way to force some settings on all jobs in the instance   
 

  
 
 
 
 

 
Change By: 
 Mikael Gaunin  
 

  
 
 
 
 

 
 We would like to be able to force some settings on all jobs in the instance somehow In our case:1) Not run concurrent builds. If a build is in progress and another build is in the queue, do not allow any further builds to be triggered or queued. This can be set in individual jobs already but we want to make it an instance setting we apply to all job types on that instance2) Abort after a certain running time. Again, users are able to set this on individual jobs but would like to impose this restriction at instance level to prevent jobs from overrunning and hoarding executors  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-34942) sonar runner configurations lost in jobs configurations since moved to 'global tools config' section

2016-08-12 Thread mgau...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin commented on  JENKINS-34942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: sonar runner configurations lost in jobs configurations since moved to 'global tools config' section   
 

  
 
 
 
 

 
 This ticket should be closed, shouldn't it? (cf. SONARJNKNS-255)  
 

  
 
 
 
 

 
 
 

 
 
 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-33833) Lost the batch task history since 1.634

2016-06-21 Thread mgau...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikael Gaunin commented on  JENKINS-33833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lost the batch task history since 1.634   
 

  
 
 
 
 

 
 Tom FENNELLY do not hesitate if you need help, I'll be there!  
 

  
 
 
 
 

 
 
 

 
 
 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] [batch-task-plugin] (JENKINS-33833) Lost the batch task history since 1.634

2016-05-31 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin edited a comment on  JENKINS-33833 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Lost the batch task history since 1.634  
 
 
 
 
 
 
 
 
 
 I looked deeper into the code trying to understand the cause of the issue.I'm pretty sure that the changes on build history, pagination and so on, done by  @  [~ tfennelly ]  (seen in [Comparing changes 1.632...1.633|https://github.com/jenkinsci/jenkins/compare/jenkins-1.632...jenkins-1.633]), could explain the empty pane for batch tasks.Indeed, from the [Batch Task Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin], BatchRun extends Actionable only. I did a quick test to make this class extends Queue.Item, here the results:!BatchTasksBuildHistory_Queue.Item.png|thumbnail!Not so good but Tom, maybe you see from where the issue comes from.Thanks for your help 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [batch-task-plugin] (JENKINS-33833) Lost the batch task history since 1.634

2016-05-31 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33833 
 
 
 
  Lost the batch task history since 1.634  
 
 
 
 
 
 
 
 
 
 
I looked deeper into the code trying to understand the cause of the issue. I'm pretty sure that the changes on build history, pagination and so on, done by @tfennelly (seen in Comparing changes 1.632...1.633), could explain the empty pane for batch tasks. Indeed, from the Batch Task Plugin, BatchRun extends Actionable only. I did a quick test to make this class extends Queue.Item, here the results:  Not so good but Tom, maybe you see from where the issue comes from. Thanks for your help 
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikael Gaunin 
 
 
 

Attachment:
 
 BatchTasksBuildHistory_Queue.Item.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module

2016-05-09 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin edited a comment on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 Fyi, the workaround asking the java downgrade to version 7 works well. As a summary:* Master and slaves running with Java 8 => some builds fails with such exception:{quote}10:14:43 ERROR: Build step failed with exception10:14:43 java.lang.IllegalStateException (http://stacktrace.jenkins-ci.org/search?query=java.lang.IllegalStateException) : Invalid object ID 52 iota=53{quote}* +Upgrading+ them to the +latest Java 8 release+ (here 1.8.0_92) *does not fix the issue*.* +Downgrading+ Master and slaves to +Java 7+ (here 1.7.0_79) *solved the problem*. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module

2016-05-09 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
Fyi, the workaround asking the java downgrade to version 7 works well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

2016-04-19 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin commented on  JENKINS-25583 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unexpected error in launching a slave. This is probably a bug in Jenkins.  
 
 
 
 
 
 
 
 
 
 
Glad to read your comment Rouke Broersma Inform us about the release thru this ticket. Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

2016-04-08 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin commented on  JENKINS-25583 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unexpected error in launching a slave. This is probably a bug in Jenkins.  
 
 
 
 
 
 
 
 
 
 
Richard Lavoie your fix is validated. Any chance to generate a release soon? Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [batch-task-plugin] (JENKINS-33833) Lost the batch task history since 1.634

2016-03-27 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin commented on  JENKINS-33833 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Lost the batch task history since 1.634  
 
 
 
 
 
 
 
 
 
 
I assure you that the steps to reproduce are complete; with 1.632 (or older versions) and 1.634 (or newer versions) and 

without installing
 the EnvInject Plugin, you don't have this issue (ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver). As a remark, with the 1.633 version, we have the issue with or without the EnvInject 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] [batch-task-plugin] (JENKINS-33833) Lost the batch task history since 1.634

2016-03-27 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33833 
 
 
 
  Lost the batch task history since 1.634  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikael Gaunin 
 
 
 
 
 
 
 
 
 
 The Batch task history panel is empty (_Find pane only_) since the 1.634 version. Maybe linked, a blocking bug has been introduced within the 1.633 version (cf. JENKINS-30820) that impeded to add any batch task on job.I guess the bug comes from the core but maybe the [Batch Task Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Batch+Task+Plugin] should be upgraded (?)*Use case*To reproduce:* install the Batch Tasks plugin* create an empty freestyle job with Batch tasks option (_echo "Hello world"_)* run  a build* run  the task several times * look at the task build history (_/job//batchTasks/task//_)Tested with 1.616, 1.632: the batch history panel displayed all the builds.Tested with 1.633: cannot access to my job. Create a new one, cannot create Batch task because of _ClassNotFoundException: org.jenkinsci.lib.envinject.service.EnvVarsResolver_Tested with 1.634, 1.642.3: the batch history panel is empty (_Find pane only_) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [batch-task-plugin] (JENKINS-33833) Lost the batch task history since 1.634

2016-03-26 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33833 
 
 
 
  Lost the batch task history since 1.634  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 batch-task-plugin, core 
 
 
 

Created:
 

 2016/Mar/26 7:27 AM 
 
 
 

Environment:
 

 1.634 or higher + Batch Task Plugin 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Mikael Gaunin 
 
 
 
 
 
 
 
 
 
 
The Batch task history panel is empty (Find pane only) since the 1.634 version.  Maybe linked, a blocking bug has been introduced within the 1.633 version (cf. 

JENKINS-30820
) that impeded to add any batch task on job. I guess the bug comes from the core but maybe the Batch Task Plugin should be upgraded  
Use case To reproduce: 
 

install the Batch Tasks plugin
 

create an empty freestyle job with Batch tasks option (echo "Hello world")
 

run the task several

[JIRA] [core] (JENKINS-33127) Wrong HTTP status code when Internal server error occurs

2016-02-24 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33127 
 
 
 
  Wrong HTTP status code when Internal server error occurs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikael Gaunin 
 
 
 
 
 
 
 
 
 
 Hi,When the "Error: Exception" with a stack trace was produced, the Jenkins winstone service reported a healthy HTTP 200 status code. I believe this should have reported an HTTP 500 internal server error. Here's how the status codes should be as I see it...* HTTP 503 Service Unavailable - Jenkins is booting, please wait... * HTTP 403 forbidden - accessing resources not authorized. * HTTP 401 authorization required - accessing URLs while not authenticated. * HTTP 500 Internal server error - an internal Jenkins exception occurred.*Use case*I encounter issues when upgrading: * Folders plugin from 5.1 to 5.2.1 * Matrix Authorization Strategy Plugin from 1.2 to 1.3.{quote}hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:935) at jenkins.model.Jenkins.(Jenkins.java:816) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:924) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) ... 8 more Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at hudson.ExtensionList.get(ExtensionList.java:171) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1347) at hudson.maven.PluginImpl.init(PluginImpl.java:58) ... 13 more{quote}Some additional notes: * When I disable security, the issue remains and Jenkins is unusable - https://wiki.jenkins-ci.org/display/JENKINS/Disable+security * Even when I bootstrap again and upgrade _all_ of the plugins and not just those two I still get the error.  * I have attached the console.log so you can see additional exceptions from the command line. console.log is a fresh 

[JIRA] [core] (JENKINS-33127) Wrong HTTP status code when Internal server error occurs

2016-02-24 Thread mgau...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33127 
 
 
 
  Wrong HTTP status code when Internal server error occurs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 console.logs.tar.gz 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 24/Feb/16 1:53 PM 
 
 
 

Environment:
 

 Jenkins  ===  Version details  ---    * Version: `1.648`    * Mode: WAR    * Url: http://localhost:8080/    * Servlet container    - Specification: 3.0    - Name: `jetty/winstone-2.9`    * Java    - Home: `/Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/jre`    - Vendor: Oracle Corporation    - Version: 1.8.0_65    - Maximum memory: 3.95 GB (4242538496)    - Allocated memory: 3.95 GB (4242538496)    - Free memory: 3.48 GB (3734565496)    - In-use memory: 484.44 MB (507973000)    - GC strategy: ParallelGC   Important configuration  ---    * Security realm: `org.jenkinsci.plugins.GithubSecurityRealm`    * Authorization strategy: `hudson.security.ProjectMatrixAuthorizationStrategy`   Active Plugins  --    * ace-editor:1.0.1 '_javascript_ GUI Lib: ACE Editor bundle plugin'    * ansicolor:0.4.2 'AnsiColor'    * antisamy-markup-formatter:1.3 'OWASP Markup Formatter Plugin'    * async-http-client:1.7.24 'Async Http Client'    * authentication-tokens:1.2 'Authentication Tokens API Plugin'    * aws-java-sdk:1.10.45 'Amazon Web Services SDK'    * build-timeout:1.16 'Jenkins build timeout plugin'    * build-view-column:0.2 'Build View Column Plugin'    * cloudbees-credentials:3.3 'CloudBees Credentials Plugin'    * cloudbees-folder:5.1 *(update available)* 'CloudBees Folders Plugin'    * cobertura:1.9.7 'Jenkins Cobertura Plugin'    * console-column-plugin:1.5 'Console Column Plugin'    * copyartifact:1.37 'Copy Artifact Plugin'    * covcomplplot:1.1.1 'Coverage/Complexity Scatter Plot PlugIn'    * credentials:1.25 'Credentials Plugin'    * dashboard-view:2.9.7 'Dashboard View'    * deployed-on-column:1.7 'Deployed