Skip to content
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

Closed
pietroalbini opened this issue May 25, 2019 · 7 comments
Closed

azure: Figure out data retention in Azure #61165

pietroalbini opened this issue May 25, 2019 · 7 comments
Labels
P-medium Medium priority T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@pietroalbini
Copy link
Member

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.

@pietroalbini pietroalbini added T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. azure-evaluation labels May 25, 2019
@alexcrichton alexcrichton changed the title Figure out data retention in Azure azure: Figure out data retention in Azure May 25, 2019
@calebcartwright
Copy link
Member

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:
image

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.

@pietroalbini pietroalbini added the P-high High priority label Jun 15, 2019
@pietroalbini
Copy link
Member Author

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.

@pietroalbini
Copy link
Member Author

Discussed this with Microsoft, they're going to follow up privately with us on that. Demoting to P-medium.

@pietroalbini pietroalbini added P-medium Medium priority and removed P-high High priority labels Jul 9, 2019
@pietroalbini
Copy link
Member Author

Triage: no update happened on this. There are still 1.5 years to figure out a solution though.

@shepmaster
Copy link
Member

Triage: We'll probably be out of Azure when this becomes an issue.

@shepmaster
Copy link
Member

Although we might need to configure something similar for GHA?

@pietroalbini
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-medium Medium priority T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants