[Agent CI] Improve release pipeline stability #3868
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue description:
Recently we faced two issues with the release pipeline:
First issue:
The
Sign Agent Assemblies (3rd Party Assemblies Signing)
step could take up to 40 minutes this could cause cancel of the pipeline job due to a hit of time limitation. Current value fortimeoutInMinutes
is set to 60 minutes.Second issue:
The
Delete CodeSignSummary.md
step could failed due to the following error:##[error]Error: Failed rmRF: EPERM: operation not permitted, unlink 'D:\a\1\s\_layout\win-x64\CodeSignSummary-RandomGUID.md'
The issue itself seems to be intermittent since and related to the environment.
Fix description:
To fix the first issue we can increase
timeoutInMinutes
to make sure that the pipeline job would not be canceled by ADO after 60 minutes. For the second issue, we can setretryCountOnTaskFailure
so ADO will retry theDelete CodeSignSummary.md
step several times before failing the pipeline job.Changelog:
build-jobs.yml
: Increase default value fortimeoutInMinutes
from 60 to 120 minutessigning.yml
: SetretryCountOnTaskFailure
to 4 forDelete CodeSignSummary.md
pipeline step