The developer has encountered the first line of defense protecting Mesa’s CI infrastructure: developers need permission to run Mesa’s CI pipelines. Since developer forks don't run pipelines automatically, the pipelines will include unrelated jobs, but the ci_run_n_monitor tool makes it easy for developers to target just the jobs that they want to test. Once a developer opens a merge request against the main Mesa repository, the CI system is more selective about which jobs to add to the pipeline because all of these jobs will need to pass before a proposed change is merged into Mesa.