618d4b2340
simply scripts alot, not the null check is necessray because gitlab ci regex with variables is weird and would contain errors otherwise.
...
limit pages to master run only, as we dont export scheduled pages
2022-04-24 10:41:35 +02:00
edce01c336
implement a new tag system for all veloren runners, including
...
- project tag:
- `veloren/veloren`: for the veloren repo only
- `veloren/*`: for projects thats are in the veloren namespace, e.g. usefull for smaller projects that dont have their own tag
- `*/*` for projects by 3rd parties, e.g. personal projects
- trusted tag:
- `owned`: The runner is hosted on veloren hardware
- `trusted`: The runner is hosted by a private person, trusted by the veloren devs
- NONE: if no special trust is given in a runner
- check/build tag:
- `check`: a job only performs a check and NO executable is build for users
- `build`: the job contains atleast 1 executable that can be run by users
- NONE: neither a check nor a executable is build, e.g. usefull for pages or meta jobs
- publish tag:
- `publish`: this job produces a artifact that is automatically pushed to users
- NONE: no artifact is pushed automatically to users
- pin tags:
- `benchmark`: pin a runner to a specific job for the cause of benchmarks
- `veloren/*:macos`: runs on a native macos runner ONLY, this needs to be a modified project tag, as otherwise also normal checks would run on this runner.
- NONE: no runner is pinned
2021-08-19 09:23:31 +02:00
5b4a7722b1
Added veloren-publish tags and veloren-build tags to CI configuration
2021-08-19 09:08:49 +02:00
07c044f2e5
extract relevant code in a script in order to remove duplicate coding with docker-ci repo
...
export VELOREN_ASSETS without pwd to keep caching working
2021-07-14 20:57:08 +02:00
957ba5d218
Use new dungeons in dungeon_voxel_export, remove old dungeon sampling function, and add more of world/examples to CI.
2021-06-27 15:35:43 -04:00
da319e71ec
Added default-publish feature and updated build scripts.
2021-06-26 17:48:48 +01:00
b5ae6227c0
Run clippy for graphviz target in CI and add instructions on how to consume the output.
2021-06-08 15:08:14 -04:00
8f86f474e8
place asset_tweak behind a feature
2021-06-08 13:34:41 +03:00
846df3a18a
--all-targets does not run targets that needs some features which are not provided. --all-features is NOT possible as we have some features which are conflicting.
...
The only possibility is to manually add the features we need to check in CI to the clippy query
2021-06-07 12:29:08 +02:00
32ab0860ca
delete all incremental things for clippy CI
2021-06-01 14:15:01 -04:00
1db0e2a15c
Use new multi image cache scheme in the CI and consolidate runner tag specification so that it is easier to modify
2021-06-01 13:19:12 -04:00
c58eb1cf50
ci fails sporadically, remove file so it doesnt fail that often till we have a bettter toolchain
2021-03-23 10:30:29 +01:00
3d195348d2
fix ci, which was broken by merging unittests and check
2021-01-23 23:05:24 +01:00
a590595149
Merged check and unit tests into single step
...
Reordered commands to run quickest first in order to tie up least CI resource
Fixed some clippy errors in examples
2021-01-19 19:58:51 +01:00
0826707b0d
use --all-targets which is the same as before AND --lib.
...
Just to be future proof, lib should not matter ATM, but might in the future when we produce libs that are not used in any binary target
2021-01-14 08:16:25 +00:00
68be467138
After some discussion with XVar, Song and Yakei we found out that cargo clippy is a superset of cargo check.
...
There are multiple hints:
- one guy in discord https://discord.gg/nWGhnbRb https://discord.com/channels/273534239310479360/335502067432947748/798886188923617290
- a old stackoverflow https://stackoverflow.com/questions/57449356/is-cargo-clippy-a-superset-of-cargo-check which lead us to the source code:
7fa1d78c89/src/main.rs (L73)https://doc.rust-lang.org/cargo/commands/cargo-fix.html )
"executing cargo fix will under the hood execute cargo-check(1)."
- `cargo clippy` fails after running `cargo check` prob as there is nothing to do.
- `cargo clippy --help` points us to `cargo check --help`
Thus we are removing `cargo check` from the CI as a seperate check.
However `cargo check --examples` did check the examples.
In order to have them covered we are also running clippy now for examples, benches and all bins.
Also we moved `--locked` from cargo check to clippy.
2021-01-13 14:22:54 +01:00
a3351be221
running cargo check with -D warnings seems to trigger a complete cache invalidation.
...
AND cargo check was implicitly run in clippy. In order to be future save we now ALWAYS run all CI with -D warnings.
(i verified that this works in a test pipeline)
2021-01-12 01:15:13 +01:00
8c883c200d
Switch veloren_network over to use the official example layout.
...
adjusted those examples to run again
created a CI TEST to always `check` examples
fixed fmt in examples so that pipeline gets green
2020-08-26 10:07:22 +02:00
e1b27c51f5
fix clippy issues in tests and add it to CI
2020-07-01 00:37:15 +02:00
b9344ffeb7
CI cleanup
...
- switching more to rules syntax
- clean up some templates
- EITHER optional builds or build builds
- ordering
2020-06-16 12:45:35 +02:00
