kyounger / casc-plugin-dependency-calculation Goto Github PK

In some cases, it would be useful to be able to supply multiple source files and have the plugin catalog created for the cumulative list of plugins found. e.g.

• plugins-core.yaml (to be installed on all controllers)
• plugins-alpha.yaml (to be installed on controller alpha only)
• plugins-beta.yaml (to be installed on controller beta only)

Downloading the war file is a lot of overhead. Let's have a look to see if it is really necessary.

The latest version of PIMT includes a PR that greatly simplifies the parsing of its output. Should update to use this instead:

jenkinsci/plugin-installation-manager-tool#448

A customer has custom comment headers in both their plugin catalog as well as the plugins files. It would be nice to keep those headers in place in the output. Potential problem: The plugin catalog is not an input.

I would like to be able to automatically find the minimal number of plugins necessary to fulfill my required set of plugins. This would mean:

• bootstrap plugins are removed automatically
• dependencies of CAP plugins are removed automatically

there is a functional difference in behavior between the two commands:

1. cascgen plugins myenv/raw-bundles/something
2. cd myenv; cascgen plugins

Wherein number 2 correctly updates the plugins yaml and shows actual errors. Number 1 merely copies it to my effective-bundle. Both generate the plugin catalog. Behavior seems inconsistent.

java is no longer needed for this tool so we should change the base image.

I am suing this project for the EKS blueprints until this capability is embraced by the product

The following review has been provided by @kellie-freeman (CloudBees' Center Of Excellent) of the outputs from plugins.yaml and catalog.yaml

After upgrading to 2.303.3.3 the following plugins were added to the CasC bundle:

pipeline-stage-tags-metadata -> 1.9.3
pipeline-model-definition -> 1.9.3
plugin-util-api -> 2.5.1
pipeline-model-extensions -> 1.9.3
pipeline-model-api -> 1.9.3

However these were the latest versions instead of the CAP versions for 2.303.3.3

I think I found the bug in the script as its not considering the CAP plugin. It requires update in "jenkins-update-center" to use like "https://jenkins-updates.cloudbees.com/update-center/envelope-core-mm/update-center.json?id=cap-cje-mm&version=$CI_VERSION" based on this link https://support.cloudbees.com/hc/en-us/articles/230655088-A-plugin-release-is-not-available-from-Update-Center

And disabled usage of environment variable JENKINS_UC_HASH_FUNCTION & CACHE_DIR.

With those change, I was able to generate the plugins.yaml and plugin-catalog.yaml for 2.303.3.3 and managed controller was able to start successfully.

For further details, see support ticket number: 210888