The opendev project has been moving away from puppet and this is one of
the puppet modules that is no longer used. To simplify things for us we
are taking the extra step of retiring this repo.
Change-Id: Ibd49cc2311b2b3ee10b5d0ec235f9d247dafdc94
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I874e20de34dc6d37d2abad121288b228ca5278db
Instead of keeping a local copy of spec_helper_acceptance.rb and
requiring updates to all modules for any change, we can move it into the
common helper gem and require it from there. This will make it easier to
create and review changes that affect all puppet modules. Also change
the Gemfile to look for the gem in the local workspace if running in a
zuul environment.
Change-Id: Icfe2ae1d6379bb55a37be833e974c567595053c5
This module does not create a jenkins user within jenkins, so there is
no way its password could have been set to 'secret'. Trying to use this
as JJB's auth credentials was causing the JJB exec to fail. This patch
grabs the default admin password out of /var and uses that for JJB.
Change-Id: Ifa60398acbc494dcfecd0cabaa8c829590c1744e
The snakeoil package uses the host's fqdn for the cert's CN, which means
trying to use '127.0.0.1' as the JJB URL will fail with an SSL error,
and the curl tests will also fail. JJB also doesn't have --insecure or
--cafle options, so it gets a SSL_CERTIFICATE_VERIFY_FAILED when trying
to run. Use the fqdn everywhere instead of the localhost address, and
add the snakeoil certs to the system's trusted bundle.
Change-Id: Iac97910b0d04eada62dd161341ee246a9cf3ebf8
We don't need beaker to check that every single file and package is
installed. It is safe to assume that if puppet ran successfully then it
was also able to successfully find and install packages and apply config
files. Rather than update the tests to reflect new names of Java
packages on xenial, we can reduce maintenance costs by just removing the
tests.
It's important to keep tests that check that the service is running and
working correctly, because it is possible for puppet to claim success
but for the application to not be working.
Change-Id: Ifd41b858812638191049f415bbdf78c1f3145e46
Our CI has a real jenkins user that needs to be able to SSH to nodes in
order to copy logs, so don't overwrite its authorized keys file. We can
still test everything else about the jenkinsuser class.
Change-Id: I766f9992359a19277eda94f59835a0c9263e540a
This was added by commit de7975c--Gerrit change 7--so old it
predates Change-Id headers in the repo (and, apparently, commit
messages). Today it seems to be completely unused. The pubring.gpg
contained just this one key:
pub 2048R/32EE128C 2010-08-15
uid OpenStack Hudson <hudson@openstack.org>
sub 2048R/92E212FC 2010-08-15
Based on discussion in IRC, Monty vaguely recalls this might have
been related to DEB package building once upon a time (something we
no longer do and wouldn't configure from this module anyway when
eventually want to start doing again).
Change-Id: I70c3b82185681ee64791cda653360c26a93bd466
Add acceptance tests for puppet-jenkins module so that once the module
is applied we check if files were created, packages were installed and
services were started.
Change-Id: Ib69055af29de08902aba8a9e1b12d716584a2e3d
Co-Authored-By: Bruno Tavares <btavare@thoughtworks.com>
Co-Authored-By: Danilo Ramalho <dramalho@thoughtworks.com>
Co-Authored-By: Maitê Balhester <mbalhest@thoughtworks.com>
Clark Boylan