- Oct 19, 2021
-
-
Hugo Beauzée-Luyssen authored
This way the application knows if the progress was reset or not, and can save a later fetch Fix #369
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
This was broken and was removing the previous bench results even on success cases
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
This way the jobs will execute in order, won't download all artifacts from previous builds, and won't fail to launch in a schedule due to the dependent job not being spawned
-
Hugo Beauzée-Luyssen authored
So that we might understand how to detect a pipeline originating from a recently merged MR
-
Hugo Beauzée-Luyssen authored
an `-if:` rule already implies `on_success`
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
If running from a schedule, we expect the schedule to run on master or a 0.x.y branch, not feature branches, so we can just use the branch the pipeline runs on
-
Hugo Beauzée-Luyssen authored
We don't care about uploading the new results if the perf decrease. Either it was a sporadic perf issue due to the runner being loaded, or it's a real performance problem which we shouldn't merge, but if we do, we definitely want next pipeline to signal a performance issue
-
Hugo Beauzée-Luyssen authored
We were prepending two dots instead of one when shipping the artifact
-
Hugo Beauzée-Luyssen authored
Until we find a good way of regenerating the test database for the master branch
-
Hugo Beauzée-Luyssen authored
This way, the benchmark jobs won't start if the checks fail, or if the debian tests fail. If specifying `needs: []` the job doesn't start when it shouldn't, but when it starts, it uses all artifacts from all previous test jobs, which causes warning at best, or tries to use the windows artifacts.
-
Hugo Beauzée-Luyssen authored
This will help us use that value inconditionnaly in later jobs
-
Hugo Beauzée-Luyssen authored
They were re-enabled by mistake
-
- Oct 18, 2021
-
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
- Oct 15, 2021
-
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
- Oct 13, 2021
-
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
There's a single request to execute, sqlite will start an implicit transaction.
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-
Hugo Beauzée-Luyssen authored
-