https://ci.centos.org/view/Atomic/job/fahc-treecompose/14027/console

13:53:27 + sudo docker run --user root:root --rm --entrypoint '' --privileged -v /home/builder/fedora-atomic-host-continuous:/srv/src -v /home/builder/jobs/fahc-treecompose:/srv/tmp -v /home/builder:/srv/home -v /home/builder/jobs/fahc-treecompose:/srv/build -w /srv/build quay.io/cgwalters/coreos-assembler coreos-assembler --ex-jigdo-output-set /srv/build/jigdo --cachedir=/srv/build/cache --touch-if-changed=/srv/tmp/changed.stamp --repo=/srv/build/repo-build --add-metadata-string=rpmostree.gitrepo0=https://pagure.io/fedora-atomic --add-metadata-string=rpmostree.gitrev0=0038c3d8c665b879eb9e05de9f3bf24b6f828f15 --add-metadata-string=rpmostree.gitrepo1=https://pagure.io/fedora-atomic-host-continuous --add-metadata-string=rpmostree.gitrev1=ab0ceda /srv/home/fedora-atomic/fedora-atomic-host.yaml
13:53:27 Unknown command: --ex-jigdo-output-set

Hmm, see latest two commits on https://pagure.io/fedora-atomic-host-continuous/commits/master - they fixed this for the rdgo task, strange it's not working for treecompose.

The Unknown command: is coming from coreos-assembler, right? We're doing run_assembler coreos-assembler --ex-jigdo-output-set, so it tried to lookup that command. I guess with the entrypoint fix, we could change this to run rpm-ostree directly. Though either way, we should freeze on :alpha for now. I submitted a follow-up here for the other instance that actually affects treecompose: https://pagure.io/fedora-atomic-host-continuous/pull-request/26