-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
build: enable GitPod prebuilds #43698
Conversation
The changes look good and simple enough, but I thought that our goal was to enable prebuilds for GitHub codespaces. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@targos I have arguments against such an approach, but if a conversation already happened, it's likely those arguments have been addressed. Is this in an issue somewhere? My hope would be that we could land this and start using it immediately, and switch to (or add) another approach if a better (or more company-neutral) one becomes available. The advantages of using GitPod right now are:
Similar efforts:
|
Who is "us" ?
A PR: #40825 I have no intention to block this, (the easier it is for everyone to contribute, the better), but I'd like to understand what your arguments against Codespaces are, as I think a lot of time was already spent trying to set that up. |
Node.js. You, me, the rest of the TSC, the OpenJS Foundation..... There's no cost for the node core repo to use this. (There are limitations of the free tier and we may run up against a limitation at some point, but getting started with this is certainly free, and it's worked OK for my fork.) |
@targos That PR is an attempt to set up a vendor-neutral configuration file that could be used by CodeSpaces, GitPod, and presumably other vendors. If that PR lands, it would make this one obsolete when |
The main concerns I have is that (IIUC) there is no free tier for open source projects like ours in Codespaces. But I wouldn't be at all surprised if that is outdated/incorrect or otherwise irrelevant to our situation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
GitHub app permissions required are specified at https://www.gitpod.io/docs/github-integration. They are:
|
I usually use GitPod. I have not built nodejs successfully at CodeSpace, the machine in CodeSpace is only 4 core, 8 GB RAM. it is very limited. So I will strong +1 for this pr. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Landed in d4b1c23 |
PR-URL: #43698 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
👋 from Gitpod. Extending an ICMYI regarding our https://www.gitpod.io/blog/gitpod-for-opensource program which provides plan upgrades for open-source maintainers and key contributors. Members of the |
PR-URL: #43698 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
PR-URL: #43698 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
PR-URL: nodejs/node#43698 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
The goal here is to make it easier to get started contributing to Node.js. Ongoing contributors will find something like this useful too, although there are limitations (such as it won't be useful for compiling Windows executables for testing).
Experience it now by going to https://gitpod.io/#https://github.com/Trott/io.js (which is this PR up and running on my fork of this repository). If you have a GitPod account, you will get (in a matter of seconds) a development environment with a compiled version of the Node.js binary and artifacts in place so that recompiling small changes won't take much time either. People wishing to get started developing in Node.js core (and people wishing to not have to recompile after every V8 update, etc.) won't need to install the compilation tool chain and so on.
This will be very useful to have installed (even if only temporarily) for Grace Hopper Open Source Day.
This will probably require installing the GitPod app to this repository, so /ping @nodejs/tsc.