-
Notifications
You must be signed in to change notification settings - Fork 306
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
Downloading action repository to self-hosted runner takes 2.5 minutes #103
Comments
When checking the downloaded files at Can you consider compiling in the dependencies that is needed so that the |
Btw, my solution was to just use az cli to login instead of the login action. |
This issue is marked need-to-triage for generating issues report. |
This issue is idle because it has been open for 14 days with no activity. |
Yeah same issue, its 3 mins just to download the action every single run. |
Do you have a quick code example of how you handled this? |
Yep. $Credential = ConvertFrom-Json($env:SERVICE_PRINCIPAL) |
Thank you very much for this. I will have to try this out using a github secret. |
This issue is idle because it has been open for 14 days with no activity. |
I also faced this same download taking time for almost 2 mins every time. jobs: build-and-deploy: |
This issue is idle because it has been open for 14 days with no activity. |
@BALAGA-GAYATRI This problem unfortunately still exists. |
Every time I run my workflow on my self-hosted runner it has to redownload the whole action repository which takes 2.5 minutes. This is the step in my workflow log: Download action repository 'azure/login@v1'.
I am not sure if this is a more general issue in GitHub Actions, where the action repository is redownloaded every time even if it is the exact same version being used each run. But since the other actions I use are downloaded in a matter of seconds and this action takes 2.5 minutes I opened the issue here.
Also I have looked into using the cache action, but can't figure out how to use it for caching "external" actions, or if that is possible at all, that's also why I have opened this issue.
The text was updated successfully, but these errors were encountered: