-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
Standalone JAR packaging of Jenkinsfile Runner is potentially unstable #350
Labels
bug
Something isn't working
Comments
oleg-nenashev
added a commit
to oleg-nenashev/jenkinsfile-runner
that referenced
this issue
Aug 1, 2020
oleg-nenashev
changed the title
Uber JAR packaging of Jenkinsfile Runner is potentially unstable
Standalone JAR packaging of Jenkinsfile Runner is potentially unstable
Dec 9, 2020
Also there is a glitch in the terminator logic due to missing extensions metadata for modules
|
I tried pulling jenkins from docker hub today and faced this issue when running locally. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR: It works by luck and thanks to the Jenkins extension loading failover logic.
META-INF definitions are not merged correctly, and extension annotations from the core might be overridden by plugins. Custom container description handlers are required to handle META-INF/annotations/hudson.Extension though it might be replaced by META-INF/annotations/hudson.Extension.txt. FTR: https://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-container-descriptor-handlers.html
Sample of an exception which may happen if a new plugin dependency is added:
Dependency order kinda keeps the Jenkins core stable, but at the same time lack of extension cache hits performance significantly in such mode
The text was updated successfully, but these errors were encountered: