New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem adding view in 1.532.1 #2
Comments
Nevermind. I just noticed you don't support LTS release. |
Hi, What's you plugin version? Thank you On Mon, Apr 7, 2014 at 2:49 PM, Nux notifications@github.com wrote:
|
Even though it is not depending on the LTS version, I'm willing to make it work on it. |
Strange. On the Jenkins wiki I see version 1.4, but in Update Center I can only download version 1.1. Maybe you just need to change compatibility and build against 1.532? I can test it if you provide a hpi file. |
I've found a link to 1.4 hpi, but when I installed it and added a view then I get the same error:
I have some jobs that have a different "Display Name" set in job configuration. Maybe that is the problem? |
The problem you had about the plugin not showing up in the update center might be fixed by forcing you jenkins to update in the pluginManager -> Advanced tab. In the right bottom of the page there's a button "Check now" that will do that. I don't know how often jenkins updates the list of plugins, but I had to use that button several times plugins that had just been released. Back to the problem, what do you mean by different "Display Name"? |
I found the problem and I'm working on it: |
Hi. Just to let you know - I still had a problem in 1.532.1*, but after upgrading to 1.532.3 it all works fine :-). *) I think problem in 1.532.1 might be a Jenkins problem (as mentioned by Daniel Beck), but if you would like to work on it the Exception was:
|
Fixing compatibility issue. Fixes jenkinsci#2
Hi.
I get below stack trace when I open categorized view no matter what settings I try. Any ideas? What should I look for or what information you would need to figure out :-).
The text was updated successfully, but these errors were encountered: