Remove outdated info from CI page

Anthony Wang 2022-09-25 22:04:40 +00:00
parent 0a0a0e286f
commit 6bb372abe8

16
CI.md

@ -2,23 +2,11 @@ We host [Woodpecker CI](https://woodpecker-ci.org/) at https://ci.exozy.me.
## Usage
Ask on Matrix if you would like access. New users don't have access by default since the CI has some security issues.
You can find some example build pipelines [here](https://git.exozy.me/Ta180m/website/src/branch/main/.woodpecker.yml) and [here](https://git.exozy.me/codedotjs/website/src/branch/main/.woodpecker.yml). Builds are usually extremely fast: less than one second!
You can find an example build pipelines [here](https://git.exozy.me/a/Hello-world/src/branch/main/.woodpecker.yml). Builds are usually extremely fast: less than one second! The repo is cloned to `/tmp/username/reponame`, so you can also SSH into exozyme and inspect failed builds.
### Pipeline `image`
Since our instance runs on the `local` backend rather than the `docker` backend, passing a docker image in the `image` field won't work. Instead, you can pass one of the shells available in the system (ex. `bash`, `fish`), and then it'll run your commands.
### Using Nix in CI
Right now, if you run `nix-shell` in CI, it won't work because `$NIX_PATH` is not set for the user running Woodpecker. Instead, you can export your own profile in the NIX_PATH:
```
export NIX_PATH=/nix/var/nix/profiles/per-user/$USER/channels
```
Replace `$USER` with your shell username, and `nix-shell` and other Nix commands should work.
Since our instance runs on the `local` backend rather than the `docker` backend, passing a container image name in the `image` field will not work. Instead, you should pass one of the shells available in the system (ex. `bash`, `fish`), and that will run your commands.
## See also