move example build to the end so we still get a package
build.yaml #124:Commit
45e87cf202
pushed by
lobo
update aws-zig to zig 0.12.0 (example will still fail)
build.yaml #123:Commit
99a61c0bd2
pushed by
lobo
update aws-zig to zig 0.12.0 (example will still fail)
build.yaml #122:Commit
b0cfb5a1c0
pushed by
lobo
add example build at the end so we have models to use for the sample
zig-nightly.yaml #116:Commit
b1b2a6cc7a
pushed by
lobo
add example build at the end so we have models to use for the sample
zig-mach.yaml #115:Commit
b1b2a6cc7a
pushed by
lobo
get build LLVM-approved (riscv64-linux disabled for now)
zig-nightly.yaml #114:Commit
e74a0e9456
pushed by
lobo
get build LLVM-approved (riscv64-linux disabled for now)
zig-mach.yaml #113:Commit
e74a0e9456
pushed by
lobo
update name of build job to what it actually does
zig-nightly.yaml #112:Commit
a3117eea54
pushed by
lobo
update name of build job to what it actually does
zig-mach.yaml #111:Commit
a3117eea54
pushed by
lobo
stop the zig build DOS attack on the CI infrastructure
zig-nightly.yaml #110:Commit
afdc75c1c6
pushed by
lobo
stop the zig build DOS attack on the CI infrastructure
zig-mach.yaml #109:Commit
afdc75c1c6
pushed by
lobo
stop the zig build DOS attack on the CI infrastructure
zig-nightly.yaml #108:Commit
7bff6a5d15
pushed by
lobo
stop the zig build DOS attack on the CI infrastructure
zig-mach.yaml #107:Commit
7bff6a5d15
pushed by
lobo
shell32 has been removed, use USERPROFILE env var instead
zig-nightly.yaml #106:Commit
e6634d3c0f
pushed by
lobo
shell32 has been removed, use USERPROFILE env var instead
zig-mach.yaml #105:Commit
e6634d3c0f
pushed by
lobo
upgrade to nominated zig 2024.3.0-mach (0.12.0-dev.3180+83e578a18)
zig-nightly.yaml #102:Commit
7dcf3d3a2e
pushed by
lobo
upgrade to nominated zig 2024.3.0-mach (0.12.0-dev.3180+83e578a18)
zig-mach.yaml #101:Commit
7dcf3d3a2e
pushed by
lobo