[JIRA] (JENKINS-60668) Pipeline view formatting messed up
Title: Message Title Igor Koyfman created an issue Jenkins / JENKINS-60668 Pipeline view formatting messed up Issue Type: Bug Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2020-01-07 00:15 Priority: Major Reporter: Igor Koyfman Pipeline View formatting has been messed up since Parameterized Trigger Plugin version 2.35.2, so I'm staying on 2.35.1. 2.36 still has the same problem. Basically, it combines two consequent builds and mixes up different jobs so you can't tell which belongs to which build. With 2.35.1 there is a clear demarcation between different builds and you can see the entire pipeline at a glance, but with versions after that the view is unusable. Add Comment
[JIRA] (JENKINS-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman resolved as Fixed The issue was due to locked up tmp files. Jenkins / JENKINS-50501 Jenkins won't load after updating maven plugin Change By: Igor Koyfman Status: Open Resolved Resolution: Fixed 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman updated an issue Jenkins / JENKINS-50501 Jenkins won't load after updating maven plugin Change By: Igor Koyfman Comment: The issue was due to locked up tmp files. 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman commented on JENKINS-50501 Re: Jenkins won't load after updating maven plugin I got the issue fixed after deleting some locked up tmp files. 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman updated an issue Jenkins / JENKINS-50501 Jenkins won't load after updating maven plugin Change By: Igor Koyfman Jenkins works fine with maven plugin 3.1.1 but after updating to 3.1.2 the web page won't load, it stays in the "Please wait while Jenkins is restarting" state. Reverting back to 3.1.1 fixes the problem. 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman updated an issue Jenkins / JENKINS-50501 Jenkins won't load after updating maven plugin Change By: Igor Koyfman Environment: Jenkins ver. 2.107.1 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman created an issue Jenkins / JENKINS-50501 Jenkins won't load after updating maven plugin Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2018-03-30 23:47 Priority: Critical Reporter: Igor Koyfman Jenkins works fine with maven plugin 3.1.1 but after updating to 3.1.2 the web page won't load, it stays in the "Please wait while Jenkins is restarting" state. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] [core] (JENKINS-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Igor Koyfman commented on JENKINS-34498 Re: Jenkins 2.0 "out of the box" plugins failed to install Can I somehow get those plugins now anyway? Is there a list somewhere? 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-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Igor Koyfman commented on JENKINS-34498 Re: Jenkins 2.0 "out of the box" plugins failed to install I'm changing it to major because it basically invalidates the 2.0 experience. Without those plugins Jenkins is just the same as the old version. 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-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Igor Koyfman updated an issue Jenkins / JENKINS-34498 Jenkins 2.0 "out of the box" plugins failed to install Change By: Igor Koyfman Priority: Minor Major 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-34498) Jenkins 2.0 "out of the box" plugins failed to install
Title: Message Title Igor Koyfman created an issue Jenkins / JENKINS-34498 Jenkins 2.0 "out of the box" plugins failed to install Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/28 7:03 PM Priority: Minor Reporter: Igor Koyfman This is kind of ridiculous, but I think it's still a bug and I do need help. So I updated to Jenkins 1.656 to 2.0, and after the main war file got installed and restarted there was a nice button, I don't remember what it said, that in effect triggered installation of the basic package of plugins, or whatever you call it, the "out of the box" stuff. But due to high demand on the website most of them failed to install, and there seems to be no way to try again. How do I get that button back, or, short of that, just a direct link or script to get all those plugins at once? I have no idea what they were because I tried rolling back and reinstalling but the button is still gone. Add Comment
[JIRA] [core] (JENKINS-28124) userContent is corrupt in 1.610
Title: Message Title Igor Koyfman commented on JENKINS-28124 Re: userContent is corrupt in 1.610 Looks like it's fixed in 1.612. I haven't tried 1.611. The gets transferred last referred to the fact that the last file in the dir was the one corrupted. I'm just guessing it must've been transferred from master after all others. 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-28124) userContent is corrupt in 1.610
Igor Koyfman created JENKINS-28124 userContent is corrupt in 1.610 Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Apr/15 3:46 AM Description: After updating to 1.610 a part of userContent, which in our case is less than 1 MB or python scripts, is full of bad characters. Everything works again after reverting to 1.607. It's an identical corruption in all jobs on all nodes; I suspect it's whatever gets transferred last. Project: Jenkins Priority: Major Reporter: Igor Koyfman 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] [core] (JENKINS-27530) Dead node
Igor Koyfman created JENKINS-27530 Dead node Issue Type: Bug Assignee: Unassigned Components: core Created: 20/Mar/15 6:29 PM Description: Submitting log per instructions on the dead node page. Unexpected executor death java.lang.IllegalStateException: /hfs/d1/local/jenkins/jobs/test_other/builds/96 already existed; will not overwite with test_other #96 at hudson.model.RunMap.put(RunMap.java:187) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1006) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor.run(Executor.java:213) Environment: The dead node is Win7 running cygwin sshd, the server is RHEL5. Jenkins version 1.605. Project: Jenkins Priority: Critical Reporter: Igor Koyfman 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] [matrix-auth-plugin] (JENKINS-26909) Project-based security inheritance doesn't work
Igor Koyfman created JENKINS-26909 Project-based security inheritance doesnt work Issue Type: Bug Assignee: Jesse Glick Components: matrix-auth-plugin, security Created: 11/Feb/15 7:30 PM Description: Somewhat similar to JENKINS-10601, I can't get the job to properly inherit global permissions. I want authenticated users to not be able to build any jobs except for those that start the pipeline. So in my global permissions authenticated users don't have the build permission, and then I add it for some certain jobs. That does not work - every authenticated user can still build every job. I don't consider "Block inheritance of global authorization matrix" checkbox an appropriate fix for this issue. Project: Jenkins Priority: Major Reporter: Igor Koyfman 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] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Igor Koyfman commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden Tom, I see the buttons now. Thank you for the 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman created JENKINS-26312 No save button on the job configuration page Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Jan/15 7:57 PM Description: In 1.596 there is no save button on the job configuration page. Cannot modify any jobs. Project: Jenkins Priority: Blocker Reporter: Igor Koyfman 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (06/Jan/15 8:01 PM) Description: In1.596thereisnosavebuttononthejobconfigurationpage.Cannotmodifyanyjobs. Revertingto1.594gotthebuttonback. 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (07/Jan/15 1:49 AM) Priority: Blocker Major 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] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Igor Koyfman commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden This also happens on other pages with buttons at the bottom, e.g. the system configuration page, the plugin installation page, etc. The zoom in/zoom out workaround works for all. The CSS workaround with the Simple Theme Plugin mentioned above didn't work. 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I uninstalled the Simple Theme Plugin, and I'm using Chrome. I don't have any jobs that fit on one screen. Also, I checked in IE and there is no Save or Apply button there either. I don't have Firefox. 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I zoomed out the browser until it got so small the job did fit on one screen, and the buttons did show up then. So I guess that's a workaround. 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman commented on JENKINS-26312 No save button on the job configuration page I zoomed out the screen until it got so small the job did fit on one screen, and the buttons did show up then. 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman edited a comment on JENKINS-26312 No save button on the job configuration page I zoomed out the browser until it got so small the job did fit on one screen, and the buttons did show up then. So I guess that's a workaround. P.S. Even better, if I scroll to the bottom of the page and zoom in and then zoom out, then the buttons show up even if the scroll bars are still there. 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman updated JENKINS-26312 No save button on the job configuration page Change By: Igor Koyfman (07/Jan/15 1:33 AM) Attachment: JenkinsNoButton.png 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] [core] (JENKINS-26312) No save button on the job configuration page
Igor Koyfman commented on JENKINS-26312 No save button on the job configuration page I uninstalled the Simple Theme Plugin, and I'm using Chrome. I don't have any jobs that fit on one screen. 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] [core] (JENKINS-24451) Dashboard is getting really ugly and hard to read
Igor Koyfman created JENKINS-24451 Dashboard is getting really ugly and hard to read Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, gui Created: 26/Aug/14 9:25 PM Description: Recent UI changes created way too much white space in the GUI. The Views tabs that used to fit on one screen now wrap around, and so do the current tasks in the Build Executor Status - the Build Name that used to fit on one line is now broken into three lines! Please revert to the old UI, it worked much better. Project: Jenkins Priority: Major Reporter: Igor Koyfman 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] [core] (JENKINS-23392) Jenkins less responsive after 1.567 update
Igor Koyfman resolved JENKINS-23392 as Not A Defect Jenkins less responsive after 1.567 update Looks like it probably isn't this version of Jenkins. I downgraded and still see the issue, so it's more likely the server is being slow. Change By: Igor Koyfman (12/Jun/14 1:39 PM) Status: Open Resolved Resolution: NotADefect 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] [core] (JENKINS-23367) Require user to enter reason for manual build abortion
Igor Koyfman commented on JENKINS-23367 Require user to enter reason for manual build abortion Well, I don't want to enter the reason for aborting the build, especially if it's a couple dozen of them all running at the same time. If this feature is added it should be optional. The regular red x should just abort the build. If you want to give a reason it should be a different button, perhaps inside the build's page. 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] [core] (JENKINS-23392) Jenkins less responsive after 1.567 update
Igor Koyfman created JENKINS-23392 Jenkins less responsive after 1.567 update Issue Type: Bug Assignee: Unassigned Components: core Created: 10/Jun/14 8:42 PM Description: After 1.567 update Jenkins seems to take much longer to render its pages. Clicking on a link used to show the page almost immediately with previous versions up to and including 1.566, and now it takes a few seconds before the pages show up. Project: Jenkins Priority: Major Reporter: Igor Koyfman 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] [core] (JENKINS-22617) Can't delete crash report
Igor Koyfman commented on JENKINS-22617 Cant delete crash report There is no message about broken proxy. I think at one point I could actually see the crash report, but now that link doesn't work either because the crash report is probably not there anymore. The delete button never worked. I'm running 1.559 because 1.561 was in fact crashing. 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] [core] (JENKINS-22617) Can't delete crash report
Igor Koyfman commented on JENKINS-22617 Cant delete crash report I'm not the original submitter, but I have the same problem and I'm not running the proxy. The script output on my system is this: hudson.PluginManager$PluginCycleDependenciesMonitor true hudson.PluginManager$PluginUpdateMonitor true hudsonHomeIsFull true hudson.diagnosis.NullIdDescriptorMonitor true OldData false hudson.diagnosis.ReverseProxySetupMonitor true hudson.diagnosis.TooManyJobsButNoView true hudson.model.UpdateCenter$CoreUpdateMonitor true hudson.node_monitors.MonitorMarkedNodeOffline true hudson.triggers.SCMTrigger$AdministrativeMonitorImpl true jenkins.diagnosis.HsErrPidList true jenkins.diagnostics.SecurityIsOffMonitor true jenkins.diagnostics.ooom.OutOfOrderBuildMonitor true jenkins.security.RekeySecretAdminMonitor true 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] [core] (JENKINS-22617) Can't delete crash report
Igor Koyfman commented on JENKINS-22617 Cant delete crash report Same problem here. Can't get rid of the message "This Jenkins appears to have crashed. Please check the logs." even though the crash happened several weeks ago and I've reverted to an older non-crashing version of Jenkins since then. There is nothing matching the pattern hs_err* in the /tmp or /jenkins directories. I don't even care if this is fixed, just tell me what triggers this message so I can clean it up. 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] [core] (JENKINS-22617) Can't delete crash report
Igor Koyfman updated JENKINS-22617 Cant delete crash report Change By: Igor Koyfman (22/May/14 9:20 PM) Component/s: core 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] [core] (JENKINS-22485) Cannot save job configuration after deleting a parameter
Igor Koyfman created JENKINS-22485 Cannot save job configuration after deleting a parameter Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, parameters Created: 03/Apr/14 2:54 PM Description: After deleting a job parameter Save and Apply buttons don't work. Jenkins 1.555 Project: Jenkins Priority: Major Reporter: Igor Koyfman 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.
