[JIRA] (JENKINS-60799) credentials-plugin:2.3.1 breaks Jenkins Docker image

[mirzmaster@gmail.com (JIRA)]

Sohail Mirza created an issue

Jenkins / JENKINS-60799 credentials-plugin:2.3.1 breaks Jenkins Docker image Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2020-01-16 16:54 Environment: Jenkins LTS Docker image (2.214) Labels: dependencies Priority: Critical Reporter: Sohail Mirza Between credentials release 2.3.0 and 2.3.1, a dependency on configuration-as-code v1.35 was introduced.  configuration-as-code:1.35 isn't included in the Jenkins LTS Docker image, and so this breaks deployments that are not explicitly specifying configuration-as-code:1.35 be installed.  The version included with Jenkins LTS is 1.32. This is mainly an issue with Docker deployments since the plugins folder may not be on a persistent volume. In general it doesn't seem like a good practice to update dependencies in a patch release. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-60799 credentials-plugin:2.3.1 breaks Jenkins Docker image

Change By: Daniel Beck Priority: Critical Major

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-60799

Re: credentials-plugin:2.3.1 breaks Jenkins Docker image

The version included with Jenkins LTS is 1.32.

It is unclear to me where that version number is coming from. Could you clarify? (Tentatively suspecting a bug in install-plugins.sh or however that works for our Docker images.)

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-60799

Re: credentials-plugin:2.3.1 breaks Jenkins Docker image

(Tentatively suspecting a bug in install-plugins.sh or however that works for our Docker images.) This 4 years old comment, if still true, would explain the behavior you're seeing: https://github.com/jenkinsci/docker/issues/327#issuecomment-239423019 I think the problem comes from the fact the script ignores optional dependencies. If a plugin has an optional dependency which is required dependency for another plugin, the downloaded plugin can be too old to fulfill the optional dependency of the former plugin. This prevents Jenkins to start the plugin with the optional dependency. This would be a bug in the scripts for the Docker image, not in Credentials Plugin.

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck closed an issue as Not A Defect

Assuming the previous comment identified the root cause, which has little to do with this plugin.

Jenkins / JENKINS-60799

credentials-plugin:2.3.1 breaks Jenkins Docker image

Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect

Add Comment