-
Notifications
You must be signed in to change notification settings - Fork 298
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
Enhance pre/post
cleanup by bypassing GitHub-hosted runners
#431
Conversation
Yes please... this would shave a few minutes off every single one of our builds... |
Thanks for this PR. A note for 2. Running an ephemeral container on a self-hosted runner, my understanding is that #407 will not fix the case of ephemeral self-hosted runners that already have Azure CLI installed. It might be quite difficult to determine if a job is running on an ephemeral runner. This information is in the runner config, but does not seem to be exposed to the running job. The easiest option would probably be to allow control of this through an action input parameter e.g. |
Let's take the following questions to consideration:
|
Hi @MoChilia , can we get this patched up and merged? We waste a ton of build time on this. I agree with Maskati that another input Then, skipping pre and post steps if |
What's the delay here? This us costing is $$$ and is pure wastage. |
We got fed up of waiting, forked the repo and reference the fix in our workflows:
|
Hi @HowardvanRooijen, @phj-incom , @damianh , we're sorry for the late response. We're reconsidering the design. If you're blocked by this issue, please consider fork the repo and take the PR change for a workaround, like @HowardvanRooijen did. |
Implement the fix in #484. Close this PR now. |
The purpose of
pre/post
cleanup is to ensure no Azure account remains active before and after a job containingazure/login
. This measure prevents incorrect operations on unexpected Azure accounts and protects against the disclosure of Azure accounts.However, certain scenarios are ephemeral for only one job and don't need
pre/post
cleanup. Two main scenarios fall into this category:az
is not pre-installed. We address this scenario by implementing PR Fix #403: Catch the error thrown inpre
andpost
steps #407.With this PR merged, it is assumed that
pre/post
cleanup will only take effect in scenarios where it is truly required.az account clear
) optional for better performance on ephemeral runners #426