Workflow - duonl/bcld GitHub Wiki

Since the BCLD Client is built with GitHub Actions, a GitHub workflow directory is available. This directory contains our GitHub Workflow files, and establishes four different workflow runs:

1. unit-test
2. regression-test
3. release
4. extra (r8168)

GitHub Actions

unit-test

This workflow triggers on every change to a develop child branch. Since all development happens in this branch, all changes are tested immediately. which means that these branches are reserved for issues that are currently under development. These changes mostly involve feature requests and hotfixes, but will sometimes include minor kernel patches, major kernel updates or even complete repository upgrades.

regression-test

All changes from child branches are collected in the ALPHA branch, before running multiple tests. If successful, the aggregated changes will be pushed to the main branch for a new release.

release

All changes to the main branch trigger a release build. The main branch will periodically be merged to develop/BETA to test merges, create experimental images, or simply back up main prior to large merges.

extra (r8168)

Everytime the release workflow is triggered, another extra (r8168) triggers, which includes a r8168-dkms package. This package supports newer hardware with a dynamic kernel module, which is not signed for Secure Boot. In many cases, support for newer hardware is added to the kernel over time. This image bridges that gap, but at the cost of Secure Boot.