code-server/ci
Asher 3f1a65005b
Allow setting the VS Code build target
For the NPM package (and tests, at least for now), we will still use
linux-x64, but this is going to allow using the platform build targets
for our standalone releases so we can avoid having to copy all the
packaging steps (like cleaning up modules).

This does mean that the NPM package when installed will be missing those
cleanup steps.  Possibly we can try to break out the packaging step into
a something that can be ran standalone (which will also require
installing dev dependencies like gulp) but not sure how much work this
would be.
2026-03-27 12:19:39 -08:00
..
build Allow setting the VS Code build target 2026-03-27 12:19:39 -08:00
dev Add non-maskable PWA icons 2025-07-07 14:40:01 -08:00
helm-chart Update Helm chart and changelog to 4.109.5 2026-03-03 08:24:56 -09:00
release-image Update Debian base image to 13 (trixie) (#7705) 2026-03-20 10:57:17 -08:00
steps Fix npm publish 2024-11-06 12:57:57 -09:00
Caddyfile feat(e2e): add support running behind proxy (#5348) 2022-08-09 18:24:37 +00:00
lib.sh Allow setting the VS Code build target 2026-03-27 12:19:39 -08:00
README.md Update Code to 1.94.2 (#7026) 2024-10-17 20:32:21 -08:00

ci

This directory contains scripts used for code-server's continuous integration infrastructure.

Some of these scripts contain more detailed documentation and options in header comments.

Any file or directory in this subdirectory should be documented here.

  • ./ci/lib.sh
    • Contains code duplicated across these scripts.

dev

This directory contains scripts used for the development of code-server.

build

This directory contains the scripts used to build and release code-server. You can disable minification by setting MINIFY=.

release-image

This directory contains the release docker container image.

  • ./ci/steps/build-docker-buildx-push.sh
    • Builds the release containers with tags codercom/code-server-$ARCH:$VERSION for amd64 and arm64 with docker buildx and pushes them.
    • Assumes debian releases are ready in ./release-packages.

images

This directory contains the images for CI.

steps

This directory contains the scripts used in CI. Helps avoid clobbering the CI configuration.