add install pipeline

[evgeni]

needs to be run with:

ansible-playbook pipelines/install_pipeline.yml -e pipeline_os=centos7 -e pipeline_type=pulpcore -e pipeline_version=3.7

this mimics the "pipelines" we have for Foreman/Katello in forklift

todo:

• docs
• jenkins integration

[evgeni]

cc @mikedep333 @jlsherrill @dkliban -- that's for the nightly testing we discussed the other day (minus having nightlies, of course)

[evgeni]

Oh, and you need to manually install the postgresql role, as we're not using the Vagrant provisioner in this setup.

[evgeni]

One of the questions I have is whether this should live in this repo or in forklift.

Why? We would be running those tests on ci.theforeman.org (and ci.centos.org) which has a rather tight coupling with the forklift repo. This has the benefit that currently adding a new pipeline to Jenkins means dropping the right files into the pipelines folder of forklift and then adding a single line to the jenkins config.

If we keep the pipeline here, we'll have to teach jenkins to also check out pulplift etc, while the pipeline part doesn't really use any pulplift specific features and could run from plain forklift (if the roles are available somehow, which is easier to implement).

[evgeni]

Thanks @mikedep333, updated.

But my main question remains unanswered: should this even live in pulplift/pulp_installer or should it live in forklift?
Given the idea is to verify the RPM packages (which you don't own/build), I am kinda torn here.