a
/
code-server-2
mirror of https://git.tuxpa.in/a/code-server.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
code-server-2/ci
History
Joe Previte 6f98e08bda
feat(ci): add audit job for security 		2021-04-06 11:06:04 -07:00
..
build Remove ipc.d.ts from final build 2021-04-01 10:56:25 -05:00
dev feat(ci): add audit job for security 2021-04-06 11:06:04 -07:00
helm-chart chore(release): bump version to 3.9.2 2021-03-25 10:33:47 -07:00
images fix(lib/vscode): remove native-keymap and keytar (#2961) 2021-03-25 22:20:58 +05:30
release-image Update fixuid 0.5 and add zsh to Docker image (#2925) 2021-03-22 16:15:06 -05:00
steps feat(ci): add audit job for security 2021-04-06 11:06:04 -07:00
README.md docs(ci): update step 1 of publish release 2021-03-24 17:51:06 -07:00
lib.sh refactor: change get_artifacts_url in lib.sh 2021-03-26 10:30:32 -07: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. 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.
    1. Install homebrew
    2. Run brew bump-formula-pr --version=3.8.1 code-server and update the version accordingly. This will bump the version and open a PR. Note: this will only work once the version is published on npm.

Updating Code Coverage in README

Currently, we run a command to manually generate the code coverage shield. Follow these steps:

  1. Run yarn test:unit and make sure all the tests are passing
  2. Run yarn badges
  3. Go into the README and change the color from red to green in this line:
![Lines](https://img.shields.io/badge/Coverage-46.71%25-red.svg)

NOTE: we have to manually change the color because the default is red if coverage is less than 80. See code here.

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.