Skip to content
Open core software, built in Singapore Established 2018  /  Five utilities
Jering
Talk to us

Advanced

DevOps.AzurePipelines Jering documentation Open source Pipeline templates
Documentation menu

These notes are for teams that need to change the templates without breaking every repository that consumes them.

Template composition

Treat a template like a dependency. Give it a narrow job, document its inputs and avoid reaching into the consumer's repository for hidden state. A stage that can be understood on its own is easier to reuse.

Versioning the templates

Pin the template repository to a branch or tag. If several projects consume the templates, a tag gives them a deliberate upgrade point instead of a moving target.

Failures

Make failures loud and specific. A test failure should name the project and the agent. A packaging failure should leave the generated artifacts in place long enough to inspect them.

Related topics

Reference shelf