fix: remove redundant conditon for job in release pipeline#16355
fix: remove redundant conditon for job in release pipeline#16355tadelesh merged 4 commits intoAzure:mainfrom
Conversation
tadelesh
commented
Dec 1, 2021
- The purpose of this PR is explained in this or a referenced issue.
- The PR does not update generated files.
- These files are managed by the codegen framework at Azure/autorest.go.
- Tests are included and/or updated for code changes.
- Updates to CHANGELOG.md are included.
- MIT license headers are included in each file.
seankane-msft
left a comment
There was a problem hiding this comment.
Can you verify this works by releasing aztemplate from this branch before merging?
| jobs: | ||
| - deployment: TagRepository | ||
| displayName: "Create release tag" | ||
| condition: and(succeeded(), eq(variables['NeedToRelease'], 'true'), ne(variables['Skip.TagRepository'], 'true')) |
There was a problem hiding this comment.
We only want to remove the "NeedToRelease" part of this condition.
There was a problem hiding this comment.
Skip.TagRepository has already been checked with previous stage CheckRelease which is the dependency of this Release stage. So I removed it.
There was a problem hiding this comment.
Maybe I'm missing it but I don't see where Skip.TagRepository is checked. Can you point me to the place we check it?
There was a problem hiding this comment.
Sorry. I've mixed the two conditions (Skip.Release, Skip.TagRepository) up 😟. I've fixed it.
Release: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1224938&view=results |
The Release pipeline failed on the |
|
That failure is because it was ran from @tadelesh's fork and test pipeline and not our official template pipeline. @tadelesh can you use our |
Thanks for your suggestion which also help me to know another way to test pipeline change under PR. Release result is here. Some validation failed for the |
@weshaggard is the failure on the Release result because it was released from a branch and not from the |
|
Yes the failure is because we cannot create a pull request against a PR merge that is expected. @tadelesh once you handle my other feedback about the |
|
@tadelesh while in here can you also address the warning I saw in the logs https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1227441&view=logs&j=f4752989-c568-5678-80f2-0a67848bfa4d. You need to declare the machine pool and image in the CheckRelease stage similar to the other release stage otherwise it uses a default image. |
Fixed. Test log is here. |
* fix: remove redundant conditon for job in release pipeline * build: release aztemplate 0.1.0 to test release pipeline * fix: revert condition of 'Skip.TagRepository' * fix: add pool to 'check release' job to avoid lagging default image