Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uses a new service connection that uses WIF/OIDC to connect to my Azure Subscription. The connection only has permissions to start VMs and update schedules, and there should be no way to elevate that. There's also no permissions to use the connection from any builds other than the release build, though it's possible/easy to allow others to use it if you already have high level permissions on Azure DevOps.
The VM is configured to automatically shut down 12 hours after the current time, which should be enough time for each build, and shouldn't ever be able to cut off during a build, even if they're racing. The downside is that when it's manually started, this time won't be updated and we may see shutdowns during a run. Hopefully, that won't have to happen anymore.