owned this note changed 3 years ago
Published Linked with GitHub

RIOT CI Infrastructure Maintainer Overview

This page tries to give an overview about the components of RIOT's CI infra, and who's in charge. This collects physical access to hardware / administration, not the underlying software.

Murdock -> RIOT's compilation testing

  • Contact: Kaspar
  • Components:
    • ci.riot-os.org (head node, Web UI) -> Admins: Cenk, Kevin
    • worker nodes:
      • breeze (Admin: Kaspar)
      • haw-icc (Admins: Cenk, Kevin)
      • mobi* (Admins: Cenk, Kevin)
      • riotbuild (Admin: Alex)
    • pifleet (Admin: Kaspar)
      • pihub (main node, provides configuration with salt-stack)
      • worker nodes

HIL -> peripheral Hardware in the Loop testing

Circle CI -> documentation build and provisioning

  • Contact: Alex

Github Actions

  • Contact: Alex & Martine
  • Actions:
    • static-tests: runs make static-tests and annotates PR with the results
      • triggers:
        • On PR (default triggers)
        • On push to master branch
        • On release (candidate) tag creation
    • tools-buildtest: compile tests fixed selection of tooling (see list of steps for which tools are tested)
      • triggers
        • On PR (default triggers)
        • On push to master branch
        • On tag creation
    • tools-test: runs tests on tooling (see list of steps for which tools are tested)
      • triggers
        • On PR (default triggers)
        • On push to master branch
        • On tag creation
    • check-pr: sanity check for Pull Requests:
      • check blocking labels
      • check if labels request more reviews than 1
      • check for fixup commits
      • check commit message length
      • triggers:
        • On PR label change, open, reopen, or synchronize
        • On PR review submission or dismissal
    • circleci: post-action to Circle CI, creates link to index.html in checks box
    • release-test: automatically runs release spec tests
      • triggers:
        • Weekly run (Sat 3:00)
        • On release (candidate) tag creation
        • Manual trigger
    • test-on-iotlab: runs compile_and_test_for_board.py on a selection of FIT IoT-LAB nodes (job names map to RIOT board names)
      • triggers:
        • Weekly run (Sun 1:00)
        • On release (candidate) tag creation
        • Manual trigger
Select a repo