mirror of https://github.com/Start9Labs/start-os.git synced 2026-03-26 10:21:52 +00:00

Files

Aiden McClelland c728f1a694 restructure initialization (#1816 )

* reorder enabling of systemd-resolved

* set dns at end

* don't disable interfaces

* let networkmanager manage ifupdown

* restructure initialization

* use pigz when available

* cleanup

* fetch key before adding registry

* fix build

* update patch-db

* fix build

* fix build

* wait for network reinit

* add dynamic wait for up to 60s for network to reinit

2022-09-22 11:40:36 -06:00

backend.yaml

0.3.2 final cleanup (#1782 )

2022-09-08 16:14:42 -06:00

frontend.yaml

Set pipeline job timeouts and add ca-certificates to test container (#1753 )

2022-08-22 13:43:29 -06:00

product.yaml

restructure initialization (#1816 )

2022-09-22 11:40:36 -06:00

README.md

add x86 build and run unittests to backend pipeline (#1682 )

2022-08-18 10:24:17 -06:00

README.md

This folder contains GitHub Actions workflows for building the project

backend

Runs: manually (on: workflow_dispatch) or called by product-pipeline (on: workflow_call)

This workflow uses the actions and docker/setup-buildx-action@v1 to prepare the environment for aarch64 cross complilation using docker buildx. When execution of aarch64 containers is required the action docker/setup-qemu-action@v1 is added. A matrix-strategy has been used to build for both x86_64 and aarch64 platforms in parallel.

Running unittests

Unittests are run using cargo-nextest. First the sources are (cross-)compiled and archived. The archive is then run on the correct platform.

frontend

Runs: manually (on: workflow_dispatch) or called by product-pipeline (on: workflow_call)

This workflow builds the frontends.

product

Runs: when a pull request targets the master or next branch and when a change to the master or next branch is made

This workflow builds everything, re-using the backend and frontend workflows. The download and extraction order of artifacts is relevant to make, as it checks the file timestamps to decide which targets need to be executed.

Result: eos.img

a note on uploading artifacts

Artifacts are used to share data between jobs. File permissions are not maintained during artifact upload. Where file permissions are relevant, the workaround using tar has been used. See (here)[https://github.com/actions/upload-artifact#maintaining-file-permissions-and-case-sensitive-files].