motiejus
/
hermetic_cc_toolchain
1
Fork 0
Code Releases Activity
hermetic_cc_toolchain/.build.yml

45 lines
1.2 KiB
YAML
Raw Normal View History

move to debian/stable
2021-11-22 17:25:02 +02:00
image: debian/stable
add .build.yml
2021-06-08 06:30:06 +03:00
packages:
install direnv
2021-09-07 10:50:16 +03:00
- direnv
shellcheck + email on failure
2021-10-18 15:15:50 +03:00
- shellcheck
run tests with qemu-aarch64
2022-02-04 10:09:32 +02:00
- qemu-user-static
Revert "remove binfmt-support" This reverts commit 88b623287cc88f1c64f0b48630d9a15761d12ac5. Although binfmt-support is a dependency, it does not get installed on CI
2022-12-12 06:06:00 +02:00
- binfmt-support
[ci] install sponge
2022-04-18 13:12:08 +03:00
- moreutils
build.yml: add file this will fix the last test in ci/test
2022-12-11 07:12:43 +02:00
- file
windows tests: move tests, get rid of wine-binfmt This removes all other Bazel test commands, so all tests can be again tested with `bazel test ...`. Also, fixes linux-arm64 glibc tests. Until now they've worked only in CI. Now they work everywhere I tried.
2022-06-02 08:46:16 +03:00
- wine64
add .build.yml
2021-06-08 06:30:06 +03:00
sources:
- https://git.sr.ht/~motiejus/bazel-zig-cc
environment:
fix environment variable
2021-06-08 06:33:06 +03:00
CC: /usr/bin/false
shellcheck + email on failure
2021-10-18 15:15:50 +03:00
triggers:
- action: email
condition: failure
to: motiejus+srht@jakstys.lt
add .build.yml
2021-06-08 06:30:06 +03:00
tasks:
- setup: |
less verbose build
2021-06-19 12:14:19 +03:00
sudo apt-get purge gcc -y && sudo apt-get autoremove -y
Restructure tests to all run in bazel - add rules to run tests for a specific platform - use downloaded buildifier - move lint to a script - rename ci tasks - stop running under qemu-aarch64-static as it doesn't do anything
2022-04-13 15:58:11 +03:00
sudo dpkg --add-architecture arm64
sudo apt-get update
sudo apt-get install libc6:arm64 -y
add gazelle to CI targets
2023-01-18 22:43:33 +02:00
- lint_gazelle: |
[ci] fix syntax error
2021-11-05 20:27:28 +02:00
cd bazel-zig-cc; . .envrc
Restructure tests to all run in bazel - add rules to run tests for a specific platform - use downloaded buildifier - move lint to a script - rename ci tasks - stop running under qemu-aarch64-static as it doesn't do anything
2022-04-13 15:58:11 +03:00
./ci/lint
add gazelle to CI targets
2023-01-18 22:43:33 +02:00
bazel run --color=yes --curses=yes //:gazelle
add //:buildifier to lint rule
2021-11-05 20:22:06 +02:00
git diff --exit-code
[release] add to CI
2022-04-18 12:35:14 +03:00
- test_release: |
cd bazel-zig-cc; . .envrc
./ci/release
ci: catch easy problems early
2022-09-30 15:18:21 +03:00
- list_toolchains_platforms: |
cd bazel-zig-cc; . .envrc
./ci/list_toolchains_platforms
zig launcher: replace shell wrappers with a binary Until now we needed to maintain two versions of the zig launcher: one for Windows and one for everything else. This was problematic for two reasons: 1. I do not know powershell and thus keep breaking the Windows wrapper all the time (see git history of Fabian fixing stuff that I broke). 2. This makes bazel-zig-cc dependent on the system shell, making it not really hermetic. So the recently added `--experimental_use_hermetic_linux_sandbox` does not work with bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`, `/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`. Switching to a Zig-based wrapper solves both issues, and we can do this: bazel build "$@" \ --experimental_use_hermetic_linux_sandbox \ --sandbox_add_mount_pair=/proc \ <...> Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to keep that. I will look into reducing even that dependency separately. Not all is nice and shiny though: this commit replaces ~80 LOC worth of shell scripts wrappers with a singe ~300 LOC zig program, which is arguably harder to understand. However, it is easier to change, at least for me, because it's a single file with unit tests! Most importantly, the gnarly code (which resolves paths and sets environment variables) is cross-platform. Thanks to Fabian Hahn for testing this on Windows and pointing out errors.
2022-12-20 17:00:50 +02:00
- test_launcher: |
cd bazel-zig-cc; . .envrc
./ci/launcher --color=yes --curses=yes
ci: catch easy problems early
2022-09-30 15:18:21 +03:00
- test: |
cd bazel-zig-cc; . .envrc
zig launcher: replace shell wrappers with a binary Until now we needed to maintain two versions of the zig launcher: one for Windows and one for everything else. This was problematic for two reasons: 1. I do not know powershell and thus keep breaking the Windows wrapper all the time (see git history of Fabian fixing stuff that I broke). 2. This makes bazel-zig-cc dependent on the system shell, making it not really hermetic. So the recently added `--experimental_use_hermetic_linux_sandbox` does not work with bazel-zig-cc, unless we bind-mount a bunch of stuff: `/usr`, `/bin`, `/lib`, `/usr/lib:/lib`, `/usr/lib64:/lib64` and `/proc`. Switching to a Zig-based wrapper solves both issues, and we can do this: bazel build "$@" \ --experimental_use_hermetic_linux_sandbox \ --sandbox_add_mount_pair=/proc \ <...> Zig itself still depends on `/proc` for `/proc/self/exe`, so we need to keep that. I will look into reducing even that dependency separately. Not all is nice and shiny though: this commit replaces ~80 LOC worth of shell scripts wrappers with a singe ~300 LOC zig program, which is arguably harder to understand. However, it is easier to change, at least for me, because it's a single file with unit tests! Most importantly, the gnarly code (which resolves paths and sets environment variables) is cross-platform. Thanks to Fabian Hahn for testing this on Windows and pointing out errors.
2022-12-20 17:00:50 +02:00
export BAZEL_ZIG_CC_CACHE_PREFIX=/tmp/bazel-zig-cc-2
./ci/test \
--color=yes --curses=yes \
--repo_env BAZEL_ZIG_CC_CACHE_PREFIX=$BAZEL_ZIG_CC_CACHE_PREFIX \
--sandbox_writable_path "$BAZEL_ZIG_CC_CACHE_PREFIX"