On Tue, Mar 17, 2020 at 09:29:32AM +0000, Peter Maydell wrote: > On Tue, 17 Mar 2020 at 04:59, Cleber Rosa <cr...@redhat.com> wrote: > > Yes, that did the trick and I can now see the configuration. What I can > > *not* see is any "Specific Runner" configured. So maybe: > > > > 1) The documentation I included is not clear enough about the fact that > > setup steps need to be done on a machine so that it becomes a "Runner" > > > > 2) The (Ansible) playbooks (especially > > contrib/ci/orgs/qemu/gitlab-runner.yml) > > is not working as intended > > > > 3) Some expectations misalignment on machines that would be available to run > > those jobs > > > > In any case, none of those should be big problems. Please let me know what > > you did/experienced/expected up to this point, and we can continue from > > there. > > Ah, I see. My assumption was that this was all stuff that you were > working on, so that I would then be able to test that it worked correctly, > not that I would need to do configuration of the gitlab.com setup.
Hi Peter, So, I had to use temporary hardware resources to set this up (and set it up countless times TBH). I had the understanding based on the list of machines you documented[1] that at least some of them would be used for the permanent setup. > I thought all the stuff about "how to set up runners" was only for > people who wanted to set up some 3rd-party CI for non-official > forks or for when we wanted to add extra runners in future (eg for > architectures not yet covered). So the only thing I did was follow > your "just push to staging" instructions. > OK, I see it, now it makes more sense. So we're "only" missing the setup for the machines we'll use for the more permanent setup. Would you like to do a staged setup/migration using one or some of the machines you documented? I'm 100% onboard to help with this, meaning that I can assist you with instructions, or do "pair setup" of the machines if needed. I think a good part of the evaluation here comes down to how manageable/reproducible the setup is, so it'd make sense for one to be part of the setup itself. FIY there's also the possibility of grabbing some free VMs on GCP, Azure, etc and setting them up as GitLab runners in a temporary way (because of the temporarily free and VM nature). I have a few problems with this approach, including the fact that it doesn't yield the complete experience wrt using hardware one owns and will have to manage, besides the hardware limitations themselves. Please let me know how you want to move on from here. Cheers, - Cleber. > thanks > -- PMM > [1] https://wiki.qemu.org/Requirements/GatingCI#Current_Tests
signature.asc
Description: PGP signature
