On Mon, Jul 20, 2020 at 05:18:54PM +0100, Peter Maydell wrote: > On Thu, 9 Jul 2020 at 03:47, Cleber Rosa <cr...@redhat.com> wrote: > > > > The idea about a public facing Gating CI for QEMU was summarized in an > > RFC[1]. Since then, it was decided that a simpler version should be > > attempted first. > > > > At this point, there are two specific runners (an aarch64 and an s390) > > registered with GitLab, at https://gitlab.com/qemu-project, currently > > setup to the "qemu" repository. > > Could I have a simple "this is the command you need to run to > test your staging branch with the project gitlab" set of > getting-started instructions, please? > > thanks > -- PMM >
Hi Peter, Sure. It's important that PATCH 2/2 in this series is included in a branch that you need to push to the "staging" branch on the https://gitlab.com/qemu-project/qemu repo (it could be just that one patch). Then, you can run: ./scripts/ci/gitlab-pipeline-status --verbose -w And that should be it. You can drop '--verbose' if you just want the final outcome as the result. A longer explanation: that command defaults to checking for the pipeline associated with the commit for the *local* staging branch. You can check the pipeline results on other commits, such as the latest master (by the time I write this): $ ./scripts/ci/gitlab-pipeline-status --verbose -c 1e6c50ad8559c18b21041ef69d8fff781a8db0bb success Please let me if anything goes wrong, as I wasn't able to submit jobs to those two machines (did so on emulated ones) and the devil lies in the details. Thanks, - Cleber.
signature.asc
Description: PGP signature
