-
Notifications
You must be signed in to change notification settings - Fork 414
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
2.0.1 Release #193
Comments
I'm not sure where #188 is being tracked any more, so I'm not sure where to post this comment. Maybe it needs to be reopened. Anyway, I think the |
I believe that @samrocketman moved #188 into #191 |
Perhaps closing #188 was premature on my part? It can be re-opened. I remember someone where I work describing the issue. I'll ask them for more details. |
I have not had a chance to try reproducing #190. I think #188 is caused by uploading a job config via the REST API. One of the people reporting it maintains their configs externally and uploads them via a Gradle plugin. In that scenario, the config is not migrated from 1.8 to 2.0 and you get that error, which is actually misleading. Restarting Jenkins fixed the issue for him because the configs were then migrated. I kind of feel like this is an issue that users will have to fix themselves ... if we somehow automatically migrate those configs, then they'll just keep maintaining the old format externally, and we'll be stuck with the config migration always having to take place. Maybe we can log an error when uploading an old format config or something. @samrocketman I'd be interested to hear whether this is the same use case that your coworker is experiencing, or whether there are some cases where configs are somehow not being migrated. |
FYI, I was still having issues after installing 2.0.1. I was no longer getting the NullPointerException all over the place, but I started getting the I fixed the issue by uninstalling the plugin, deleting the |
I've re-opened #188 which describes a similar stack trace. |
@shaneargo, do you have a backup of a config.xml from the job that you could not save? If you do, can you post it here or in #188 please. The job configs were supposed to be automatically migrated from the 1.8 format, but it's possible that it failed to do that, resulting in those errors. If you don't have a backup of the config, could you look for "Starting Settings Migration Process" in your log files and post any errors that follow it. |
@shaneargo : I just tried your workaround of Here's the stacktrace from jenkins.log:
|
Moving any discussion about the |
Critical bug-fix release for #191 via #190
TODO:
maintainer communication
.git checkout origin/master -b prepare_release
CHANGELOG.md
.prepare_release
branch tomaster
branch. Merge it.master
.Wait ~8 hours....
The text was updated successfully, but these errors were encountered: