| Age | Commit message (Collapse) | Author |
|
|
|
|
|
This should improve the experience by having separate clickable
links for each test matrix item and see the pass/fail more early.
Also make Testing Farm scale better as it uses separate TF requests
for testing.
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
|
|
This is not exhaustive, but does get users into the right environment
to build images. We also indicate that this is only tested on Fedora Linux.
|
|
In preparation for having multiple top-level kiwi description files,
expose the ability to define which file to read.
Additionally, tests are updated to use this new flag.
|
|
|
|
As the list of buildable variants grows, it will be harder to maintain
in the main README. Thus, split it out to its own file to keep the
README manageable.
|
|
This adds the definitions for building the container tarballs for
the base container, the minimal base container, and the toolbox
container.
|
|
We now have more than one cloud system that is essentially a KVM
environment that uses cloud-init to boot, so now we declare that
"generic" and have the OpenStack and Oracle images reuse those
definitions.
Also, in preparation for layered cloud image variants, rename
them from "Cloud-" to "Cloud-Base-". Vagrant variants are
similarly prefixed to make it clear who provides them.
Finally, restructure the layout of the tmt plans to match the
description structure.
|
|
|
|
This allows us to have pull requests tested before we review changes
to merge.
|
|
Oracle Cloud images are KVM cloud images, just like the OpenStack
images. Reuse the OpenStack image definition for Oracle Cloud.
|
|
KIWI differentiates between libvirt and VirtualBox based Vagrant
images, especially for the box format, so now we split up the
Vagrant definition accordingly.
|
|
|
|
|
|
|