Unverified Commit afe8fee1 authored by Michele Degges's avatar Michele Degges Committed by GitHub
Browse files

[CI-only] Use pattern matching for release_branches

### Description
Pattern matching was [recently added](https://github.com/hashicorp/crt-orchestrator/pull/51) so that teams no longer have to explicitly list every branch that should trigger the CRT pipeline. This simplifies release preparation- anytime a new release branch is created, it will produce releasable artifacts and exercise the full pipeline.

### Testing & Reproduction steps
This has been tested in multiple projects since being rolled out. There are no nomad-specific tests that need to be done.

### Links
PR where this functionality was added: https://github.com/hashicorp/crt-orchestrator/pull/51

### PR Checklist

* [ ] updated test coverage
* [ ] external facing docs updated
* [X] not a security concern
parent b07f5678
Showing with 1 addition and 4 deletions
+1 -4
......@@ -13,10 +13,7 @@ project "nomad" {
release_branches = [
"main",
"release/1.0.x",
"release/1.1.x",
"release/1.2.x",
"release/1.3.x",
"release/**",
]
}
}
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment