-
Notifications
You must be signed in to change notification settings - Fork 326
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
Gradle project fails to run with Jenkins v2.277.1 #109
Comments
Just ran into this yesterday. I'm not super familiar with java systems (including gradle) but I did my best to dig into it regardless. The chain of events:
Obviously this isn't much of a fix given the amount of deletions involved. But it points to the fact that However I'm not really able to reconcile that conclusion with the fact that empirically I've got a jenkins instance running on version 2.283 w/ As before, take this all with a grain of salt. My familiarity with all these systems is very limited. |
Cool, thanks for the additional investigation. I'm using a forked version of this repo. Performing the first mitigation step fixed the project compilation for me.
After making this change, I verified that the xml files are still being generated as expected. I also confirmed that providing invalid job dsl breaks compilation. |
Instead of removing job-dsl-core i've exclude xstream
|
Hi, When I change to Jenkins version 2.375.3, it's not work. |
The gradle project was running just fine when defining
jenkinsVersion=2.263.4
in thegradle.properties
file. When bumping the version tojenkinsVersion=2.277.1
the project fails to run and the following error is logged to the console.It seems to be related to
XStream
. The 2.277.1 Jenkins release notes explicitly mention that breaking XStream changes are included in this release.The text was updated successfully, but these errors were encountered: