Additional information for when runs are retained.#14362
Additional information for when runs are retained.#14362arkoppan wants to merge 5 commits intoMicrosoftDocs:mainfrom
Conversation
Clarified retention policy for Azure Repos regarding the latest runs retained for default and protected branches (only successful or partially succeeded runs are retained).
Clarified the retention policy for pipeline runs, specifying conditions under which runs are retained based on deployment success.
Only successful or partially succeeded runs are retained. Clarified the calculation for retention days based on run completion time.
|
@arkoppan : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
Updates Azure Pipelines retention policy documentation to clarify which runs are kept under “recent runs” retention and how retention days are calculated relative to run completion time.
Changes:
- Adds clarification that only successful or partially succeeded runs are considered for “latest runs” retention (Azure Repos case).
- Adds explanation/example that retention days are calculated from run completion time, including an illustrative screenshot.
- Minor formatting adjustments in the retention policy instructions section.
| Only latest successful or partially succeeded pipeline runs are retained. If deployment to only specific environment or stage succeeded, the run is not retained. | ||
|
|
There was a problem hiding this comment.
This new sentence is not indented under the “- Azure Repos: …” list item, so it will render as a separate paragraph (and can interrupt the list). Indent it to be part of the Azure Repos bullet, and consider separating it into its own indented paragraph for readability.
| Only latest successful or partially succeeded pipeline runs are retained. If deployment to only specific environment or stage succeeded, the run is not retained. | |
| Only latest successful or partially succeeded pipeline runs are retained. If deployment to only specific environment or stage succeeded, the run is not retained. |
| | Run 1 | main | Not retained | Neither latest 3 for main, nor for pipeline | | ||
|
|
||
|
|
||
| Further, the number of days to retain is calculated from when the run is completed. For example, there are two runs on a master branch on Jan 19th. The run that completed later is retained. |
There was a problem hiding this comment.
This example introduces “master branch”, which is inconsistent with the earlier main terminology and can be confusing. Consider using “default branch” (or main) consistently, and clarify the outcome in terms of the computed deletion time/date (rather than saying the run “is retained”, which can be read as a different retention rule).
| Further, the number of days to retain is calculated from when the run is completed. For example, there are two runs on a master branch on Jan 19th. The run that completed later is retained. | |
| Further, the number of days to retain is calculated from when the run is completed. For example, suppose there are two runs on the default branch (for example, `main`) on Jan 19th. The run that completed later will have a later deletion time because its retention period is counted from its completion time. |
|
|
||
|
|
||
|
|
||
|
|
There was a problem hiding this comment.
There are multiple consecutive blank lines after the image. Please remove the extra empty lines to keep the Markdown tidy and avoid unexpected spacing in rendering.
Co-authored-by: Regan Downer <v-rdowner@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Only successful or partially succeeded runs are retained.
Clarified the calculation for retention days based on run completion time.