summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFedja Beader <fedja@protonmail.ch>2024-04-05 22:26:17 +0200
committerFedja Beader <fedja@protonmail.ch>2024-04-06 15:30:14 +0200
commit98d52412c4caced9890add0d8433de4bec698bcd (patch)
tree4b7574d9f691570a5bc10276577c56c208f52c33
parent7dad7f273d46af6d2299f3615a426819563f527a (diff)
downloadplus-98d52412c4caced9890add0d8433de4bec698bcd.tar.gz
plus-98d52412c4caced9890add0d8433de4bec698bcd.tar.bz2
plus-98d52412c4caced9890add0d8433de4bec698bcd.tar.xz
plus-98d52412c4caced9890add0d8433de4bec698bcd.zip
Disable gcc-snapshot CI job.. do we really need to waste CI and dev time
testing the very bleeding edge for every commit everywhere? Should still be made to run every so often... TODO
-rw-r--r--.gitlab-ci.yml4
1 files changed, 3 insertions, 1 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index acf3d1d81..b5fdadd49 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -91,7 +91,9 @@ variables:
tags:
- docker
-gcc-snapshot_sdl2:
+# Do we really need to test such bleeding edge?
+# It's mostly a waste of CI time and it should be made allow-fail, perhaps?
+.gcc-snapshot_sdl2:
stage: prebuild
script:
- export PATH="/usr/lib/gcc-snapshot/bin:/usr/lib/gcc-snapshot/lib:$PATH"