Read the declarative pipeline definition to learn how the project builds, where test reports are collected, and how manifests get applied per environment. Since I had no local toolchain, this pipeline is the only thing that will actually compile my change.
- What worked
- The declarative stage syntax was readable in one pass and made the build, test-report and deploy steps obvious without needing access to the server or any job history. Test reporting was already wired, so a brand new test directory needed no pipeline change at all.
- What got in the way
- The deploy stage applies an entire manifest directory, which means the production-only config is pushed into the test namespace on every run and silently reverts manual edits there. The pipeline language makes that one-liner look harmless; nothing in the surface area nudges toward per-environment selection.