shaba/ostree
1
0
Fork 0
mirror of https://github.com/ostreedev/ostree.git synced 2025-01-05 13:18:17 +03:00
Code Issues Projects Releases Wiki Activity
f2e71c60ec
ostree/.papr-ex.yaml

121 lines
2.4 KiB
YAML
Raw Normal View History

ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
# https://fedoraproject.org/wiki/CI/Tests
branches:
- master
- auto
- try
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
context: FAH28-insttests
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
required: true
container:
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
image: registry.fedoraproject.org/fedora:28
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
kvm: true
tests:
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
- ci/fah28-insttests.sh
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
artifacts:
- tests/installed/artifacts/
---
# This suite skips the RPMs and does the build+unit tests in a container
inherit: false
branches:
- master
- auto
- try
required: true
container:
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
image: registry.fedoraproject.org/fedora:28
context: f28-primary
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
env:
# We only use -Werror=maybe-uninitialized here with a "fixed" toolchain
CFLAGS: '-fsanitize=undefined -fsanitize-undefined-trap-on-error -fsanitize=address -O2 -Wp,-D_FORTIFY_SOURCE=2'
# Only for CI with a known g-ir-scanner
GI_SCANNERFLAGS: '--warn-error'
ASAN_OPTIONS: 'detect_leaks=0' # Right now we're not fully clean, but this gets us use-after-free etc
# TODO when we're doing leak checks: G_SLICE: "always-malloc"
CONFIGOPTS: '--with-curl --with-openssl'
tests:
- ci/ci-commitmessage-submodules.sh
- ci/build-check.sh
- ci/ci-release-build.sh
artifacts:
- test-suite.log
- config.log
- gdtr-results
---
# And now the contexts below here are variant container builds
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
context: f28-rust
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
inherit: true
container:
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
image: registry.fedoraproject.org/fedora:28
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
env:
CONFIGOPTS: '--enable-rust'
CI_PKGS: cargo
tests:
- ci/build.sh
- make check TESTS=tests/test-rollsum
---
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
context: f28-gnutls
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
inherit: true
container:
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
image: registry.fedoraproject.org/fedora:28
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
env:
CONFIGOPTS: '--with-crypto=gnutls'
CI_PKGS: pkgconfig(gnutls)
tests:
- ci/build.sh
- make check TESTS=tests/test-basic.sh
---
inherit: true
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
context: f28-minimal
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
env:
CONFIGOPTS: '--without-curl --without-soup --disable-gtk-doc --disable-man
--disable-rust --without-libarchive --without-selinux --without-smack
--without-openssl --without-avahi --without-libmount --disable-rofiles-fuse
--disable-experimental-api'
tests:
- ci/build.sh
---
inherit: true
required: true
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
context: f28-libsoup
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
env:
ci: exclude 'lib' from libsoup configure option The option used by configure script is actually --with-soup/--without-soup. Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com> Closes: #1661 Approved by: jlebon
2018-06-29 11:16:41 +03:00
CONFIGOPTS: "--without-curl --without-openssl --with-soup"
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
tests:
- ci/build-check.sh
---
inherit: true
required: true
ci: Bump to f28, except flatpak We successfully switched to F28 in rpm-ostree. Time to follow suit here. We exclude flatpak for now since we're still hitting test issues there on F28. Closes: #1601 Approved by: cgwalters
2018-05-28 22:21:19 +03:00
context: f28-introspection-tests
ci: Add .papr-ex.yaml I'd like to start working towards migrating the OSTree CI towards the new PAPR model running in PACI. In order to take it for a test drive (pun intended) without yet replacing our current CI, the new PAPR now knows to look for a `.papr-ex.yaml` file. So as to not conflict with the current PAPR, no GitHub statuses will be output other than a `required-ex` label, which plays the same role as `required`. For more information, see: https://github.com/projectatomic/papr/commit/85b1d0a91eba6597d01b52b674de38a876f030fe The `.papr-ex.yaml` version is essentially the same except for: 1. the `FAH27-insttests` suite runs directly in the scheduled container (notice the new `kvm: true` key) 2. the `host:` based contexts (rpm-ostree and flatpak) are missing since we don't support provisioning a host just yet Keeping them in sync could get annoying, though building confidence in the new approach will allow us to migrate faster. Closes: #1587 Approved by: cgwalters
2018-05-11 22:03:58 +03:00
env:
# ASAN conflicts with introspection testing;
# See https://github.com/ostreedev/ostree/issues/1014
INSTALLED_TESTS_PATTERN: "libostree/test-sizes.js libostree/test-sysroot.js libostree/test-core.js"
tests:
- ci/build-check.sh
Reference in New Issue Copy Permalink