aboutsummaryrefslogtreecommitdiff
path: root/examples
diff options
context:
space:
mode:
authorDaniel P. Berrangé <berrange@redhat.com>2024-04-29 11:22:37 +0100
committerDaniel P. Berrangé <berrange@redhat.com>2024-04-29 11:26:01 +0100
commit6f92e2d61d33dbca3b63921341309502be6a0bcd (patch)
tree19c13fc28e5dda089c2d4d22a7f0e1d4777ab201 /examples
parent639527898b85d33bb7721052b20f17b0faa762fe (diff)
downloadlibvirt-ci-6f92e2d61d33dbca3b63921341309502be6a0bcd.zip
libvirt-ci-6f92e2d61d33dbca3b63921341309502be6a0bcd.tar.gz
libvirt-ci-6f92e2d61d33dbca3b63921341309502be6a0bcd.tar.bz2
lcitool: default unreleased distros to 'allow-failure: true'
In recent times we have increasingly been marking the unreleased distros (rawhide, tumbleweed, sid, etc) as 'allow-failure: true' in many projects. This reflects the fact that they all suffer from periods in time when packages are not reliably installable, or those that are installed are broken in some way. Rather than continue to mark individual projects, this adds an 'stable: true|false' field in the target yaml files, with all the unreleased distros being marked 'stable: false'. Any target with 'stable: false' will get 'allow-failure: true' set by default. The project's manifest.yml file can still override this setting it back to 'allow-failure: false', if a project really wants to treat an unreleased target as gating, though this is not recommended. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions