a
/
code-server
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
code-server/ci
History
Timur Sultanaev 1ffca5751c introduce extraInitContainers to helm chart 
New extraInitContainers configuration added.
It allows to pass template with a list of containers to execute before
main code-server container started. Main container will only start when
all init containers are  completed (exited with 0 code).

 Additionally changes the way extraContainers is used - instead of
 toYaml use tpl, because this allows to
 reference any values from extraContainers string.
 		2021-05-20 17:52:35 +02:00
..
build fix(release-prep.sh): don't update CHANGELOG 2021-05-14 16:09:06 -07:00
dev feat: add CHANGELOG 2021-05-10 12:05:55 -07:00
helm-chart introduce extraInitContainers to helm chart 2021-05-20 17:52:35 +02:00
release-image Check the logged user instead of $USER (#3330) 2021-05-11 10:26:38 -05:00
steps dev(ci): complete refactor 2021-04-08 23:42:01 +05:30
README.md fix: use next version in changelog 2021-05-14 16:09:30 -07:00
lib.sh v3.10.1 (#3406) 2021-05-17 14:59:41 -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

  1. Run yarn release:prep and type in the new version i.e. 3.8.1
  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.
    2. Change the @ to target the version branch. Example: v3.9.0 @ Target: v3.9.0
  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. 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.
  8. Update the AUR package.
  9. Wait for the npm package to be published.

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.