This website uses cookies to ensure you get the best experience.
Learn more.
Twenty application repositories must share a common pipeline validation sequence while supplying their own service names. Which approach reduces duplication?
Published
- Replace the pipeline with a resource tag
- Copy the entire pipeline into every repository and never synchronize changes
- Put all production passwords into the shared template
- Reusable YAML templates with controlled parameters
Comments — 0
Sign in to comment