On 24 November 2017 at 14:36, Dan Horák <dan(a)danny.cz> wrote:
ok, I'm pretty sure we can make it work :-) Please send me your
public SSH key and preferred username, then I'll set up you an account
for you and we can work on the remaining details.
I would actually like two keys to be configured, one for our staging system:
And another for the production system:
The user names for the systems are 'jenkins-staging' and 'jenkins'
respectively, though it'll also be ok to use a different user name and
the same user for both. Both those users need to belong to the 'mock'
I have some places in the code where it just assumes it's got
password-less sudo configured and tries to install some needed
dependencies on its own. Those dependencies are most probably not
needed for the builds we're discussing here (They include libvirt and
docker that are used by build processes that escape mock to generate
container and VM images...) , but I'll need to add some checking in my
code and skip those settings if sudo permissions are not available.
This is why I'd rather connect the staging system first.
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
| TRIED. TESTED. TRUSTED. | redhat.com/trusted