[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-04 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 Also fixed with 3.4.1 here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54399) Configuration page no longer loads

2018-11-02 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 Also seeing this on Jenkins 2.149. Rollback to 3.3 fixes 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-08 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu edited a comment on  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
 Fixed by downgrading to a  non-corrupt  gradle plugin version  with matching checksums .  
 

  
 
 
 
 

 
 
 

 
 
 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-08 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu updated  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed by downgrading to a non-corrupt gradle plugin version.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53906  
 
 
  Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
Change By: 
 Frank Shimizu  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-08 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu commented on  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
 Update to 2.145 was successful too. Again thanks for the helpful information. I'm setting this issue to Resolved.  
 

  
 
 
 
 

 
 
 

 
 
 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-08 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu commented on  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
 Thank you for all the information so far, especially about the deprecation of ruby-runtime. I was able to disable ruby-runtime since we do not seem to actually use its dependency. Which is the GitLab Hook Plugin.   I also manually downgraded the gradle plugin to 1.24 which for me seems to be the latest release with matching checksums. Now the Jenkins update to 2.144 seems to have succeeded. Jenkins starts up successfully, the many Exceptions in the log are gone and we're testing whether everything works. I may also proceed to update to 2.145 since it's available now.   Not sure if the issue with the gradle plugin checksums happens only to us or others too. Should I close this issue if we find no more problems with the update and create a new one concerning the gradle plugin checksums?  
 

  
 
 
 
 

 
 
 

 
 
 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-05 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu edited a comment on  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
 [~jglick], I set up Jenkins 2.142 from scratch in Docker with jenkins/jenkins:2.142 and installed the exact same plugins as on our production system.  Otherwise  I did no configuration or otherwise. Then I updated to 2.144 by deleting the Docker container and starting a new one with the :2.144 image. I could not reproduce the problem; Jenkins starts normally.Something I noticed:I had to manually download the hpi files for the ruby-runtime and gradle plugins  because of download/checksum errors . ruby-runtime was manually installed without a problem. gradle initially failed the automatic installation because of a checksum error. I downloaded gradle plugin 1.29 from [https://updates.jenkins-ci.org/download/plugins/gradle/] and indeed the checksums don't match. I still installed it manually via the Advanced -> Upload Plugin function and despite some errors it was successfully installed. Then after updating Jenkins to 2.144, there were now many Exceptions related to hudson.plugins.gradle.Messages during startup. But Jenkins 2.144 still successfully started. I will try again to reproduce this next week.  
 

  
 
 
 
 

 
 
 

 
 
 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-05 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu commented on  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
 Jesse Glick, I set up Jenkins 2.142 from scratch in Docker with jenkins/jenkins:2.142 and installed the exact same plugins as on our production system. Otherwise I did no configuration or otherwise. Then I updated to 2.144 by deleting the Docker container and starting a new one with the :2.144 image. I could not reproduce the problem; Jenkins starts normally. Something I noticed: I had to manually download the hpi files for the ruby-runtime and gradle plugins. ruby-runtime was manually installed without a problem. gradle initially failed the automatic installation because of a checksum error. I downloaded gradle plugin 1.29 from https://updates.jenkins-ci.org/download/plugins/gradle/ and indeed the checksums don't match. I still installed it manually via the Advanced -> Upload Plugin function and despite some errors it was successfully installed. Then after updating Jenkins to 2.144, there were now many Exceptions related to hudson.plugins.gradle.Messages during startup. But Jenkins 2.144 still successfully started. I will try again to reproduce this next week.  
 

  
 
 
 
 

 
 
 

 
 
 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-05 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu commented on  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
 I updated Jenkins from 2.142 to 2.143 and I get the same error when trying to start after updating. Again, a downgrade to 2.142 solves the 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-05 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu commented on  JENKINS-53906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
 Daniel Beck, I may be able to try upgrading to 2.143 later today. I'll report back.  
 

  
 
 
 
 

 
 
 

 
 
 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-53906) Jenkins fails to start with Exception after update to 2.144

2018-10-05 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53906  
 
 
  Jenkins fails to start with Exception after update to 2.144   
 

  
 
 
 
 

 
Change By: 
 Frank Shimizu  
 
 
Summary: 
 Jenkins fails to start with Exception after update to 2. 142 144  
 

  
 
 
 
 

 
 
 

 
 
 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-53906) Jenkins fails to start with Exception after update to 2.142

2018-10-04 Thread frank.shim...@est.fujitsu.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Shimizu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53906  
 
 
  Jenkins fails to start with Exception after update to 2.142   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Stefan Wolf  
 
 
Attachments: 
 1.txt, 2.txt, 3.txt, 4.txt, 5.txt  
 
 
Components: 
 core, gradle-plugin  
 
 
Created: 
 2018-10-04 12:07  
 
 
Environment: 
 Operating system: CentOS release 6.10 x86_64  JRE running Jenkins: OpenJDK 1.8.0_181-b13  Jenkins version: 2.144 (updated from 2.142), installed via yum from repository  Gradle Plugin: 1.29  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Frank Shimizu  
 

  
 
 
 
 

 
 After updating Jenkins from 2.142 to 2.144 via yum, Jenkins does not successfully start up. On accessing the web UI the following exception is displayed: 

 

java.lang.IllegalArgumentException: Comparison method violates its general contract!
	at java.util.ComparableTimSort.mergeHi(ComparableTimSort.java:866)
	at java.util.ComparableTimSort.mergeAt(ComparableTimSort.java:483)
	at java.util.ComparableTimSort.mergeForceCollapse(ComparableTimSort.java:422)
	at java.util.ComparableTimSort.sort(ComparableTimSort.java:222)
	at java.util.Arrays.sort(Arrays.java:1312)
	at java.util.Arrays.sort(Arrays.java:1506)
	at java.util.ArrayList.sort(ArrayList.java:1462)
	at java.util.Collections.sort(Collections.java:141)
	at hudson.ExtensionList.sort(ExtensionList.java:400)
	at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
	at