On Tue, Jun 8, 2021 at 11:09 AM Cleber Rosa <cr...@redhat.com> wrote: > > This builds on top the "GitLab Custom Runners and Jobs (was: QEMU > Gating CI)" series, showing an example of how other entities can > add their own custom jobs to the GitLab CI pipeline. > > First of all, it may be useful to see an actual pipeline (and the > reespective job introduced here) combined with the jobs introduced > on "GitLab Custom Runners and Jobs (was: QEMU Gating CI)": > > * https://gitlab.com/cleber.gnu/qemu/-/pipelines/316527166 > * https://gitlab.com/cleber.gnu/qemu/-/jobs/1325976765 > > The runner (the machine and job) is to be managed by Red Hat, and > adds, at the very least, bare metal x86_64 KVM testing capabilities to > the QEMU pipeline. This brings extra coverage for some unittests, and > the ability to run the acceptance tests dependent on KVM. > > The runner is already completely set up and registered to the > https://gitlab.com/qemu-project/qemu project instance, and jobs will > be triggered according to the same rules for the jobs introduced on > "GitLab Custom Runners and Jobs (was: QEMU Gating CI)", that is, > but pushes to the staging branch. Still, the job is set with mode > "allow failures", so it should not disrupt the existing pipeline. > Once its reliability is proved (rules and service levels are to be > determined), that can be reverted. > > Even though the formal method of tracking machine/job maintainers have > not been formalized, it should be known that the contacts/admins for > this machine and job are: > > - Cleber Rosa > <cr...@redhat.com> > clebergnu on #qemu > > - Willian Rampazzo > <willi...@redhat.com> > willianr on #qemu
Acked-by: Willian Rampazzo <willi...@redhat.com>
