aboutsummaryrefslogtreecommitdiff
path: root/.github/workflows/ci.yaml
Commit message (Collapse)AuthorAgeFilesLines
* Remove usless pre-cache taskAleksey Kladov2020-08-181-4/+0
| | | | | | We are not cleaning the rest of xtask artifacts, so this effectively does nothing. xtask is small and changes rarely, so this shouldn't really matter.
* Re-enable mac buildAleksey Kladov2020-08-181-1/+1
|
* Temporary disable MacOS builderAleksey Kladov2020-08-131-1/+1
| | | | GH Actions is not feeling great today :-(
* Disabe macros TypeSCript builderAleksey Kladov2020-08-131-1/+1
| | | | It hangs for some reason, and we are moving TS extension anyways...
* Completely remove cargo auditAleksey Kladov2020-08-121-14/+0
| | | | | | | | | My current feeling is that the build maintenance friction it creates is not proportional to the benefits it provides. We are pretty frugal with the set of Rust dependencies, and our security model is "we run build.rs and proc macros", so it doesn't seem like cargo audit could help us much.
* Fix build on musl and test it in CIJonas Schievink2020-08-121-5/+13
|
* Remove the premissions-misconifguration bug workarounds on CIVeetaha2020-07-291-5/+0
|
* Disable audit stepAleksey Kladov2020-07-161-13/+13
| | | | See https://github.com/actions-rs/install/issues/6
* Update actions/cache to v2Yuki Okushi2020-07-141-22/+14
|
* Check power on CIAleksey Kladov2020-07-141-1/+35
|
* check cargo.lockAleksey Kladov2020-07-071-1/+1
|
* Disable npm auditAleksey Kladov2020-07-021-3/+3
| | | | At the moment it fails with unfixable minor vuln in a dev-dependency
* vscode tests configuration for more verbose outputvsrs2020-05-231-0/+2
|
* OS matrix for TypeScriptvsrs2020-05-231-1/+8
|
* xvfb-action fixvsrs2020-05-231-3/+3
|
* Try GabrielBB/xvfb to run vscode testsvsrs2020-05-231-11/+5
|
* Start xvfb manually on ubuntuvsrs2020-05-231-1/+10
|
* try to run TypeScript CI on windowsvsrs2020-05-231-2/+2
|
* Add `npm test` to CIvsrs2020-05-231-0/+3
|
* Use actions-rs/install and /audit-check for cargo-auditLaurențiu Nicola2020-04-111-14/+3
|
* More general CI env varAleksey Kladov2020-04-061-1/+1
|
* Add back deny_cEdwin Cheng2020-04-051-5/+2
|
* Remove deny_c in CIEdwin Cheng2020-04-031-2/+5
|
* Enable backtrace on CIAleksey Kladov2020-03-301-0/+1
|
* Don't deny C for cargo auditAleksey Kladov2020-03-261-1/+2
| | | | It depends on openssl ;-(
* Specify env once for all jobsAleksey Kladov2020-03-261-15/+8
|
* cicd: revive npm auditveetaha2020-03-181-2/+2
|
* Disable npm audit, as it blocks unrelated PR without a way to fixAleksey Kladov2020-03-171-2/+2
| | | | https://github.com/rust-analyzer/rust-analyzer/pull/3582#issuecomment-600107117
* Fix cargo registry caching for buildsbjorn32020-03-161-0/+3
|
* Fix audit caching betterAleksey Kladov2020-03-161-1/+2
|
* Fix cargo audit cachingAleksey Kladov2020-03-161-1/+2
| | | | | | See https://github.com/actions/cache/issues/133#issuecomment-599102035 for chown bit
* Actually make npm audit more robustAleksey Kladov2020-03-161-1/+1
| | | | In bash, && and || have the same priority.
* Cache cargo-audit on CIAleksey Kladov2020-03-161-0/+13
| | | | closes #3399
* Retry rust audit as wellAleksey Kladov2020-03-161-0/+4
| | | | https://github.com/rust-analyzer/rust-analyzer/runs/511553989?check_suite_focus=true#step:3:6
* Make audit more reliableAleksey Kladov2020-03-161-1/+1
| | | | | | I've seen this transient error a couple of times: https://github.com/rust-analyzer/rust-analyzer/runs/511162809?check_suite_focus=true#step:5:8
* Use actions/checkout@v2CAD972020-03-071-3/+3
|
* Remove needless depAleksey Kladov2020-03-041-7/+2
|
* Deindent YAMLAleksey Kladov2020-03-041-76/+78
|
* Clean xtask partial artifacts in `xtask pre-cache`Christopher Durham2020-03-031-1/+1
|
* Actually gate CI on eslintAleksey Kladov2020-02-271-1/+1
|
* Merge pull request #3330 from Veetaha/feature/cargo-auditAleksey Kladov2020-02-261-0/+10
|\ | | | | cicd: add cargo audit
| * cicd: add cargo auditVeetaha2020-02-261-0/+10
| |
* | vscode: added audit at ciVeetaha2020-02-261-1/+6
|/
* Check that we use no C deps on CIAleksey Kladov2020-02-191-0/+1
| | | | | | | | | C deps are not a problem for a typical build, but cause issues in more esoteric scenarios, like cross-compiling. Let's check that we don't have them. Setting `CC` to some dummy value should do the trick, as custom build scripts typically respect this variable.
* Gate stuff on CIAleksey Kladov2020-02-181-0/+2
|
* Don't fail fast on CIAleksey Kladov2020-01-221-0/+1
|
* Don't be overly genericAleksey Kladov2020-01-111-2/+1
|
* Split out into a release build as bins were not getting generated as cargo ↵Giles Cope2020-01-091-32/+0
| | | | build wasn't run
* second attemptGiles Cope2020-01-091-1/+1
|
* parameterised debugGiles Cope2020-01-091-3/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-18 06:20:06 +0000