Jump to: navigation, search

Difference between revisions of "Puppet/CI"

Line 18: Line 18:
 
| gate-puppet-openstack-integration-{3,4}-scenarioX-tempest-dsvm-{centos7,trusty} || Functional testing jobs that will deploy OpenStack run tempest smoke to validate OpenStack is actually working. Now deploy Puppet 3 but our team is testing Puppet 4 too. More details [https://github.com/openstack/puppet-openstack-integration#description here] ||  style="background-color: lightgreen;" | 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. It can also be a problem in Tempest, a new test that is failing or a new parameter which is missing.
 
| gate-puppet-openstack-integration-{3,4}-scenarioX-tempest-dsvm-{centos7,trusty} || Functional testing jobs that will deploy OpenStack run tempest smoke to validate OpenStack is actually working. Now deploy Puppet 3 but our team is testing Puppet 4 too. More details [https://github.com/openstack/puppet-openstack-integration#description here] ||  style="background-color: lightgreen;" | 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. It can also be a problem in Tempest, a new test that is failing or a new parameter which is missing.
 
|-
 
|-
| check-tripleo-ironic-overcloud-f21puppet-nonha || Deploy a [https://wiki.openstack.org/wiki/TripleO TripleO] overcloud by running Puppet OpenStack modules. || style="background-color: orange;" | 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).
+
| check-tripleo-ironic-overcloud-f21puppet-nonha || Deploy a [https://wiki.openstack.org/wiki/TripleO TripleO] overcloud by running Puppet OpenStack modules. || style="background-color: orange;" | 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). Also make sure to consult the [http://tripleo.org/cistatus.html status of TripleO CI].
 
|}
 
|}

Revision as of 12:27, 17 March 2016

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-openstack-integration-{3,4}-scenarioX-tempest-dsvm-{centos7,trusty} Functional testing jobs that will deploy OpenStack run tempest smoke to validate OpenStack is actually working. Now deploy Puppet 3 but our team is testing Puppet 4 too. More details here 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. It can also be a problem in Tempest, a new test that is failing or a new parameter which is missing.
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). Also make sure to consult the status of TripleO CI.