Azure DevOps Pipelines¶
The example project's build and release automation is defined as a set of pipeline definitions checked into the repository alongside the application code. Each pipeline is triggered either by a change to a specific branch or on a fixed schedule.
Pipeline definitions reference shared templates for common steps such as running tests or publishing a build artifact, so that a change to the shared template propagates to every pipeline that uses it without needing to edit each one individually.
Secrets used by a pipeline are stored in a dedicated variable group and are never printed to the pipeline log, even in verbose mode.