Skip to content

Now exits with 1 when a build produced no packages - #2424

Merged
larsewi merged 1 commit into
cfengine:masterfrom
larsewi:build-in-container-exit-code
Aug 12, 2026
Merged

Now exits with 1 when a build produced no packages#2424
larsewi merged 1 commit into
cfengine:masterfrom
larsewi:build-in-container-exit-code

Conversation

@larsewi

@larsewi larsewi commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

The container exiting zero was taken as success, even with an empty output directory. A build that produces nothing has failed, and a caller checking only the exit code had no way to tell.

A failing container already exited non-zero. This covers the case where it claims success but leaves nothing behind.

Signed-off-by: Lars Erik Wik lars.erik.wik@northern.tech

The container exiting zero was taken as success, even with an empty
output directory. A build that produces nothing has failed, and a caller
checking only the exit code had no way to tell.

A failing container already exited non-zero. This covers the case where
it claims success but leaves nothing behind.

Signed-off-by: Lars Erik Wik <lars.erik.wik@northern.tech>
@larsewi
larsewi merged commit fcf7486 into cfengine:master Aug 12, 2026
1 check passed
@larsewi
larsewi deleted the build-in-container-exit-code branch August 12, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants