Build retention should not fail the build in Staging pipeline
See original GitHub issueStaging pipeline -> https://dev.azure.com/dnceng/internal/_build/results?buildId=2160139&view=logs&j=6606dbf2-e954-58ee-2b33-bc1713636658&t=55d2db69-7837-5679-149b-695c54eef813
Motivation:
One of our goals is to ensure that the release team can operate the infrastructure efficiently and with confidence. To achieve this, we want to ensure that errors in build Retention should not block the build.
Work items:
- Utilize
continueOnError: true
in the retain-build steps. - Run test staging pipeline.
Issue Analytics
- State:
- Created 5 months ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Set retention policies for builds, releases, and tests
Set run retention policies ... In most cases, you don't need to retain completed runs longer than a certain number of days. Using...
Read more >Is it possible to set a minimum number of builds to retain ...
I'd have preferred an option which would not require to use a release pipeline but I guess there's no better way. The documentation...
Read more >Successful builds no longer retained so BuildNumber is ...
This means that after the pipeline retention period has passed the build is deleted automatically. The build revision property resets to one ...
Read more >Control Build Retention
Description: Specifies retention parameters for build info Since: 5.2.1 Note: A promoted Build Info cannot be deleted using this API.
Read more >Dynamically Retain Azure DevOps Pipelines - John Folberth
Usually, we only need to retain pipelines that deployed to a production stage. This means we will need to have this process conditionally...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Test -> https://dev.azure.com/dnceng/internal/_build/results?buildId=2171801&view=logs&s=b576a58d-8d3b-5d68-c48d-6d3ec0e2b155&j=c62e860b-6817-58cb-b096-cb547a9441f4
@epananth , do we know how often this problem occurred? Do we need to follow up of those errors? Update documentation, etc