Generates a compatibility matrix for plugins against Jenkins core.
The PCT CLI requires passing a WAR file containing plugins (generated from jenkinsci/bom
, for example) as input;
the versions of the plugins are inferred from the WAR file contents.
java -jar target/plugins-compat-tester-cli.jar \
--war "$(pwd)/megawar.war" \
--working-dir "$(pwd)/pct-work"
To test a subset of plugins in the WAR, use --include-plugins
:
java -jar target/plugins-compat-tester-cli.jar \
--war "$(pwd)/megawar.war" \
--include-plugins ssh-slaves,credentials \
--working-dir "$(pwd)/pct-work"
You can run the CLI with the --help
argument to get a full list of supported options.
PCT simply invokes Maven, which relies on the JAVA_HOME
environment variable.
If you want to use a custom Java version, set JAVA_HOME
appropriately before running PCT.
- Devoxx '11 BOF Presentation about Plugin Compat Tester is available here. This presentation is partially obsolete (GAE feature was removed in recent versions)