-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azure: Figure out data retention in Azure #61165
Comments
This may have changed, but the last time I'd checked into it, the retention for YAML builds was still a bit limited in terms of configurability Some relevant documentation:
Others have definitely encountered scenarios when they need to retain a pipeline run indefinitely though. On any completed run (build or release pipeline) there is an option to maintain that specific run indefinitely that can be done manually: Folks have also added extensions that allow for adding a step to a pipeline to automatically retain it, such as https://marketplace.visualstudio.com/items?itemName=mmajcica.retain-release. I'm not sure if any of those existing extensions work for builds (I've only used them for release pipelines), but even if they don't, I suspect something very similar could be done for build pipelines. |
An update, I managed to extend the retention on rustc to 2 years, but we'll discuss this in more depth with Microsoft people in the following days. |
Discussed this with Microsoft, they're going to follow up privately with us on that. Demoting to P-medium. |
Triage: no update happened on this. There are still 1.5 years to figure out a solution though. |
Triage: We'll probably be out of Azure when this becomes an issue. |
Although we might need to configure something similar for GHA? |
We talked about this in the 2020-09-02 infra team meeting, and decided the effort needed to push for this or implement a backup ourselves is not worth it compared to the benefits we'd get from indefinite retention. |
I saw around the docs and the UI that Azure Pipelines has configurable data retention for build logs. We should configure it to store them indefinitely.
The text was updated successfully, but these errors were encountered: