Hello folks,
I've just restarted Jenkins for an security update to a plugin. There was
one running centos-regression job that I had to cancel.
--
nigelb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://bugzilla.redhat.com/show_bug.cgi?id=1567880
--- Comment #3 from Nigel Babu ---
Yeah, we have the option of either setting two levels or giving all access and
depending on trust.
Right now, I'm looking for all Jenkins nodes, build.gluster.org, and the
associated
https://bugzilla.redhat.com/show_bug.cgi?id=1567880
--- Comment #5 from M. Scherer ---
I am also ok with all access, if someone explain the best practice regarding
ssh security and stuff like this. (ideally, key on a smartcard/yubikey, but at
minima, password protected ssh
https://bugzilla.redhat.com/show_bug.cgi?id=1567880
Worker Ant changed:
What|Removed |Added
Status|POST|MODIFIED
---
https://bugzilla.redhat.com/show_bug.cgi?id=1549662
Nigel Babu changed:
What|Removed |Added
Status|NEW |CLOSED
https://bugzilla.redhat.com/show_bug.cgi?id=1567880
Bug ID: 1567880
Summary: Grant Deepshikha access to all CI-related
infrastructure
Product: GlusterFS
Version: mainline
Component: project-infrastructure
https://bugzilla.redhat.com/show_bug.cgi?id=1567880
M. Scherer changed:
What|Removed |Added
CC||msche...@redhat.com