shaba/ostree
1
0
Fork 0
mirror of https://github.com/ostreedev/ostree.git synced 2024-12-25 01:34:34 +03:00
Code Issues Projects Releases Wiki Activity
661ec2b1a4
ostree/.papr.yml

220 lines
4.4 KiB
YAML
Raw Normal View History

add .redhat-ci.yml and .redhat-ci.Dockerfile Add a YAML file for the new Red Hat CI framework. Rather than re-installing all the build deps everytime, which takes time, I added a Dockerfile that we can wire up to the Docker Hub. For now it lives at `jlebon/ostree-tester:rhci`, but we can move it under the `projectatomic` org (or a new `ostree` org). Closes: #535 Approved by: cgwalters
2016-10-19 19:37:54 +03:00
branches:
- master
- auto
- try
ci: Make all ci tests gating for Homu See the rhci docs. Closes: #617 Approved by: jlebon
2016-12-07 00:29:39 +03:00
required: true
papr: Bump primary to f27 Let's start with just f27-primary for now. Closes: #1350 Approved by: cgwalters
2017-11-27 20:18:19 +03:00
context: f27-primary
ci: Make all ci tests gating for Homu See the rhci docs. Closes: #617 Approved by: jlebon
2016-12-07 00:29:39 +03:00
add .redhat-ci.yml and .redhat-ci.Dockerfile Add a YAML file for the new Red Hat CI framework. Rather than re-installing all the build deps everytime, which takes time, I added a Dockerfile that we can wire up to the Docker Hub. For now it lives at `jlebon/ostree-tester:rhci`, but we can move it under the `projectatomic` org (or a new `ostree` org). Closes: #535 Approved by: cgwalters
2016-10-19 19:37:54 +03:00
container:
papr: Bump primary to f27 Let's start with just f27-primary for now. Closes: #1350 Approved by: cgwalters
2017-11-27 20:18:19 +03:00
image: registry.fedoraproject.org/fedora:27
ci: Combine UBSAN and ASAN by default I only recently realized this was possible. While we're still seeing leaks in the CI environment for some reason, adding ASAN gives us use-after-free detection etc., which is obviously still very useful even if we're not doing leak checking. Closes: #622 Approved by: jlebon
2016-12-08 05:26:43 +03:00
.redhat-ci.yml: use new build key This allows us to more concisely separate building from testing, which in turn gives us a nicer inheritance pattern in our case. See also: https://github.com/jlebon/redhat-ci/issues/11 Closes: #569 Approved by: cgwalters
2016-11-09 05:37:43 +03:00
env:
ci: Enable -Werror=maybe-uninitialized We don't want to inject this warning by default for every build like the other ones in `configure.ac`, since it can be spruriously wrong. But there's no reason not to have a more extended set of warnings for well-known toolchains (e.g. f25). Closes: #943 Approved by: jlebon
2017-06-21 00:19:01 +03:00
# Enable all the sanitizers for this primary build.
# We only use -Werror=maybe-uninitialized here with a "fixed" toolchain
ci: unconditionally turn on -Werror Closes: #971 Approved by: cgwalters
2017-06-28 18:59:36 +03:00
CFLAGS: '-fsanitize=undefined -fsanitize-undefined-trap-on-error -fsanitize=address -O2 -Wp,-D_FORTIFY_SOURCE=2'
ci: Make introspection warnings fatal Closes: #965 Approved by: pwithnall
2017-06-27 01:12:33 +03:00
# Only for CI with a known g-ir-scanner
GI_SCANNERFLAGS: '--warn-error'
ci: Combine UBSAN and ASAN by default I only recently realized this was possible. While we're still seeing leaks in the CI environment for some reason, adding ASAN gives us use-after-free detection etc., which is obviously still very useful even if we're not doing leak checking. Closes: #622 Approved by: jlebon
2016-12-08 05:26:43 +03:00
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"
ci: compile f26/c7-primary with libcurl/openssl This is how ostree is shipped in those distros. We already have alternative testsuites for testing other HTTP & crypto backends. Closes: #1261 Approved by: cgwalters
2017-10-11 17:54:59 +03:00
CONFIGOPTS: '--with-curl --with-openssl'
.redhat-ci.yml: use new build key This allows us to more concisely separate building from testing, which in turn gives us a nicer inheritance pattern in our case. See also: https://github.com/jlebon/redhat-ci/issues/11 Closes: #569 Approved by: cgwalters
2016-11-09 05:37:43 +03:00
add .redhat-ci.yml and .redhat-ci.Dockerfile Add a YAML file for the new Red Hat CI framework. Rather than re-installing all the build deps everytime, which takes time, I added a Dockerfile that we can wire up to the Docker Hub. For now it lives at `jlebon/ostree-tester:rhci`, but we can move it under the `projectatomic` org (or a new `ostree` org). Closes: #535 Approved by: cgwalters
2016-10-19 19:37:54 +03:00
tests:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
- ci/ci-commitmessage-submodules.sh
- ci/build-check.sh
ci: add ci-release-build.sh Add a check that verifies that `is_release_build` is `yes` only for release commits. And also verify that the commit message has the correct version. Closes: #945 Approved by: cgwalters
2017-06-19 18:25:25 +03:00
- ci/ci-release-build.sh
add .redhat-ci.yml and .redhat-ci.Dockerfile Add a YAML file for the new Red Hat CI framework. Rather than re-installing all the build deps everytime, which takes time, I added a Dockerfile that we can wire up to the Docker Hub. For now it lives at `jlebon/ostree-tester:rhci`, but we can move it under the `projectatomic` org (or a new `ostree` org). Closes: #535 Approved by: cgwalters
2016-10-19 19:37:54 +03:00
timeout: 30m
ci: Record primary context results using g-d-t-r --log-directory So the output isn't all intermingled. I just pushed a commit to add `--log-directory`, so we need to build it from git master for now. Closes: #1218 Approved by: jlebon
2017-09-26 21:05:08 +03:00
# Keep this in sync with build-check.sh
add .redhat-ci.yml and .redhat-ci.Dockerfile Add a YAML file for the new Red Hat CI framework. Rather than re-installing all the build deps everytime, which takes time, I added a Dockerfile that we can wire up to the Docker Hub. For now it lives at `jlebon/ostree-tester:rhci`, but we can move it under the `projectatomic` org (or a new `ostree` org). Closes: #535 Approved by: cgwalters
2016-10-19 19:37:54 +03:00
artifacts:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
- test-suite.log
ci: Enable -Werror for clang I hit an unused-variable warning with `GLNX_AUTO_PREFIX_ERROR` for rpm-ostree and led me to wonder why ostree didn't fail, then I noticed we had lost the special `-Werror=unused-variable` bit. Let's go ahead and use `-Werror` for clang too. Closes: #1023 Approved by: jlebon
2017-07-20 22:34:15 +03:00
- config.log
ci: Record primary context results using g-d-t-r --log-directory So the output isn't all intermingled. I just pushed a commit to add `--log-directory`, so we need to build it from git master for now. Closes: #1218 Approved by: jlebon
2017-09-26 21:05:08 +03:00
- gdtr-results
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
---
papr: build and test on c7 Start testing on CentOS 7 as well to cover kernel differences (e.g. O_TMPFILE support). Closes: #968 Approved by: cgwalters
2017-06-27 23:39:27 +03:00
context: c7-primary
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
inherit: true
ci: Add CentOS 7 build For similar reasons as https://github.com/projectatomic/rpm-ostree/pull/824 Closes: #919 Approved by: jlebon
2017-06-09 17:57:40 +03:00
required: true
papr: build and test on c7 Start testing on CentOS 7 as well to cover kernel differences (e.g. O_TMPFILE support). Closes: #968 Approved by: cgwalters
2017-06-27 23:39:27 +03:00
host:
distro: centos/7/atomic
ci: Add CentOS 7 build For similar reasons as https://github.com/projectatomic/rpm-ostree/pull/824 Closes: #919 Approved by: jlebon
2017-06-09 17:57:40 +03:00
env:
CFLAGS: ''
ci: compile f26/c7-primary with libcurl/openssl This is how ostree is shipped in those distros. We already have alternative testsuites for testing other HTTP & crypto backends. Closes: #1261 Approved by: cgwalters
2017-10-11 17:54:59 +03:00
CONFIGOPTS: '--with-curl --with-openssl'
ci: Add CentOS 7 build For similar reasons as https://github.com/projectatomic/rpm-ostree/pull/824 Closes: #919 Approved by: jlebon
2017-06-09 17:57:40 +03:00
tests:
papr: build and test on c7 Start testing on CentOS 7 as well to cover kernel differences (e.g. O_TMPFILE support). Closes: #968 Approved by: cgwalters
2017-06-27 23:39:27 +03:00
- docker run --privileged -v $PWD:$PWD --workdir $PWD
ci: Update centos container to current again Repo sync issue should be cleared now, and for some reason the previous container is already GC'd. Closes: #1304 Approved by: peterbaouoft
2017-10-24 17:27:23 +03:00
registry.centos.org/centos/centos:7 sh -c
papr: build and test on c7 Start testing on CentOS 7 as well to cover kernel differences (e.g. O_TMPFILE support). Closes: #968 Approved by: cgwalters
2017-06-27 23:39:27 +03:00
'yum install -y git && ci/build-check.sh'
ci: Add CentOS 7 build For similar reasons as https://github.com/projectatomic/rpm-ostree/pull/824 Closes: #919 Approved by: jlebon
2017-06-09 17:57:40 +03:00
---
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
context: f27-rust
ci: Add CentOS 7 build For similar reasons as https://github.com/projectatomic/rpm-ostree/pull/824 Closes: #919 Approved by: jlebon
2017-06-09 17:57:40 +03:00
inherit: true
container:
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
image: registry.fedoraproject.org/fedora:27
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
env:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
CONFIGOPTS: '--enable-rust'
ci: Hackaround Fedora rpm/libdb/glibc issue Not sure I want to wait a few days for a new container, so let's give this a shot now. See https://bugzilla.redhat.com/show_bug.cgi?id=1483553 Closes: #1143 Approved by: jlebon
2017-09-06 19:42:51 +03:00
CI_PKGS: cargo
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
tests:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
- ci/build.sh
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
- make check TESTS=tests/test-rollsum
ci: Add unit case for --enable-experimental-api We're starting to get a lot of contexts, and this is likely going to drive some requirements for consolidation and improvements like not testing *every* context on every PR, etc. But for now since experimental is new, and under development, let's test it. Closes: #875 Approved by: cgwalters
2017-05-19 17:39:48 +03:00
---
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
context: f27-gnutls
Add --with-crypto=gnutls Introduce support for GnuTLS for computing cryptograpic hashes, similar to the OpenSSL backend. A reason to do this is some distributors want to avoid GPLv3, and GPG pulls that in. A possible extension of using GnuTLS would be replacing the GPG signing with `PKCS#7` signatures and `X.509` keys. We also support `--with-crypto=openssl`, which has the same effect as `--with-openssl`, and continues to be supported. Changes by Colin Walters <walters@verbum.org>: - Drop libgcrypt option for now - Unify buildsystem on --with-crypto Link: https://mail.gnome.org/archives/ostree-list/2017-June/msg00002.html Signed-off-by: Jussi Laako <jussi.laako@linux.intel.com> Closes: #1189 Approved by: cgwalters
2017-06-13 16:56:21 +03:00
inherit: true
container:
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
image: registry.fedoraproject.org/fedora:27
Add --with-crypto=gnutls Introduce support for GnuTLS for computing cryptograpic hashes, similar to the OpenSSL backend. A reason to do this is some distributors want to avoid GPLv3, and GPG pulls that in. A possible extension of using GnuTLS would be replacing the GPG signing with `PKCS#7` signatures and `X.509` keys. We also support `--with-crypto=openssl`, which has the same effect as `--with-openssl`, and continues to be supported. Changes by Colin Walters <walters@verbum.org>: - Drop libgcrypt option for now - Unify buildsystem on --with-crypto Link: https://mail.gnome.org/archives/ostree-list/2017-June/msg00002.html Signed-off-by: Jussi Laako <jussi.laako@linux.intel.com> Closes: #1189 Approved by: cgwalters
2017-06-13 16:56:21 +03:00
env:
CONFIGOPTS: '--with-crypto=gnutls'
CI_PKGS: pkgconfig(gnutls)
tests:
- ci/build.sh
- make check TESTS=tests/test-basic.sh
---
ci: Add unit case for --enable-experimental-api We're starting to get a lot of contexts, and this is likely going to drive some requirements for consolidation and improvements like not testing *every* context on every PR, etc. But for now since experimental is new, and under development, let's test it. Closes: #875 Approved by: cgwalters
2017-05-19 17:39:48 +03:00
inherit: true
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
context: f27-experimental-api
ci: Add unit case for --enable-experimental-api We're starting to get a lot of contexts, and this is likely going to drive some requirements for consolidation and improvements like not testing *every* context on every PR, etc. But for now since experimental is new, and under development, let's test it. Closes: #875 Approved by: cgwalters
2017-05-19 17:39:48 +03:00
env:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
CONFIGOPTS: '--enable-experimental-api'
ci: Add unit case for --enable-experimental-api We're starting to get a lot of contexts, and this is likely going to drive some requirements for consolidation and improvements like not testing *every* context on every PR, etc. But for now since experimental is new, and under development, let's test it. Closes: #875 Approved by: cgwalters
2017-05-19 17:39:48 +03:00
tests:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
- ci/build-check.sh
ci: Add unit case for --enable-experimental-api We're starting to get a lot of contexts, and this is likely going to drive some requirements for consolidation and improvements like not testing *every* context on every PR, etc. But for now since experimental is new, and under development, let's test it. Closes: #875 Approved by: cgwalters
2017-05-19 17:39:48 +03:00
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
---
ci: Add an "all options disabled" context We keep occasionally regressing this so let's start covering it now. I'm intentionally not running the tests since that would likely entail a lot more conditionalizing pain. Closes: #1194 Approved by: jlebon
2017-09-19 22:19:05 +03:00
inherit: true
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
context: f27-minimal
ci: Add an "all options disabled" context We keep occasionally regressing this so let's start covering it now. I'm intentionally not running the tests since that would likely entail a lot more conditionalizing pain. Closes: #1194 Approved by: jlebon
2017-09-19 22:19:05 +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
---
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
inherit: true
required: true
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
context: f27-libsoup
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
env:
ci: Enable libcurl by default on Fedora The insttest fell over since its build used libsoup, but that just dropped out of FAH. Closes: #1030 Approved by: jlebon
2017-07-26 22:51:57 +03:00
CONFIGOPTS: "--without-curl --without-openssl --with-libsoup"
libcurl backend For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
2016-12-08 05:02:30 +03:00
tests:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
- ci/build-check.sh
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
---
ci/papr: Add a suite to run introspection-based tests without ASAN Unfortunately we can't do gobject-introspection based tests while compiling with `-fsanitize=address`, since it needs to hook `malloc` early on. Add a new suite which just runs the introspection-based tests without ASAN. Closes: #1016 Approved by: jlebon
2017-07-19 16:21:23 +03:00
inherit: true
required: true
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
context: f27-introspection-tests
ci/papr: Add a suite to run introspection-based tests without ASAN Unfortunately we can't do gobject-introspection based tests while compiling with `-fsanitize=address`, since it needs to hook `malloc` early on. Add a new suite which just runs the introspection-based tests without ASAN. Closes: #1016 Approved by: jlebon
2017-07-19 16:21:23 +03:00
env:
# ASAN conflicts with introspection testing;
# See https://github.com/ostreedev/ostree/issues/1014
tests: More fixes for gjs tests Previous to this commit, the gjs tests were installed-only; and our logic for handling the "--enable-installed-tests=exclusive" logic actually also meant they weren't installed. It did work for me locally with `--enable-installed-tests`. However, to make things fully symmetric, let's enable the js tests to also be run under `make check`. Also remove `corrupt-repo-ref.js` from the PAPR invocation since it's not actually a unit test, it's a utility helper. Closes: #1022 Approved by: jlebon
2017-07-20 17:32:44 +03:00
INSTALLED_TESTS_PATTERN: "libostree/test-sizes.js libostree/test-sysroot.js libostree/test-core.js"
ci/papr: Add a suite to run introspection-based tests without ASAN Unfortunately we can't do gobject-introspection based tests while compiling with `-fsanitize=address`, since it needs to hook `malloc` early on. Add a new suite which just runs the introspection-based tests without ASAN. Closes: #1016 Approved by: jlebon
2017-07-19 16:21:23 +03:00
tests:
- ci/build-check.sh
---
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
inherit: false
branches:
- master
- auto
- try
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
context: f27ah-insttest
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
required: false
cluster:
hosts:
- name: vmcheck
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
distro: fedora/27/atomic
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
container:
ci/papr: Update most contexts to f27 Many of them actually already *were* because they were inherting. An exception is flatpak which is being worked on in https://github.com/ostreedev/ostree/pull/1400 Closes: #1426 Approved by: jlebon
2018-01-18 17:01:27 +03:00
image: registry.fedoraproject.org/fedora:27
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
# Copy the build from the container to the host; ideally down the line
# this is installing an RPM via https://github.com/jlebon/redhat-ci/issues/10
tests:
ci: Update to match current rpm-ostree This copies the `ci/` directory from rpm-ostree, with much the same rationale; among other things we don't want to depend on the Docker hub. The specific reason I'm doing this is that I want to add a CentOS7 build, but that means we can't use `projectatomic/ostree-tester`, and at that point we might as well unwind it all. Closes: #917 Approved by: jlebon
2017-06-08 20:47:20 +03:00
- ci/build.sh
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
- make install DESTDIR=$(pwd)/insttree
ci/papr: Update to F26 In particular F25AH will stop getting updates. Closes: #1012 Approved by: jlebon
2017-07-18 12:59:04 +03:00
- yum -y install rsync
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
- rsync -rl -e 'ssh -o User=root' . vmcheck:ostree/
tests,ci: Move "test-basic" (bare mode) to installed test Our CI uses default Docker, which has SELinux labeling but is rather evil in returning `EOPNOTSUPP` to any attempts to set `security.selinux`, even if to the same value. The previous fire 🔥 for this was: https://github.com/ostreedev/ostree/pull/759 The `bare` repo mode really only makes sense as uid 0, so our installed test framework is a good match for this. However, the unit tests *do* work in a privileged container even as non-root, and *also* should work on SELinux-disabled systems. So let's teach the test framework how to skip in those situations. I tested this both in a priv container (my default builder) and an unpriv container (like our CI). At the same time, start executing the `test-basic.sh` from an installed test, so we get better coverage than before. This is just the start - all of the sysroot tests really need the same treatment. Closes: #1217 Approved by: jlebon
2017-09-26 19:41:07 +03:00
- ssh root@vmcheck './ostree/tests/installed/fah-prep.sh && ./ostree/tests/installed/run.sh'
tests/installed: New installed, privileged tests using Fedora AH Our container-driven tests can't e.g. test SELinux sanely, and have to support being run as root *and* non-root too. Use redhat-ci to provision a VM and run tests directly there. These are installed tests too. Closes: https://github.com/ostreedev/ostree/issues/806 Closes: #807 Approved by: jlebon
2017-04-24 21:40:06 +03:00
ci: Add a context for testing flatpak This was part of the philosophy behind https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests - libraries like libostree don't need to replicate everything in unit tests, we can use the tests from our dependencies directly too. We'll also get API break coverage testing too. Closes: #818 Approved by: jlebon
2017-04-28 16:32:35 +03:00
---
inherit: false
branches:
- master
- auto
- try
ci/papr: Update to F26 In particular F25AH will stop getting updates. Closes: #1012 Approved by: jlebon
2017-07-18 12:59:04 +03:00
context: f26-flatpak
ci: Add a context for testing flatpak This was part of the philosophy behind https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests - libraries like libostree don't need to replicate everything in unit tests, we can use the tests from our dependencies directly too. We'll also get API break coverage testing too. Closes: #818 Approved by: jlebon
2017-04-28 16:32:35 +03:00
required: false
# This test case wants an "unprivileged container with bubblewrap",
# which we don't have right now; so just provision a VM and do a
# docker --privileged run.
host:
ci/papr: Update to F26 In particular F25AH will stop getting updates. Closes: #1012 Approved by: jlebon
2017-07-18 12:59:04 +03:00
distro: fedora/26/atomic
ci: More flatpak ci fixes We need our `make install` to override the ostree RPM, so do it all in one txn. This sort of thing is where a more rigorous model like rdgo/gcontinuous use becomes better, but we'll hack it with shell for now. Closes: #824 Approved by: jlebon
2017-05-02 01:02:27 +03:00
specs:
ram: 4096 # build-bundle is a static delta, which needs RAM right now
ci: Add a context for testing flatpak This was part of the philosophy behind https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests - libraries like libostree don't need to replicate everything in unit tests, we can use the tests from our dependencies directly too. We'll also get API break coverage testing too. Closes: #818 Approved by: jlebon
2017-04-28 16:32:35 +03:00
tests:
ci/papr: Update to F26 In particular F25AH will stop getting updates. Closes: #1012 Approved by: jlebon
2017-07-18 12:59:04 +03:00
- docker run --rm --privileged -v $(pwd):/srv/code registry.fedoraproject.org/fedora:26 /bin/sh -c "cd /srv/code && ./ci/flatpak.sh"
ci: Add a context for testing flatpak This was part of the philosophy behind https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests - libraries like libostree don't need to replicate everything in unit tests, we can use the tests from our dependencies directly too. We'll also get API break coverage testing too. Closes: #818 Approved by: jlebon
2017-04-28 16:32:35 +03:00
artifacts:
- test-suite.log
ci: Run a subset ⊂ of rpm-ostree's tests This is a quick hack to get us more than unit testing, albeit indirectly. See: https://github.com/projectatomic/rpm-ostree/issues/662 Closes: #771 Approved by: jlebon
2018-01-09 21:20:24 +03:00
---
# Run rpm-ostree's vmcheck. This is a temporary hack until
# we share more code. https://github.com/projectatomic/rpm-ostree/issues/662
inherit: false
branches:
- master
- auto
- try
context: f27-rpmostree
required: true
cluster:
hosts:
- name: vmcheck
distro: fedora/27/atomic
container:
image: registry.fedoraproject.org/fedora:27
env:
HOSTS: vmcheck
# This should roughly match the Fedora spec file, although right now we don't
# explicitly enable gtk-doc because we don't really need it
CONFIGOPTS: '--with-selinux --with-dracut=yesbutnoconf --with-curl --with-openssl'
tests:
- ./ci/rpmostree.sh
artifacts:
- test-suite.log
- vmcheck
timeout: 60m
Reference in New Issue Copy Permalink