Skip to content

Continuous Integration

Jump to bottom
Amy Buck edited this page Jan 24, 2018 · 15 revisions

NOTE: CI and CD for OpenSwitch are in a state of continuous improvement. As more processes are automated, this content will expand.

The CI process starts when a code review is opened by a developer.

  • Developer opens review or updates and existing review
  • Zuul CI runs check job — Zuul CI adds Verified +1 tag to review (on success)
  • Zuul CI waits until review has three labels:
    • Verified +1
    • Code-Review +2
    • Workflow +1
  • Zuul CI runs gate job — Zuul CI adds Verified +2 tag to review (on success)
  • Zuul CI waits until review has three labels:
    • Verified +2
    • Code-Review +2
    • Workflow +1
  • Zuul CI submits review to the master branch of the repository

NOTE: The check/gate jobs vary per repository. What follows is an overview (See infra/project-config for more details).

Debian package repositories

  • Check job — build package and run smoketest
  • Gate job — build package and run smoketest

Other repositories

  • opx-build
    • Check job — build all packages and run smoketest
    • Gate job — build all packages and run smoketest
  • opx-test
    • Check job — run smoketest
    • Gate job — run smoketest

© 2019 OpenSwitch project. All information is contributed to and made available by OPX under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/).

Clone this wiki locally