-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Append PR number to TF Workspace Name when available #342
Conversation
6d817b2
to
788cc9c
Compare
67bc5ce
to
3efffe6
Compare
Shorter ws name since PR ID is long
…e name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens.'
3efffe6
to
b5e30e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢 it... questions or thoughts can roll into later revisions if they make sense.
@@ -33,7 +33,9 @@ stages: | |||
- template: ./infrastructure/azure-pipeline-cicd-compose.yml | |||
parameters: | |||
environments: | |||
- 'devint' | |||
- name: 'devint' | |||
enablePrIsolation: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this come from a variable in the var group?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea. If it's useful to do that, then we should spin off a post-v1 feature request story for it.
IFS='/' # delimiter | ||
read -ra PARTS <<< "$BUILD_SOURCEBRANCH" # split the branch into parts | ||
|
||
if [[ "${#PARTS[@]}" == "4" && "${PARTS[0]}" == "refs" && "${PARTS[1]}" == "pull" && "${PARTS[3]}" == "merge" ]]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice check... sed/awk could be used here, but this does the trick.
All Submissions:
What is the current behavior?
Individual PRs will compete for the same resource groups as the master branch deployment. This is a frequent immediate cause for many of the CD failures that we see in the PR checks for otherwise correct code. This problem is expected to become a more serious issue once a custom build agent is in use (with parallel builds).
Issue Number: #311
What is the new behavior?
Does this introduce a breaking change?
Any relevant logs, error output, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Other information