b357ecd467
Explain why rusty-cachier is put first ( #11740 )
2022-06-23 17:54:15 +03:00
2d9f187364
Put rusty-cachier before PR merge into master for cargo-check-benches job ( #11737 )
2022-06-22 19:00:00 +03:00
98f6d8e96c
[ci] use cargo nextest instead cargo test in test-linux-stable ( #11576 )
...
* [DO NOT MERGE] Experimenting with nextest
* enable jobs
* enable stages
* add comment
* create test-frame-support job
2022-06-02 21:18:59 +02:00
a084dd684f
CI: fix build-subkey-macos build job ( #11573 )
...
* CI: fix `build-subkey-macos` build job
* CI: use full path for the `CARGO_TARGET_DIR` default value
2022-06-02 11:48:12 +03:00
7d8477b48d
rusty-cachier pipeline impovements and fixes (#11572 )
2022-06-01 19:48:53 +03:00
bb6bbab687
Fix all warnings when building for wasm ( #11569 )
...
* Fix all warnings when building for wasm
Besides that it also enables warnings as errors for wasm builds in the CI.
* FMT
* Make clippy happy
2022-06-01 13:03:21 +00:00
a4fdcb9a06
Don't limit test-linux-stable-int job output ( #11560 )
2022-06-01 14:28:24 +03:00
c91c1c793e
Introduce rusty-cachier ( #11462 )
...
* Introduce `rusty-cachier`
* Return LF at the end of file
* Use `entrypoint` to `unshare(1)` into a new mount namespace
* Use `rusty-cachier`-provided absolute path for `CARGO_TARGET_DIR` everywhere
* Debug single `build-rustdoc` job
* CI: debug
* CI: debug
* CI: debug
* `unshare(1)` is no longer needed
* CI: remove debug
* Revert "Debug single `build-rustdoc` job"
* Formatiing
* Update scripts/ci/gitlab/pipeline/build.yml
Co-authored-by: Denis Pisarev <denis.pisarev@parity.io >
2022-05-31 17:10:04 +02:00
ce77cb1735
[ci] Adjust job order in pipeline test stage with Gitlab DAG ( #11442 )
...
* [Do Not Merge] Test gitlab DAG in pipeline
* add jobs for pipeline cancel
* add check-tracing to cancel-pipeline
2022-05-18 13:14:25 +02:00
52d9bf24cc
[ci] Divide .gitlab-ci.yml into several files ( #11333 )
...
* rebase
* update Cargo.lock
* revert Cargo.lock
* fix Cargo.lock from 11384
2022-05-11 11:01:02 +02:00
Vlad