[openstack-dev] [fuel] State of the Fuel gates: liftoff!
dborodaenko at mirantis.com
Fri Oct 23 00:25:05 UTC 2015
Back in July, I proposed a plan to implement PTI in Fuel  during Fuel
8.0 development cycle, with the following mandatory stages:
Stage 1: Create non-voting gate jobs for a single Fuel repo.
Stage 2: Get these gate jobs to pass and make them voting.
Stage 3: Create non-voting gate jobs for all Fuel repos.
Stage 4: Cover all Fuel repos with voting unit test gate jobs.
and bonus stages:
Stage 5: Add functional tests for Fuel UI and Fuel Library to the gates.
Stage 6: Run fuel-qa (multi-node deployment) tests on OpenStack Infra.
With the Kilo based Fuel 7.0 released in September, we were finally able
to make some solid progress on that. Of 21 non-plugin Fuel repositories
on review.openstack.org, 12 (including one of our two largest core
components: fuel-web) already have voting gate jobs, 3 more (including
the other largest core component: fuel-library) have passing gate jobs
that can become voting once all outstanding fixes are merged, and 3 more
are a work in progress.
- fuel-ostf (pep8; python gates are waiting for images with gevent)
Ready to vote:
- fuel-library (needs https://review.openstack.org/238628)
Work in progress:
- fuel-astute (has unit tests, needs a gate job)
- fuel-docs (docs gate job is failing)
- network-checker (unit test gate job is failing)
Not covered by unit tests:
- fuel-main (scripts to make Fuel ISO)
- fuel-nailgun-agent (588 lines of Ruby)
- fuel-qa (Fuel deployment system tests)
While it might be a bit too early to pull out a "Mission Accomplished"
banner, it's safe to say that vast majority of Fuel code is now covered
by gate checks running unit tests and syntax checks on OpenStack CI.
Nice work Alexey, Alex, Alexander, Sebastian, Vladimir, and Vladimir!
Many thanks to the OpenStack Infra team for encouraging and supporting
More information about the OpenStack-dev