-
Notifications
You must be signed in to change notification settings - Fork 841
chore: update & document release process #964
Conversation
mydiemho
commented
May 18, 2020
•
edited
Loading
edited
4958d39
to
f007c86
Compare
125f7d2
to
a2689e2
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.
Looks good overall - Let me know if you need help testing before we pull the trigger on official release.
@@ -0,0 +1,33 @@ | |||
name: "GitHub & Web Release [$(SourceBranchName)] - $(Date:yyyyMMdd)$(Rev:.r)" |
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.
Was the old process not working? Looks like a full rewrite on the pipelines?
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.
a lot of the old process was manual. A few of AzDO task has been updated to support the functionality we need so I removed the manual pieces.
destination: azureBlob | ||
storage: $(DEV_STORAGE_ACCOUNT) | ||
containerName: '$web' | ||
# condition: eq(variables['Build.SourceBranch'], 'refs/heads/develop') |
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 line be commented out?
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 catch, need to remove. thought process is that preview would only go to Dev, but release from both master
would update both Dev & Prod web instance
aba8432
to
dba6dfe
Compare
Kudos, SonarCloud Quality Gate passed!
|