-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
False
-
As we implemented "Lock Plugin Versions in Upstream openshift/jenkins" in JKNS-269, it seems that the image build still unpacks the downloaded plugins and check other dependencies.
This step could be skipped as we are now enforcing this check in `make plugins-list` and in the relevant ci test.
A possible solution has been explained here,
https://github.com/openshift/jenkins/pull/1384#issuecomment-1030257978
That could consists in adding a parameter to the `doDownload` function https://github.com/openshift/jenkins/blob/master/2/contrib/jenkins/install-plugins.sh#L194
to allow transitive dependencies check or not; and then change the openshift ci job `image` to pass this argument, so while building in CI, we just donwload the plugins but we do check their dependencies.
- impacts account
-
JKNS-269 Lock Plugin Versions in Upstream openshift/jenkins
- Closed
- links to