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: I8f5c94b34373cb0cc7696e0a19168db186e8164e
A subsequent patch will change how the the cgit apache vhost will be
defined, so add tests now to ensure that the future change produces
identical config files.
Change-Id: Ib8c1c3c63b52a6ea90bf25222fe0dba6936409da
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: If86144ecaf206ada80aebae350504c0d51495dff
Since the beaker jobs are being run on xenial, we need a special nodeset
for it, otherwise beaker gives an error:
beaker-hostgenerator was not able to use this value as input.
Exiting with an Error.
We also want to install puppet from the Ubuntu repos rather than from
puppetlabs, since puppetlabs doesn't support puppet 3 for Xenial. For
centos we can keep the install process the same.
Finally, since the epel repo is now disabled by default on nodepool
nodes, make sure it's enabled in the package resource.
Change-Id: Ifd2244ae9dd212b2475f9cd6adb994bc058a4769
If things are working correctly, then there may only be one port number
for a given port type, so it may not be part of a comma-separated list.
This patch relaxes the tests to allow a single port number instead of
strictly a comma-separated list in the output of `semanage port -l`.
Change-Id: Iaa9c8cda7a2eae904eb8f25cfa33be249b2b4cab
These tests ensure that selinux is set up properly for the basic case
as well as for when behind_proxy is set and higher ports are used.
Change-Id: I9d359b3fc71c7a83b6094f7ee535ab8418f20468
Depends-On: Ia985dad81a95130ea55bb6479632375ac4ea6d24
As discussed on another project patches when introducing tests[1], we
would like to keep the tests closer to the where we apply the spec.
This change makes the testing structure consistent to the feedback given
on puppet-bandersnatch discussion.
[1] https://review.openstack.org/#/c/221941/
Change-Id: I12b50747b9a8e40fe76af25f54b734f6239ff425
Co-Authored-By: Danilo Ramalho <dramalho@thoughtworks.com>
Add acceptance tests for puppet-cgit module so that once the module is
applied we check if files were created, packages were installed and
services were started.
Co-Authored-By: Bruno Tavares <btavare@thoughtworks.com>
Co-Authored-By: Danilo Ramalho <dramalho@thoughtworks.com>
Change-Id: I8d12999b6d91f1ab67fa16d6bbd8bc1d2efa3a05
When running in CI, zuul-cloner clones repos to namespaced directories,
e.g. openstack-infra/puppet-cgit/. When running regular git clone, by
default it clones directly into the present working directory, e.g.
puppet-cgit/. This makes the relative directory inconsistent between
developer-run tests and CI jobs. This patch fixes the issue by telling
git clone to clone into the same directory that zuul-cloner would clone
it to.
Change-Id: I30ef38cda3420efc8834342298441e0733f0fb99