a/code-server-2
1
0
Fork 0
mirror of https://git.tuxpa.in/a/code-server.git synced 2024-12-30 14:08:45 +00:00
Code Issues Projects Releases Wiki Activity
fb835838db
code-server-2/ci
History
Asher 3d7fbec40f
Use file system for settings and fix data home path 
It's possible that using browser storage makes more sense with settings
sync, so we might want to revisit this once/if we get settings sync
working. As it currently is though, browser storage just causes jank.

The path was also missing a `User` at the end so I added that. This
might affect the Vim extension which would have been writing to the
wrong path previously but I don't believe it should affect anything
else since they would have been writing to browser storage.

- Fixes #2208
- Fixes #2231
- Fixes #2279
- Fixes #2274
2020-11-20 14:03:07 -06:00
..
build ci: Fix typo in release template 2020-11-19 18:03:12 -05:00
dev Use file system for settings and fix data home path 2020-11-20 14:03:07 -06:00
helm-chart v3.7.2 2020-11-19 17:28:22 -05:00
images ci: Pin nfpm to v1.9.0 2020-11-16 16:57:04 -05:00
release-image release-image: Remap UID within the image before handling $DOCKER_USER (#2223) 2020-10-23 12:07:08 -04:00
steps Update Node to 12.18.4 (#2175) 2020-10-08 16:15:05 -05:00
lib.sh Add auto install script 2020-05-27 15:48:22 -04:00
README.md v3.7.2 2020-11-19 17:28:22 -05:00

README.md

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.

Publishing a release

Make sure you have $GITHUB_TOKEN set and hub installed.

  1. Update the version of code-server and make a PR.
    1. Update in package.json
    2. Update in ./doc/install.md
    3. Update in ./ci/helm-chart/README.md
      • Remember to update the chart version as well on top of appVersion in Chart.yaml.
  2. GitHub actions will generate the npm-package, release-packages and release-images artifacts.
    1. You do not have to wait for these.
  3. Run yarn release:github-draft to create a GitHub draft release from the template with the updated version.
    1. Summarize the major changes in the release notes and link to the relevant issues.
  4. Wait for the artifacts in step 2 to build.
  5. Run yarn release:github-assets to download the release-packages artifact.
    • It will upload them to the draft release.
  6. Run some basic sanity tests on one of the released packages.
    • Especially make sure the terminal works fine.
  7. Make sure the github release tag is the commit with the artifacts. This is a bug in hub where uploading assets in step 5 will break the tag.
  8. Publish the release and merge the PR.
    1. CI will automatically grab the artifacts and then:
      1. Publish the NPM package from npm-package.
      2. Publish the Docker Hub image from release-images.
  9. Update the AUR package.
  10. Wait for the npm package to be published.
  11. Update the homebrew package.

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.

  • ./release-image/build.sh
    • Builds the release container with the tag codercom/code-server-$ARCH:$VERSION.
    • 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.

  • ./steps/fmt.sh
    • Runs yarn fmt after ensuring VS Code is patched.
  • ./steps/lint.sh
    • Runs yarn lint after ensuring VS Code is patched.
  • ./steps/test.sh
    • Runs yarn test after ensuring VS Code is patched.
  • ./steps/release.sh
    • Runs the release process.
    • Generates the npm package at ./release.
  • ./steps/release-packages.sh
    • Takes the output of the previous script and generates a standalone release and release packages into ./release-packages.
  • ./steps/publish-npm.sh
    • Grabs the npm-package release artifact for the current commit and publishes it on npm.
  • ./steps/build-docker-image.sh
    • Builds the docker image and then saves it into ./release-images/code-server-$ARCH-$VERSION.tar.
  • ./steps/push-docker-manifest.sh
    • Loads all images in ./release-images and then builds and pushes a multi architecture docker manifest for the amd64 and arm64 images to codercom/code-server:$VERSION and codercom/code-server:latest.