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

Many of these scripts contain more detailed documentation and options in comments at the top.

Any file and directory added into this tree should be documented here.

1. Change the version of code-server in package.json and push this commit.
2. CI will run and generate an NPM package and release packages that you can download as artifacts on Github Actions.
3. Create a new draft release with the built release packages.
4. Run some basic sanity tests on one of the released packages.
5. Publish.
6. Download the built npm package and publish it.
7. Place the debian releases into ./release-packages and then push the docker image with ./ci/release-container/push.sh.
   1. This will need to be ran on an ARM64 instance as well.
   2. At some point we need to automate this.

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

• ./dev/container
  • See CONTRIBUTING.md for docs on the development container
• ./dev/ci.sh (yarn ci)
  • Runs formatters, linters and tests
• ./dev/fmt.sh (yarn fmt)
  • Runs formatters
• ./dev/lint.sh (yarn lint)
  • Runs linters
• ./dev/test.sh (yarn test)
  • Runs tests
• ./dev/vscode.sh (yarn vscode)
  • Ensures lib/vscode is cloned, patched and dependencies are installed
• ./dev/vscode.patch
  • Our patch of VS Code to enable remote browser access
  • Generate it with yarn vscode:diff and apply with yarn vscode:patch
• ./dev/watch.ts (yarn watch)
  • Starts a process to build and launch code-server and restart on any code changes
  • Example usage in CONTRIBUTING.md

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

• ./lib.sh
  • Contains code duplicated across these scripts.
• ./build/build-code-server.sh (yarn build)
  • Builds code-server into ./out and bundles the frontend into ./dist.
• ./build/build-vscode.sh (yarn build:vscode)
  • Builds vscode into ./lib/vscode/out-vscode.
• ./build/build-release.sh (yarn release)
  • Bundles the output of the above two scripts into a single node module at ./release.
• ./build/build-static-release.sh (yarn release:static)
  • Requires a release already built in ./release.
  • Will build a static release with node and node_modules into ./release-static
• ./build/clean.sh (yarn clean)
  • Removes all git ignored files like build artifacts.
  • Will also git reset --hard lib/vscode
  • Useful to do a clean build.
• ./build/code-server.sh
  • Copied into static releases to run code-server with the bundled node binary.
• ./build/test-release.sh
  • Ensures code-server in the ./release-static directory runs
• ./build/build-packages.sh (yarn package)
  • Packages ./release-static into an archive in ./release-packages
  • If on linux, nfpm is used to generate .deb and .rpm
• ./build/nfpm.yaml
  • Used to configure nfpm to generate .deb and .rpm
• ./build/code-server-nfpm.sh
  • Entrypoint script for code-server for .deb and .rpm

This directory contains the release docker container.

This directory contains the container for CI.

This directory contains a few scripts used in CI. Just helps avoid clobbering .travis.yml.

• ./steps/test.sh
  • Runs yarn ci after ensuring VS Code is patched
• ./steps/release.sh
  • Runs the full release process
  • Generates the npm package at ./release
• ./steps/static-release.sh
  • Takes the output of the previous script and generates a static release and packages