A colleague has had a lot of problems with our gitlab CI running too slowly.
-
A colleague has had a lot of problems with our gitlab CI running too slowly. I had him send a link over of a particularly bad instance where it takes 30 min to make the MR and then 30 more to release the changes when the pipeline runs on main...
-
A colleague has had a lot of problems with our gitlab CI running too slowly. I had him send a link over of a particularly bad instance where it takes 30 min to make the MR and then 30 more to release the changes when the pipeline runs on main...
well, I found out they have 5 test suites and they run them one at a time inside a single job. So there's no concurrency to make up for all the waiting the tests do.. And they only run on a single CI runner because it's all one job.
So his "I have to wait 60 minutes to release one small change" complaint could easily be cut down to 1/3rd the time by changing his CI definitions and doing NOTHING to the underlying infrastructure
-
well, I found out they have 5 test suites and they run them one at a time inside a single job. So there's no concurrency to make up for all the waiting the tests do.. And they only run on a single CI runner because it's all one job.
So his "I have to wait 60 minutes to release one small change" complaint could easily be cut down to 1/3rd the time by changing his CI definitions and doing NOTHING to the underlying infrastructure
this is genuinely SUCH A RECURRING pattern working in IT. People do shit that is bad and then they blame the infra when their bad shit is bad
-
A colleague has had a lot of problems with our gitlab CI running too slowly. I had him send a link over of a particularly bad instance where it takes 30 min to make the MR and then 30 more to release the changes when the pipeline runs on main...
@rune I read this and thought "this is so much like a Rune post" and then I realized *it was* and you just have a new profile pic
