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

Investigate flighting new virtual environments images in our hosted agent pool #3611

Open
benbp opened this issue Jul 11, 2022 · 0 comments
Open
Assignees
Labels
Central-EngSys This issue is owned by the Engineering System team.

Comments

@benbp
Copy link
Member

benbp commented Jul 11, 2022

Our devops agent pool is managed by another team, part of which includes automatic VM version upgrades from the VM images specified at https://github.com/actions/virtual-environments/. Recently we had an issue where the latest VM image included a git cli version upgrade to 2.37.0 which broke our usage of sparse checkout (switching to cone mode by default. See #3606 for more details).

Ideally, we would have been able to catch this issue if we were able to preview new VM image updates coming to our agents several days in advance, before they roll out to the entire VM agent pool. I'm not sure yet what a solution here would look like, whether it's a feature we can ask for from the agent pool team, or whether we would need to build the VM images ourselves and attempt to run a sampling of pipelines on a separate hosted pool.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 11, 2022
@kurtzeborn kurtzeborn added Central-EngSys This issue is owned by the Engineering System team. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Oct 31, 2022
@kurtzeborn kurtzeborn moved this to 🤔Triage in Azure SDK EngSys 🚢🎉 Oct 31, 2022
@kurtzeborn kurtzeborn moved this from 🤔Triage to 📋Backlog in Azure SDK EngSys 🚢🎉 Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants