Idempotent builds of edge commits

Posted on

Despite introducing no changes to the blueprint file, each new commit build triggered with composer-cli still produces a new commit with changes to the files listed below and potentially other files too.

Is there a way to make the build idempotent and avoid a new commit on every build? I am already pointing composer-cli to the previous edge commit like so:

sudo composer-cli compose start-ostree <blueprint name> edge-commit --url <server url> --ref <ref>

/usr/etc/pki/ca-trust/extracted/java/cacerts
/usr/etc/shadow
/usr/lib/fontconfig/cache/
/usr/lib/sysimage/rpm-ostree-base-db/rpmdb.sqlite
/usr/share/rpm/rpmdb.sqlite
JJ

Responses