[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner edited a comment on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Hi Tomas.It is not deleted immediately, apperantly it is deleted when global jenkins configuration is saved, but I will test reproducability, and document in the new bug. https://issues.jenkins-ci.org/browse/JENKINS-59610 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.20.1569837284000.9427.1569967809061%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Hi Stephen. I agree that your bug sounds a lot like this and the other I have submitted because Tomas couldn't reproduce this bug. I think this one: https://issues.jenkins-ci.org/browse/JENKINS-59610 is closely related to your https://issues.jenkins-ci.org/browse/JENKINS-59593 Br Jens 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.20.1569837284000.9424.1569967560234%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Jens Brejner created an issue Jenkins / JENKINS-59610 Build failure causes are deleted when saving Jenkins global configuration. Issue Type: Bug Assignee: Tomas Westling Attachments: bfa_settings.PNG, pluginslist.txt Components: build-failure-analyzer-plugin Created: 2019-10-01 14:10 Environment: Windows, jdk1.8.0_141, Jenkins LTS 2.190.1. Installed plugin list in attached file. Priority: Blocker Reporter: Jens Brejner Basically a new build-failure-analyzer.xml configuration file with default settings is written when "Save" is clicked in Jenkins global configuration (http://jenkins_ulr/configure). I also observed that when installing build-failure-analyzer first time, then restart Jenkins, still there is no build-failure-analyzer.xml in JENKINS_HOME. If I change a global setting and click save, the file appears. If I add a failure cause, and and use it, it stays and is visible in build-failure-analyzer.xml. And the failure cause is still there after restarting Jenkins. But if I change the global configuration, the modifed file is overwritten with default settings, which means that I effectively loose all my failure causes. My BFA global settings are in the screenshot, and I notice alse that it defaults to enable the gerrit-trigger notifications, although that plugin is not installed. Reproduce: Install Jenkins, install all mentioned plugins except BFA Install BFA, restart Jenkins, Notice there is no BFA configuration file Change a global setting and save. Notice BFA configuration file now exist Add a failure cause - do what ever, the
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Hi Tomas. It is not deleted immediately, apperantly it is deleted when global jenkins configuration is saved, but I will test reproducability, and document in the new bug. 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.20.1569837284000.8926.1569937020367%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Ups - NOT happy. I do not know if this bug is build-failure-analyzer, but If I make a change to the global jenkins configuration - which also have settings from BFA, and save, then all my failure causes are deleted That is really bad. Do you want me to log a new bug for this ? 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.20.1569837284000.8608.1569928500101%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Hi Tomas. I get the same behaviour, so I think it is not related to the bug mentioned. But I have made it work now. What I did: shut down Jenkins Remove build-failure-analyzer.jpi and folder from plugins folder Rename build-failure-analyzer.xml Start Jenkins Install Build-failure-analyzer Restart Jenknis Add a failure cause shutdown jenkins Merge the failure causes over from old "build-failure-analyzer - Copy.bak.xml" into the new Start Jenkins Remove the dummy failure cause So maybe I have an entry in "build-failure-analyzer - Copy.bak.xml" which is not parseable ? - which also could explain the part of the original exception message that mentions hudson.diagnosis.OldDataMonitor ? Anyway - I am happy again, but I am attaching both files, maybe you can spot if there is data in the old file that does not make sense. build-failure-analyzer - Copy.bak.xml build-failure-analyzer.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner updated an issue Jenkins / JENKINS-59582 build-failure-analyzer fails to load on startup, exception thrown. Change By: Jens Brejner Attachment: build-failure-analyzer - Copy.bak.xml Attachment: build-failure-analyzer.xml 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.20.1569837284000.8599.1569926700262%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Hi Tomas. The issue does not seem to be related, but I will test tomorrow, when I am at work again. If I read that issue correctly the root of that problem is the .net version required by the windows server executable and eventually the restart command. So I will test by launching jenkins from command line - the good old way, then we can see if that changes anything Br Jens 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.20.1569837284000.8050.1569862080107%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Jens Brejner created an issue Jenkins / JENKINS-59582 build-failure-analyzer fails to load on startup, exception thrown. Issue Type: Bug Assignee: Tomas Westling Attachments: build-failure-analyzer.xml, jenkins.err.log Components: build-failure-analyzer-plugin Created: 2019-09-30 09:54 Environment: OS: Windows, Jenkins LTS 2.190.1. Labels: exception Priority: Blocker Reporter: Jens Brejner The plugin fails to load on jenkins startup, and is there for ignored completely. The settings are not visible in Configure Jenkins nor is the plugin listed in Installed Plugins. jenkins.err.log contains the following: SEVERE: Failed Loading plugin Build Failure Analyzer v1.21.0 (build-failure-analyzer) java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:388) at hudson.PluginManager$2$1$1.run(PluginManager.java:545) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1095) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-55244) Shelved projects footprint increased by factor 10
Title: Message Title Jens Brejner commented on JENKINS-55244 Re: Shelved projects footprint increased by factor 10 Pierre Beitz if that is the sometimes corrupted symlinks to lastStable that were problematic, you could simply delete them before archiving... Jenkins should parse the builds on startup and recreate, if the project is unshelved. You probably also call the method to recreate symlinks on unshelve. But do what you find best, you are the developer, I'm just a happy user. 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Jens Brejner edited a comment on JENKINS-55244 Re: Shelved projects footprint increased by factor 10 Hi Pierre.Thank you very much. I guess it can be implemented as simple as continue to tar and untar the project folder, Then on shelving, just zip the tar file, and on unshelve, use unzip, and check if the unzipped content is a .tar file, if yes, call your untar method.That way you will not have to implement support for one more shelve format, and the plugin will continue be backwards compatible. Just remember to delete the .tar files after use :) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55244) Shelved projects footprint increased by factor 10
Title: Message Title Jens Brejner commented on JENKINS-55244 Re: Shelved projects footprint increased by factor 10 Hi Pierre. Thank you very much. I guess it can be implemented as simple as continue to tar and untar the project folder, Then on shelving, just zip the tar file, and on unshelve, use unzip, and check if the unzipped content is a .tar file, if yes, call your untar method. That way you will not have to implement support for one more shelve format, and the plugin will continue be backwards compatible. Just remember to delete the .tar files after use Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55244) Shelved projects footprint increased by factor 10
Title: Message Title Jens Brejner created an issue Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Issue Type: Bug Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2018-12-18 16:16 Environment: Windows Priority: Major Reporter: Jens Brejner Version 2.1 changed the archive format to .tar. Tar files are not compressed, so the size of a .tar archived project is about 10 times an archive produced with earlier version of the plugin. To reproduce: Install shelve-project-plugin version < 2.1 and shelve a project. Take note of the .zip file size Install version 2.1, unshelve the project, then shelve it again. Compare the size of the .tar file to the size of the previous .zip file. Suggest to compress the .tar file into a .tar.gz instead. Add Comment
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Jens Brejner commented on JENKINS-24686 scm-sync-configuration fails if job name contains whitespace Not a solution, but I worked around by disabling the scm-sync repository, then renamed my jobs so spaces where replace with non-whitespace. After that, I reenabled the scm-sync repository 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] [build-publisher-plugin] (JENKINS-27381) Last Success/Failure/Duration shows N/A on published instance
Jens Brejner updated JENKINS-27381 Last Success/Failure/Duration shows N/A on published instance If you send me a snapshot version I will be happy to help testing the fix. Change By: Jens Brejner (12/Mar/15 10:15 AM) Environment: Jenkins1.601.Sendingmasteronubuntu,receivingmasterrunsonWindows.Latestversionoftheplugin .Themastersareindifferenttimezones. 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] [build-publisher-plugin] (JENKINS-27381) Last Success/Failure/Duration shows N/A on published instance
Jens Brejner created JENKINS-27381 Last Success/Failure/Duration shows N/A on published instance Issue Type: Bug Assignee: vjuranek Components: build-publisher-plugin Created: 12/Mar/15 10:13 AM Description: On the receiving master the values for "Last Success","Last Failure","Last Duration" on any views page shows "N/A". Could be related to: JENKINS-17239 JENKINS-18105 Environment: Jenkins 1.601. Sending master on ubuntu, receiving master runs on Windows. Latest version of the plugin Project: Jenkins Priority: Minor Reporter: Jens Brejner 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] [p4-plugin] (JENKINS-25491) Stack trace when attempting to delete P4 enabled job
Jens Brejner created JENKINS-25491 Stack trace when attempting to delete P4 enabled job Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 07/Nov/14 2:35 PM Description: A job which has already run will cause a stack trace when you attempt to delete it. Environment: Windows 7, JDK 8u25, jenkins 1.580.1 p4-plugin 1.0.17 Project: Jenkins Priority: Blocker Reporter: Jens Brejner 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.
