[JIRA] (JENKINS-35027) Upgraded to V2.5 this morning now error screen on startup
Title: Message Title Oleg Nenashev resolved as Duplicate Closing as a duplicate of JENKINS-36115, which has more info inside Jenkins / JENKINS-35027 Upgraded to V2.5 this morning now error screen on startup Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate 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
[JIRA] (JENKINS-35027) Upgraded to V2.5 this morning now error screen on startup
Title: Message Title Oleg Nenashev commented on JENKINS-35027 Re: Upgraded to V2.5 this morning now error screen on startup wolfs From what I see the component has been already renamed. Moreover, about one year ago I have created the "__unsorted" component, so it is now the first one in the list. Hopefully it helps maintainers of the "a.*" plugins 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-35027) Upgraded to V2.5 this morning now error screen on startup
Title: Message Title wolfs commented on JENKINS-35027 Re: Upgraded to V2.5 this morning now error screen on startup I know why. I created a plugin called all-changes-plugin and we have a JIRA component called all-changes. Now everytime someone creates a JIRA ticket and decides that this should be related to all-changes the component gets assigned and I am assigned to the ticket. What would we need to do to rename the component to all-changes-plugin? 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-35027) Upgraded to V2.5 this morning now error screen on startup
Title: Message Title Oleg Nenashev commented on JENKINS-35027 Re: Upgraded to V2.5 this morning now error screen on startup wolfs You are assigned to the ticket. Not sure why. Regarding the ticket itself, we cannot iterate on it without System logs and the jenkins version at least. Since the ticket is too old && likely it's impossible to get this data, I propose to close it unless Tom West has additional info. 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-35027) Upgraded to V2.5 this morning now error screen on startup
Title: Message Title Suresh Kumar updated an issue Jenkins / JENKINS-35027 Upgraded to V2.5 this morning now error screen on startup Change By: Suresh Kumar Component/s: core Component/s: all-changes-plugin 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.
