build-linux-factory

Github action for Clay Risser's linux factory framework. The current version is v1.

Example Usage

build-linux-factory/.github/workflows/test-clayrisser-linux-factory.yml

Lines 9 to 38 in fbb4b2b

	jobs:
	build:
	runs-on: ubuntu-latest
	steps:
	- name: Maximize build space
	uses: AdityaGarg8/remove-unwanted-software@v2
	with:
	remove-android: 'true'
	remove-codeql: 'true'
	- uses: actions/checkout@v3
	with:
	repository: 'clayrisser/linux-factory'
	path: linux-factory
	lfs: true
	- name: Cleanup and check broken example overlays
	run: |
	rm -r $GITHUB_WORKSPACE/linux-factory/overlays/example
	ls $GITHUB_WORKSPACE/linux-factory/overlays
	- name: Build Linux Factory
	uses: cnshing/build-linux-factory@v1
	with:
	path: linux-factory
	- uses: actions/upload-artifact@v3
	with:
	name: clayrisser-iso
	path: ${{ github.workspace }}/linux-factory/.build/lb/*.iso

Description

Builds an image from a linux factory

Inputs

name	description	required	default
path	Path of the linux factory under $GITHUBWORKSPACE. If no path is supplied, $GITHUBWORKSPACE will act as the working build directory.	false	""

Runs

This action is a composite action.

BTS

Any dependencies required for Linux Factory are installed via action.yml and subsequently used to build the image. You may run this action on any runner VM, provided the Linux Factory dependencies and debian-archive-keyring are installable via APT. This action will also attempt to install live-build from the current Debian stable repository for compatibility purposes.

Some of the workflow files are "dummy" files like test-clayrisser-linux-factory.yml, where the source workflow code don't appear to do anything in the main/release branch but are instead located in a seperate testing branch.