bughz
/
code-server
mirror of https://github.com/coder/code-server.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
code-server/ci/README.md

113 lines
5.3 KiB
Markdown
Raw Normal View History

Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
# ci
This directory contains scripts used for code-server's continuous integration infrastructure.
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
Some of these scripts contain more detailed documentation and options
in header comments.
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
Any file or directory in this subdirectory should be documented here.
- [./ci/lib.sh](./lib.sh)
- Contains code duplicated across these scripts.
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
## dev
This directory contains scripts used for the development of code-server.
Rename dev/container -> dev/image
2020-06-04 00:09:01 +08:00
- [./ci/dev/image](./dev/image)
refactor: rename doc to docs
2021-02-04 00:32:35 +08:00
- See [./docs/CONTRIBUTING.md](../docs/CONTRIBUTING.md) for docs on the development container.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/dev/fmt.sh](./dev/fmt.sh) (`npm run fmt`)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Runs formatters.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/dev/lint.sh](./dev/lint.sh) (`npm run lint`)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Runs linters.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/dev/test-unit.sh](./dev/test-unit.sh) (`npm run test:unit`)
refactor: add scripts to separate unit, e2e tests
2021-03-10 07:35:25 +08:00
- Runs unit tests.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/dev/test-e2e.sh](./dev/test-e2e.sh) (`npm run test:e2e`)
refactor: add scripts to separate unit, e2e tests
2021-03-10 07:35:25 +08:00
- Runs end-to-end tests.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/dev/watch.ts](./dev/watch.ts) (`npm run watch`)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Starts a process to build and launch code-server and restart on any code changes.
refactor: rename doc to docs
2021-02-04 00:32:35 +08:00
- Example usage in [./docs/CONTRIBUTING.md](../docs/CONTRIBUTING.md).
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/dev/gen_icons.sh](./dev/gen_icons.sh) (`npm run icons`)
Revamp icons (#2383) I took our website's SVG favicon and plopped it on a round white rectangle in Affinity Designer. The I exported it as an SVG and wrote a script that uses imagemagick to convert to the various sizes and formats we need. Closes #2307
2020-12-01 08:11:26 +08:00
- Generates the various icons from a single `.svg` favicon in
`src/browser/media/favicon.svg`.
- Requires [imagemagick](https://imagemagick.org/index.php)
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
## build
Automate draft release
2020-05-12 05:08:22 +08:00
This directory contains the scripts used to build and release code-server.
Simplify packaging and improve scripts Much better test now as well.
2020-05-08 12:34:20 +08:00
You can disable minification by setting `MINIFY=`.
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/build-code-server.sh](./build/build-code-server.sh) (`npm run build`)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Builds code-server into `./out` and bundles the frontend into `./dist`.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/build-vscode.sh](./build/build-vscode.sh) (`npm run build:vscode`)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Builds vscode into `./lib/vscode/out-vscode`.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/build-release.sh](./build/build-release.sh) (`npm run release`)
Switch to a single job to build the npm package The architecture specific jobs pull it in and then build releases. Much faster!
2020-05-08 11:48:49 +08:00
- Bundles the output of the above two scripts into a single node module at `./release`.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/clean.sh](./build/clean.sh) (`npm run clean`)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Removes all build artifacts.
- Useful to do a clean build.
- [./ci/build/code-server.sh](./build/code-server.sh)
Rename binary release to standalone
2020-05-28 04:39:17 +08:00
- Copied into standalone releases to run code-server with the bundled node binary.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/test-standalone-release.sh](./build/test-standalone-release.sh) (`npm run test:standalone-release`)
Rename binary release to standalone
2020-05-28 04:39:17 +08:00
- Ensures code-server in the `./release-standalone` directory works by installing an extension.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/build-packages.sh](./build/build-packages.sh) (`npm run package`)
Rename binary release to standalone
2020-05-28 04:39:17 +08:00
- Packages `./release-standalone` into a `.tar.gz` archive in `./release-packages`.
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- If on linux, [nfpm](https://github.com/goreleaser/nfpm) is used to generate `.deb` and `.rpm`.
- [./ci/build/nfpm.yaml](./build/nfpm.yaml)
- Used to configure [nfpm](https://github.com/goreleaser/nfpm) to generate `.deb` and `.rpm`.
- [./ci/build/code-server-nfpm.sh](./build/code-server-nfpm.sh)
v3.4.0
2020-05-28 06:04:36 +08:00
- Entrypoint script for code-server for `.deb` and `.rpm`.
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- [./ci/build/code-server.service](./build/code-server.service)
- systemd user service packaged into the `.deb` and `.rpm`.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/release-github-draft.sh](./build/release-github-draft.sh) (`npm run release:github-draft`)
chore(ci): migrate from hub to gh (#3168)
2021-04-20 04:51:33 +08:00
- Uses [gh](https://github.com/cli/cli) to create a draft release with a template description.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- [./ci/build/release-github-assets.sh](./build/release-github-assets.sh) (`npm run release:github-assets`)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Downloads the release-package artifacts for the current commit from CI.
chore(ci): migrate from hub to gh (#3168)
2021-04-20 04:51:33 +08:00
- Uses [gh](https://github.com/cli/cli) to upload the artifacts to the release
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
specified in `package.json`.
- [./ci/build/npm-postinstall.sh](./build/npm-postinstall.sh)
- Post install script for the npm package.
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- Bundled by`npm run release`.
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
Rename container and release-container to images and release-image
2020-06-04 00:07:42 +08:00
## release-image
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
Rename container and release-container to images and release-image
2020-06-04 00:07:42 +08:00
This directory contains the release docker container image.
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
fix: relative path in markdown (#6188) Co-authored-by: jinjing.zzj <jinjing.zzj@alibaba-inc.com>
2023-05-09 04:38:52 +08:00
- [./ci/steps/build-docker-buildx-push.sh](./steps/docker-buildx-push.sh)
fix(ci): build+push image in release flow (#3838)
2021-07-30 02:01:46 +08:00
- Builds the release containers with tags `codercom/code-server-$ARCH:$VERSION` for amd64 and arm64 with `docker buildx` and pushes them.
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Assumes debian releases are ready in `./release-packages`.
Fixes for CI from @code-asher's review
2020-05-09 04:31:42 +08:00
Rename container and release-container to images and release-image
2020-06-04 00:07:42 +08:00
## images
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
Rename container and release-container to images and release-image
2020-06-04 00:07:42 +08:00
This directory contains the images for CI.
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
## steps
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
This directory contains the scripts used in CI.
Helps avoid clobbering the CI configuration.
Add NPM package, debs, rpms and refactor CI/build process Closes many issues that I'll prune after adding more docs for users.
2020-04-30 19:52:54 +08:00
CI fixes - Splits up test into fmt, lint and test - Fixes bug in build-packages.sh - Minor README.md fixes
2020-05-13 07:33:34 +08:00
- [./steps/fmt.sh](./steps/fmt.sh)
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- Runs `npm run fmt`.
CI fixes - Splits up test into fmt, lint and test - Fixes bug in build-packages.sh - Minor README.md fixes
2020-05-13 07:33:34 +08:00
- [./steps/lint.sh](./steps/lint.sh)
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- Runs `npm run lint`.
refactor: add scripts to separate unit, e2e tests
2021-03-10 07:35:25 +08:00
- [./steps/test-unit.sh](./steps/test-unit.sh)
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- Runs `npm run test:unit`.
refactor: move integration tests to Jest (#5275) * feat: add installExtension integration test This adds a new helper function called `runCodeServerCommand` along with a test for `--install-extension`. We can use this approach for writing integration tests (i.e. testing a real code-server build, CLI commands, etc). * refactor: s/ test:standalone with test:integration This replaces our integration approach to use Jest instead of a single bash script. By doing this, we will be able to easily maintain and add to our integration test suite. * refactor: filter unit tests Now that our integration tests also use Jest, we need to update our unit test script to ignore `test/integration`. * refactor: add SKIP_SUBMODULE_DEPS to postinstall * refactor: add SKIP_SUBMODULE_DEPS to postinstall * fixup!: skip submod deps * refactor: move runCodeServerCommand into sep. file When Jest runs a test, it loads all the files and imports for that test. This means you might be "requiring" code that's unrelated to your tests. This leads to unexpected errors depending on where the code runs. Moved this file to avoid GLIBC and other errors relaed to argon2 when running integration tests in CI. * fizup: formatting * fizup: increase timeout * refactor: use fixture in installExtension test Instead of relying on a network to install an extension, we use a fixture - vsix file in the repo. This is also faster. * feat: add integration test for listExtensions * chore: ignore integration fixtures * fixup: formatting * fixup: remove custom-hacks.css * fixup: formatting * Update test/integration/installExtension.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/installExtension.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * fixup: contributing integration tests section * fixup: update ci/readme * fixup: use RELEASE_PATH in test-integration.sh * refactor: unzip vsix for listExtensions * refactor: use exec instead of spawn * Update docs/CONTRIBUTING.md Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * Update test/integration/listExtensions.test.ts Co-authored-by: Asher <ash@coder.com> * refactor: use different default binary path * fixup!: formatting Co-authored-by: Asher <ash@coder.com>
2022-06-25 00:33:38 +08:00
- [./steps/test-integration.sh](./steps/test-integration.sh)
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- Runs `npm run test:integration`.
refactor: add scripts to separate unit, e2e tests
2021-03-10 07:35:25 +08:00
- [./steps/test-e2e.sh](./steps/test-e2e.sh)
Update Code to 1.94.2 (#7026) * Update Code to 1.94.2 * Convert from yarn to npm This is to match VS Code. We were already partially using npm for the releases so this is some nice alignment. * Update caniuse-lite This was complaining on every unit test. * Update eslint I was having a bunch of dependency conflicts and eslint seemed to be the culprit so I just removed it and set it up again, since it seems things have changed quite a bit. * Update test dependencies I was getting oom when running the unit tests...updating seems to work. * Remove package.json `scripts` property in release The new pre-install script was being included, which is dev-only. This was always the intent; did not realize jq's merge was recursive. * Remove jest and devDependencies in release as well * Update test extension dependencies This appears to be conflicting with the root dependencies. * Fix playwright exec npm does not let you run binaries like yarn does, as far as I know. * Fix import of server-main.js * Fix several tests by waiting for selectors
2024-10-18 12:31:28 +08:00
- Runs `npm run test:e2e`.
Switch fully to GH Actions
2020-05-08 08:44:32 +08:00
- [./steps/release.sh](./steps/release.sh)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Runs the release process.
- Generates the npm package at `./release`.
Rename binary release to standalone
2020-05-28 04:39:17 +08:00
- [./steps/release-packages.sh](./steps/release-packages.sh)
- Takes the output of the previous script and generates a standalone release and
release packages into `./release-packages`.
Automate release process
2020-05-08 15:08:30 +08:00
- [./steps/publish-npm.sh](./steps/publish-npm.sh)
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
- Grabs the `npm-package` release artifact for the current commit and publishes it on npm.
fix(ci): build+push image in release flow (#3838)
2021-07-30 02:01:46 +08:00
- [./steps/docker-buildx-push.sh](./steps/docker-buildx-push.sh)
- Builds the docker image and then pushes it.
Push docker manifest in CI for multi arch image
2020-05-16 22:55:46 +08:00
- [./steps/push-docker-manifest.sh](./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
Document structure better Closes #1648
2020-05-18 04:53:08 +08:00
`codercom/code-server:latest`.