[wp-trac] [WordPress Trac] #57187: Add devcontainer + Codespaces support
WordPress Trac
noreply at wordpress.org
Fri Feb 10 03:54:14 UTC 2023
#57187: Add devcontainer + Codespaces support
------------------------------+---------------------
Reporter: helen | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: 6.2
Component: Build/Test Tools | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
------------------------------+---------------------
Changes (by helen):
* keywords: has-patch commit =>
Comment:
Notes:
* I think we need to commit the correct permissions on `.devcontainer
/install-tools.sh` and `.devcontainer/setup.sh` rather than changing them
at runtime, because otherwise they show as modified which interferes with
doing version control tasks.
* It took 11 minutes to get from clicking "create a new codespace" to the
environment being fully ready with WordPress installed - this is
manageable with set expectations as a trial run but we need to explore our
options for bringing this down. It was 2.5 minutes to start the container
and open VSCode, so I believe it's `npm install` that is taking the bulk
of the time here. Under 3 minutes total seems ideal to me although it's
just an arbitrary number. I'll ask for help in understanding our options -
because contributors should be running the Codespace from a fork in order
to create a branch and open a PR, I don't think prebuilds work for this
case.
* The setup script output is getting lost - at some point in iterations we
were writing this to `setup.log` which is why it's in the `.gitignore` but
it's gotten dropped - should decide what to do about that (write it to a
file, output it to the terminal, something else?). Output to the terminal
is helpful in reassuring users things are still moving along.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/57187#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list