Pipeline Catalog Import via CLI fails all imports on one catalog failure

Issue

Since I upgraded my CloudBees CI to release 2.462.2.2, if one Pipeline Template Catalog import fails, then the CLI command is interrupted and the catalogs won’t appear.

Environment

Resolution

This issue will be fixed in a future CloudBees CI release, and this article will be updated with the specific version number with the fix.

Workaround

This is caused by a catalog failure during the CLI import command, for example, because of a syntax error. Therefore, you have to fix the failed catalog in order to import correctly all your Pipeline Template Catalogs using the CLI import command.

Tested product/plugin versions

CloudBees CI on modern cloud platforms - managed controller - 2.462.2.2
CloudBees CI on traditional platforms - client controller - 2.462.2.2

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.