Hi,
Recently I've been approached by several developers who are working on enabling
vdsm functional tests on
jenkins.ovirt.org, and they need access to the slaves running
those tests,
otherwise its almost impossible to debug and fix those tests (errors doesn't
reproduce on their test env).
What i propose is giving "power user" access to jenkins slaves, similar to what
we do on jenkins master,
maybe at 1st w/o sudo access, and later on adding specific commands to sudo if it's
needed.
procedure should be documented in
ovirt.org and request should be sent to
infra(a)ovirt.org,
explaining the need to access the slaves + public key of the requester.
I think it's important to allow this access if we want our infra to scale, having
more
people that can fix and solve problems on their specific jobs/projects.
thoughts/suggestions?
I think it will be great when more people can get issues resolved and get the tests
stable. IMHO this is really a high priority to have a solid foundation (100% working basic
tests) before we add higher level integration tests and flows
Thanks,
michal