11:44 a.m.
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--gDVuifhQiPSBA5FRXKxtwuqsdGu3P0cAf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Tue 11 Mar 2014 09:55:08 AM CET, Allon Mureinik wrote:
----- Original Message -----
> On Mon 10 Mar 2014 09:15:12 AM CET, Eyal Edri wrote:
>> Hi,
>>
>> Recently I've been approached by several developers who are working o=
n
>> enabling
>> vdsm functional tests on jenkins.ovirt.org, and they need access to t=
he
>> 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, simil=
ar to
>> what we do on jenkins master,
>> maybe at 1st w/o sudo access, and later on adding specific commands t=
o
sudo
>> if it's needed.
>>
>> procedure should be documented in ovirt.org and request should be sen=
t
to
>> infra(a)ovirt.org,
>> explaining the need to access the slaves + public key of the requeste=
r.
>>
>> I think it's important to allow this access if we want our infra to s=
cale,
>> having more
>> people that can fix and solve problems on their specific jobs/project=
s.
>>
>> thoughts/suggestions?
>>
>> Eyal.
>>
>> _______________________________________________
>> Infra mailing list
>> Infra(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>
> IMO each allowed developer must have it's own user/ssh key to log into=
> the slaves.
>
> Also some of the slaves are not reachable from outside (minidells) or
> only reachable from jenkins master or vpn (rackspace). That needs to b=
e
> sorted out also.
Another "parallel" feature would be the ability to pin a job to a slave=
(not sure if this is achievable currently), so you could run a job, logi=
n to the slave, fix something, re-run, repeat.
Mmm, well, if you can configure the job you can pin it to a slave, just=20
click 'restrict where this job can be run' and write there the name of=20
the slave. Is that what you want?
That should only be done on jobs that are in development, as it will=20
greatly affect other runs.
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
>
> Email: dcaro(a)redhat.com
> Web: www.redhat.com
> RHT Global #: 82-62605
>
>
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
--
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--gDVuifhQiPSBA5FRXKxtwuqsdGu3P0cAf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJTHtrzAAoJEEBxx+HSYmnD9IAH/05EJd2OCiWzw/rTAEib9Nj7
zRVIi80aZjXU8xLNJ1nDP3TRjw8zkjXt0m+awwas+/vtVn3XZ633ALZxP2epMfwb
/HilMqNDGkyyJKhUr2ZY2r3Bemnq6EGrOcEXO+lDJCtJFGYeN1ZcupiqmVDibBYo
2MlhkSmj0vUDnBfxmEwbNFDwndoo9QZFRqGdeihGmF5JU3UZm8ibfT4ChXPrKgXi
y9XJJTfwavOdGZZJgaQhR2C42jI8Kh9TDteYypTZwnHtU+orDYNF3F3O5SLKOAZG
wXM0iJgQmvPAn4wl+tTBtfnV3LUhzgs0vRQ5dHxsjmi5Z4F5xeRmTn1j9kWhmBY=
=hYXY
-----END PGP SIGNATURE-----
--gDVuifhQiPSBA5FRXKxtwuqsdGu3P0cAf--