Jump to: navigation, search

ThirdPartySystems/Quobyte CI

< ThirdPartySystems
Revision as of 08:33, 5 May 2017 by Kaisers (talk | contribs) (Updated overall CI status)
3rd party system: Quobyte CI
Gerrit Account: quobyteci
Contact Information: primary contact: silvan@quobyte.com (kaisers@IRC); backup contacts (in order): robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com,
Intent: Test Cinder, OS-Brick, Manila, and Nova changes against Quobyte drivers
Structure: ansible installed sos-ci setup with some modifications
Method: sos-ci monitors Gerrit event stream and triggers test builds, ansible based installation in DevStack instances, running volume related tempest tests vs. Cinder, OS-Brick, and Nova changes. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup.
OpenStack Programs: Cinder, OS-Brick, Manila, and Nova
Current Status: enabled

Status Details

Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)

Bugs/changes affecting the Cinder CI results:

Bugs/changes affecting the OS-Brick CI results:

Bugs/changes affecting the Nova CI results:

Bugs/changes affecting the Manila CI results:

  • Manila CI runs all basic tests as well as some optional tempest test groups:
    • run_quota_tests=True
    • run_extend_tests=True
    • run_shrink_tests=True
  • Manila CI is currently hit by an unknown DevStack setup issue, we're analyzing this...

Rechecking Quobyte CI Systems

Quobyte CI systems trigger rechecks in two scenarios:

  • Jenkins recheck: Every time Jenkins comments +1 on a change the corresponding Quobyte CI is triggered. This includes initial check runs as well as recheck triggered Jenkins re-runs
  • CI specific recheck (see below)

Quobyte CI Specific Rechecks

All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question.

Recheck trigger: "run <ci-instance-name>"

For example:

run cinder-quobyteci-dsvm-volume

This command works even if there's no previous report from the given CI instance for the given patch set.