update-generated-files/Justfile

# Build the container image from current sources
build *ARGS:
    podman build --jobs=4 -t localhost/bootc {{ARGS}} .

# This container image has additional testing content and utilities
build-integration-test-image *ARGS: build
    podman build --jobs=4 -t localhost/bootc-integration -f hack/Containerfile {{ARGS}} .

# Run container integration tests
run-container-integration: build-integration-test-image
    podman run --rm localhost/bootc-integration bootc-integration-tests container

unittest *ARGS:
    podman build --jobs=4 --target units -t localhost/bootc-units --build-arg=unitargs={{ARGS}} .
build-sys: Rework to have toplevel Dockerfile + Justfile This is aligning with what I did in https://github.com/ostreedev/ostree/pull/3439 - What gets invoked in e.g. GHA should ideally most be `just` commands that are easy to run locally too (with sudo in GHA, without sudo locally) - Move the "core build" to the toplevel so that one can just `podman build` directly too (without the Justfile) and have it do something useful - The "always build and test in a container" helps for LLM-assisted coding because what they can do is inherently sandboxed Signed-off-by: Colin Walters <walters@verbum.org> 2025-06-06 11:11:58 -04:00			`# Build the container image from current sources`
			`build *ARGS:`
			`podman build --jobs=4 -t localhost/bootc {{ARGS}} .`

			`# This container image has additional testing content and utilities`
			`build-integration-test-image *ARGS: build`
			`podman build --jobs=4 -t localhost/bootc-integration -f hack/Containerfile {{ARGS}} .`

			`# Run container integration tests`
			`run-container-integration: build-integration-test-image`
			`podman run --rm localhost/bootc-integration bootc-integration-tests container`

			`unittest *ARGS:`
			`podman build --jobs=4 --target units -t localhost/bootc-units --build-arg=unitargs={{ARGS}} .`