Difference between revisions of "Fuel/CI"
(Created page with "== Fuel CI Overview == thumb|right|Fuel CI Infrustructure Fuel project uses the Openstack Gerrit infrustructure and follows its Gerrit Workflow|Gerrit...") |
Jaegerandi (talk | contribs) (→Fuel CI Overview) |
||
| Line 2: | Line 2: | ||
[[File:Fuel-ci.png|thumb|right|Fuel CI Infrustructure]] | [[File:Fuel-ci.png|thumb|right|Fuel CI Infrustructure]] | ||
| − | Fuel project uses the Openstack Gerrit infrustructure and follows its [ | + | 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 http://fuel-jenkins.mirantis.com which is connected to Openstack Gerrit via Gerrit Trigger plugin using service account '''Fuel CI'''. | There is one Jenkins master node http://fuel-jenkins.mirantis.com which is connected to Openstack Gerrit via Gerrit Trigger plugin using service account '''Fuel CI'''. | ||
Revision as of 18:33, 5 December 2014
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 http://fuel-jenkins.mirantis.com which is connected to Openstack Gerrit via Gerrit Trigger plugin using service account Fuel CI.
There are several slaves (three at the moment), all running Ubuntu 14.04. They are similar in configuration, though fuel-jenkins2 is slightly slower with disk I/O.
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.
