openstack
/
project-config
Code Issues Proposed changes
project-config/nodepool/elements/zuul-worker
History
Paul Belanger c919e1e782 Remove jenkins-slave element from DIB images 
There is no jenkins, only zuul! With zuulv3 running in production,
there is no more need to add jenkins user or scripts to our images.

Move chmod of /opt/cache/files from
nodepool/elements/jenkins-slave/install.d/20-jenkins-slave to
nodepool/elements/zuul-worker/install.d/60-zuul-worker

We also leave the jenkins-slave elements for now, in case 3rd party CI
use them.

Change-Id: Ia9750877fbc1a17ec467ca4ac685afdb9c1627f8
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
 		2018-03-05 14:29:26 +01:00
..
extra-data.d Don't use devuser for zuul-worker 2016-06-27 11:01:47 +10:00
install.d Remove jenkins-slave element from DIB images 2018-03-05 14:29:26 +01:00
README.rst Don't use devuser for zuul-worker 2016-06-27 11:01:47 +10:00
element-deps Don't use devuser for zuul-worker 2016-06-27 11:01:47 +10:00
package-installs.yaml Add ansible dependencies to infra-package-needs 2017-09-14 12:30:25 -04:00
pkg-map Cleanup zuul-worker pkg-map 2017-09-22 14:32:50 -04:00

README.rst

zuul-worker

Setup a node to be a zuul worker

User Creation

This element bakes in a zuul user on the host for the zuul-worker process to log in with.

By default login permissions (authorized_keys) will be populated for the zuul user from ~/.ssh/id_rsa.pub -- i.e. the public key of the currently building user. Specify an alternative filename in ZUUL_USER_SSH_PUBLIC_KEY to override this.

The zuul user is provided with passwordless sudo access.