AMIs for Test Day?

Thu Nov 20 02:31:02 UTC 2014

On Wed, Nov 19, 2014, at 04:16 PM, Matthew Miller wrote:
> On Wed, Nov 19, 2014 at 03:16:19PM -0500, Colin Walters wrote:
> > I tested this one, it boots.  However, I screwed up with:
> > https://git.fedorahosted.org/cgit/fedora-atomic.git/commit/?h=f21&id=70c9fbf49d85d183405b7e39753a79e1797dc0ac
> > Fixed by:
> > https://git.fedorahosted.org/cgit/fedora-atomic.git/commit/?h=f21&id=5d545a55223e024db28d393e678862d3753a2c6d
> > Basically that AMI is OK, but the next one will be broken unless it picks up the latest commit there.
> 
> Currently, what causes a compose to pick up a given commit?

In Fedora there are two codebases going on:

Fedora releng:
https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi#n34
As you can see, this one just does a git clone, it's run "nightly".

A fedmsg driven one:
https://github.com/fedora-infra/fedmsg-atomic-composer
Deployed by: https://github.com/fedora-infra/fedmsg-atomic-composer/blob/master/ansible/playbook.yml