Commit Graph

7 Commits

Author SHA1 Message Date
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
Andreas Jaeger b72eed6fba Remove zuul-sudo-grep lines from nodepool
File
http://git.openstack.org/cgit/openstack-infra/openstack-zuul-jobs/tree/playbooks/legacy/pre.yaml#n54
sets up sudoers for zuul-sudo-grep.sh, remove it from nodepool images.

Change-Id: Ibd8b6024975587a0d137477808c212dfd3f91e76
2018-02-05 21:43:38 +01:00
Matthew Thode 56929e4639
make a gentoo nodepool image
Depends-On: I17202de3016616ce34c8cbead7d0fb047a64e96b

Change-Id: Icf5e7e8bc4f005111cd2492d3c1a2c492b8a7a96
2017-10-18 15:20:11 -05:00
Clark Boylan 5f83fec479 Put /home/zuul/cache in place on test node images
We use paths relative to the current user's homedir to find the location
of the cached files for devstack. Unfortunately we only set up the
symlink for that in Jenkins' homedir and not Zuul's. Update that so
either user can find the cache.

Change-Id: Iff9bcb9700ad5eab36cf8c42d5b6c145dee342b5
2017-10-10 14:39:43 -07:00
Clark Boylan a4331953bd Zuul versions of sudo grep checks
Old legacy jobs will continue to want tocheck that the test user isn't
using sudo if sudo has been disabled. Add a zuul version of the checker
script and update the sudo rules to allow the zuul user to run it.

Change-Id: I10720cdec309dc8418b6cf7e9badf9a04aa8e98e
2017-09-28 14:15:18 -07:00
Andreas Jaeger ec333103e1 Always add zuul group to zuul user
Not all distros - like openSUSE - create a separate group for each user.
Be explicit when creating zuul user like in
nodepool/elements/jenkins-slave/install.d/20-jenkins-slave.

Code later assumes that user and group are both named zuul, so we need
to set the specific zuul group.

Also, set /bin/bash as root shell following a similar change for
jenkins done in Ic671b7c5344a1e7980bede88bee730b50764e60b to keep these
two invocations in sync.

Change-Id: Iec8de3c0799aa023ace8f172f84bf8a137d0967b
2017-04-28 10:14:59 +02:00
Ian Wienand 0feb838506 Don't use devuser for zuul-worker
The devuser element is designed to add a single development user and
manage their keys.  Any local use of devuser by a developer thus
silently conflicts with zuul-worker.

Additionally, this is currently tacitly taking the public-key from
~/.ssh/id_rsa.pub -- i.e. the public key of the currently building
user.  Mixing permissions from the builder into the final-image makes
sense for a development-user case, but not for deploying worker
accounts.

This simply creates the worker account by hand, which is easy enough.
To maintain the status-quo we still source ~/.ssh/id_rsa.pub by
default, but provide a documented flag to override this.

Change-Id: Ic9c9e415c158ad1f057b8d2aa2776dbe2bbd1e47
2016-06-27 11:01:47 +10:00