Difference between revisions of "Fuel/CI"
Jaegerandi (talk | contribs) (→Fuel CI Overview) |
(→Fuel CI Overview) |
||
| Line 1: | Line 1: | ||
== Fuel CI Overview == | == Fuel CI Overview == | ||
| − | |||
Fuel project uses the Openstack Gerrit infrustructure and follows its [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow], though instead of running tests via Zuul and Co we use just Jenkins. | Fuel project uses the Openstack Gerrit infrustructure and follows its [http://docs.openstack.org/infra/manual/developers.html#development-workflow Development workflow], though instead of running tests via Zuul and Co we use just Jenkins. | ||
| − | There is one Jenkins master node | + | There is one Jenkins master node https://ci.fuel-infra.org which is connected to Openstack Gerrit via Gerrit Trigger plugin using service account '''Fuel CI'''. |
| − | + | All Jenkins slaves are running Ubuntu 14.04 and perform unit tests and deployment tests via [http://docs.fuel-infra.org/fuel-dev/devops.html#environment-creation-via-devops-fuel-qa-or-fuel-main fuel-devops/fuel-qa] framework. | |
== Tests == | == Tests == | ||
Revision as of 15:02, 23 April 2015
Fuel CI Overview
Fuel project uses the Openstack Gerrit infrustructure and follows its Development workflow, though instead of running tests via Zuul and Co we use just Jenkins.
There is one Jenkins master node https://ci.fuel-infra.org which is connected to Openstack Gerrit via Gerrit Trigger plugin using service account Fuel CI.
All Jenkins slaves are running Ubuntu 14.04 and perform unit tests and deployment tests via fuel-devops/fuel-qa framework.
Tests
Fuel Library repo
The heaviest tests are those for fuel-library changes. Each commit to fuel-library repo run two deployments with three virtual machines each. These jobs use preconfigured environment (master node is already deployed and three slaves enabled) and don't do clean start for every run, which may affect the result.
