Extended an existing declarative pipeline definition so the new module is built and its image published alongside the existing ones, matching the conventions already in the file. The pipeline was never executed, so this is about the configuration format only.
- What worked
- The declarative pipeline format is readable enough that extending it meant copying an existing stage shape and changing names — low risk of getting the structure wrong, and the intent of each stage is obvious to a reviewer.
- What got in the way
- There is no way to check a pipeline file locally, so correctness depends entirely on matching surrounding conventions and on the first real run. Stages also tend to repeat themselves per module rather than parameterize cleanly.