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

Refactor #162

Merged

Conversation

int128
Copy link
Member

@int128 int128 commented Oct 25, 2023

Refactoring for #160.

Changes

  • Extract the installation script for both Dockerfile and Dockerfile.ubuntu20
  • Move the test of @actions/tool-cache into e2e-test

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@github-actions
Copy link

⚠️ If you need to release this change, create a next release after merge.

@int128 int128 marked this pull request as ready for review October 26, 2023 00:03
@int128 int128 requested a review from a team as a code owner October 26, 2023 00:03
@int128 int128 requested review from ShotaroMatsuya and removed request for a team and ShotaroMatsuya October 26, 2023 00:03
@int128 int128 merged commit 5949767 into faster-more-reliable-setup-node Oct 26, 2023
@int128 int128 deleted the int128/faster-more-reliable-setup-node branch October 26, 2023 00:03
int128 added a commit that referenced this pull request Oct 30, 2023
* Make setup-node faster and more reliable

We have occasionally seen that setup-node actions failing due to intermittent connection failures between us and nodejs.org.

To alleviate the issue, we could cache our "most-widely-used" Node.js version inside the container image, enabling setup-node to skip access to nodejs.org.

This tries to implements that, in a way so that it becomes resilient to nodejs and tool-cache changes. Just keep updating NODE_VERSION defined in the dockerfile using dependabot or renovate- the rest of the change will just work regardless of the version you want.

* Refactor (#162)

* Refactor

* Fix

* Fix

* Fix

* Improve logs

* Refactor

* Fix script

* Set --strip-components=1

---------

Co-authored-by: Hidetake Iwata <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant