3 ms·
Gitlab and github both reports issues (excluding the configuration changes, we are talking timeouts during build and also issues with volumes apparently) that p
by bionsystem 4y ago
Gitlab and github both reports issues (excluding the configuration changes, we are talking timeouts during build and also issues with volumes apparently) that people experienced on day one. It's not like it's a hidden, complicated bug, if people like me experience it within minutes of the new version rolling out.
I guess we'll need to change strategy, maybe mark / fix every version everywhere and test both fixed versions and latest (in case our clients decide to upgrade on their own without consulting us first because that's still my main concern as mentionned in another comment), but that would double our CI costs and I'm not sure if I can find the time to duplicate every configuration.
I don't know maybe I'm too old for this.