This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Change-Id: Ic27fb8019ab35fbdf45e23164f907c6c6baf8655
As vagrant using xenial so no python2 installed, hence test script will
fail. This installs python2 before executing the tests
Change-Id: I0dbfae47b0ef057a255952f2f68531da0a184a5d
The run_tests.sh script fails when it is run multiple times on CentOS.
The `bindep` run returns an empty list of packages and then `yum`
exits with an error since no packages were provided to install.
This patch checks the length of the `bindep` output and skips the `yum`
installation when the package list is empty.
The patch also cleans up some of the old cruft left over from previous
scripts and avoids repetition.
Change-Id: Id78d4a7522a363a845b361fa33e4e625ac571f12
Signed-off-by: Major Hayden <major@mhtx.net>
Some Linux distributions, such as CentOS 7 and Xenial, have trouble
validating SSL certificates when using get_url with servers
that use Server Name Indication (SNI).
This patch adds those packages to the list of required packages and
uses bindep to install them in developer test environments the same
way that the gate tests install them.
Change-Id: I532b32a26ca49deb63f66a8f146c7114874bdf87
Paramiko version 2.0 has been released. It now uses the Python library
cryptography. Installing this requires additional system packages. This
commit adds in the appropriate packages required by cryptography based
on its documentation [1].
An alternative approach would have been to constrain the version of
Paramiko however the project describes the 1.x versions as relying on
insecure dependencies [2].
[1] https://cryptography.io/en/latest/installation/
[2] http://www.paramiko.org/installing.html
Change-Id: I25d3a103be3ba5c9d2c9e79322658c65b0fd1b2d
This patch includes the following:
- Base configuration for OpenStack's CI Infrastructure.
- Base documentation build configuration.
- A Vagrantfile for local testing.
- A base test configuration in order to execute a functional test.
- An updated README, added LICENSE file and a CONTRIBUTING file.