Jump to: navigation, search

Difference between revisions of "Puppet/CI"

Line 1: Line 1:
 
This is a list of the CI jobs that are running against most of Puppet OpenStack modules:
 
This is a list of the CI jobs that are running against most of Puppet OpenStack modules:
 +
 +
The code that configure Jenkins jobs is hosted by [http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/puppet-module-jobs.yaml project-config].
  
 
{|class="wikitable sortable"
 
{|class="wikitable sortable"

Revision as of 17:42, 5 July 2015

This is a list of the CI jobs that are running against most of Puppet OpenStack modules:

The code that configure Jenkins jobs is hosted by project-config.

Job name Description Voting What to do in case of failure
gate-puppet-<module>-puppet-lint It makes sure the code follows recommended Puppet style guidelines Yes Read the job logs to see where the code does not follow the Puppet lint style.
gate-puppet-<module>-puppet-syntax-{3,4} Syntax checks for Puppet manifests, templates, and Hiera YAML. The jobs runs on latest Puppet 3.x and 4.x releases. Yes Read the job logs to see where the code does not follow the Puppet syntax style.
gate-puppet-<module>-puppet-unit-{3.4,3.6,3.7,3.8,4.0} RSpec tests for Puppet manifests. The jobs runs on Puppet 3.4, 3.6, 3.7, 3.8 and 4.0. Yes Read the job logs to see where the tests are failing. More documentation about RSpec
gate-puppet-<module>-puppet-unit-latest RSpec tests for Puppet manifests. The jobs runs on the latest version of Puppet. It aims to be experimental to track any work to do in the module to be compatible with the latest release of Puppet. No Read the job logs to see where the tests are failing. Even though the job is not voting, please raise a bug in Launchpad to make sure someone have a look and maybe update the module to work with latest version of Puppet.
gate-puppet-<module>-puppet-beaker-rspec-dsvm-{centos7,trusty} Beaker jobs to do functional testing. It will prepare the Puppet environment on 2 different systems (CentOS 7 and Ubuntu Trusty), run Puppet to configure the module resources and run some tests with serverspec. Yes Read the job logs. Sometimes, the job fails because of packaging issues or mirrors downtime. Please report a bug for this so we can find workarounds. Otherwise, make sure your patch is supposed to work with current tests or you'll have to adapt the tests to change the expected behavior. More documentation about Beaker
gate-puppet-<module>-puppet-beaker-rspec-upgrade-dsvm-{centos7,trusty} The jobs will deploy the module with current HEAD^1 (current master or latest patch in the dependency tree), run Beaker, apply the patch and run Beaker again. The goal is to track if the patch is breaking an existing infrastructure and test if resources do survive an upgrade and are still idempotent. After our Kilo release, this job will probably deploy Kilo and test the upgrade to Liberty. No If the regular gate-puppet-<module>-puppet-beaker-rspec-dsvm-{centos7,trusty} job is not failing but the upgrade job does, you might have something that break upgrades in your patch. Even though this job is experimental, it's still interesting t have a look at the logs.
check-tripleo-ironic-overcloud-f21puppet-nonha Deploy a TripleO overcloud by running Puppet OpenStack modules. No If it's not a TripleO CI downtime, you can dig into os-collect-config.txt.gz logs to see why catalog is failing. Sometimes it's very interesting to test the modules against a real use-case (TripleO is an OpenStack installer).