Skip to content

Review trigger build jobs and extend to test ones, and more.

With recent changes in Mesa (in the stages and the previous on the behavior in fork pipelines) it is useful to adapt how this tool is triggering jobs. This is the main purpose of this merge request, but its development included some side effects contributions.

The core commit in this MR is 33314ba6 to review how the tool is checking the jobs in manual status to decide what should be triggered and what should be left in that state. It is explicitly not triggering "trace" jobs, but there would be more jobs that we can avoid triggering (or even cancel).

Another important contribution is d5accd1f that fixes the attempt to early trigger the pipelines from !108 (merged) with a fix attempt in !110 (merged) that has been reverted in !110 (merged).

The other contribution to highlight is e3dc5388 that make the tool use completely the fork when it is not in production. We already set to create the merge request in the fork to reduce noise in the main upstream project. But with this, it uses everything from and to the fork when it is not in production. This removes the mentioned noise, but also allows us to force conditions in the fork that can reveal a bug to solve.

The other commits in this merge request are secondary improvements that help the whole group. They may have sense on separated merge requests, but can also be included here and make this fix on pack.

  • use venv instead of install virtualenv

  • don't label the uprev MR to not disturb MR-label-maker

  • use the utcnow as the time from GitLab comes in UTC

  • group the list of jobs in certain status by groups to help to search names there.

  • remove a checker spacer that was implemented wrongly and not doing its purpose

  • extend the timeout, as while testing in the fork one can have the test canceled when it's a less priority issue.


Sample pipeline of the result of this contributiuon.

Edited by Sergi Blanch Torné

Merge request reports

Loading