summaryrefslogtreecommitdiff
path: root/ci
Commit message (Collapse)AuthorAgeFilesLines
* ci: Require `libcap2-bin` for `capsh`Colin Walters2021-11-091-0/+1
| | | | | This was previously pulled in indirectly, but it looks like we need to require it explicitly in newer Ubuntu.
* ci: Enable -fanalyzerColin Walters2021-10-151-1/+1
| | | | | | | | | Followup to https://github.com/ostreedev/ostree/pull/2463 One thing I noticed here is we lost usage of `build-check.sh` which also invokes `clang`, which doesn't speak `-fanalyzer` and would be broken by this if we try to enable `build-check.sh` again. But that can come later.
* Attempt to update packit flow to build in COPRColin Walters2021-10-141-17/+9
| | | | | No idea if this will really work, but at least `packit srpm` does work now.
* tests: Unset SOURCE_DATE_EPOCHSimon McVittie2021-07-261-0/+5
| | | | | | | | | | | | | Some distributions set this during build in order to have reproducible builds from the same source code: for example, Debian uses the date from debian/changelog. However, some of our tests assume that `ostree commit` will result in a commit with the current date/time, and SOURCE_DATE_EPOCH breaks that assumption. Unset it for our build-time tests. Resolves: https://github.com/ostreedev/ostree/issues/2405 Signed-off-by: Simon McVittie <smcv@collabora.com>
* ci/release-build: evaluate package_version from m4 definitionLuca BRUNO2021-07-091-3/+15
| | | | | | This fixes the ci-release-build.sh script to directly source and evaluate 'package_version' from its m4 definition, without requiring a fully configured source tree.
* ci: Update Debian and Ubuntu build dependenciesDan Nicholson2021-06-211-36/+91
| | | | | | | This refreshes the build dependencies installed for the GitHub Tests workflow based on the Build-Depends in the upstream packaging. The handling is now more explicit about any deviations and any release differences.
* ci: Drop special handling of test-suite.logDan Nicholson2021-06-211-14/+5
| | | | | | | | The automake test harness[1] already dumps the contents of `test-suite.log` when `VERBOSE=1` is set, so we don't need to add special handling for it. 1. https://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html
* ci: So long, Travis CIDan Nicholson2021-06-183-261/+0
| | | | | | travis-ci.org stopped running builds on June 15, 2021. Since this organization is very unlikely to switch to travis-ci.com, just drop the setup. The new GitHub Actions tests completely replace it.
* ci: Add GitHub Actions workflow for test suiteDan Nicholson2021-06-182-0/+146
| | | | | | | | | | | | | | | | | | | | | | | | | | | This runs the test suite in various distros. The intention is to use this to replace the Travis CI setup since it often has rate limit failures. Each configuration in the matrix runs in a Docker container, installs system dependencies and then builds and tests ostree. The scripts are basically copy and paste of the travis ones with some of the lesser used features pruned out. Some differences from the travis setup: * OS details are gathered from `/etc/os-release` instead of being passed in as environment variables. * The scripts always assume the user is root and don't try to use `sudo`. * The `installcheck` test has been removed since ostree doesn't actually use that. It could be added to run the installed tests or `gnome-desktop-testing-runner` could just be called directly. There should be enough flexibility to run other distros like Fedora, Arch or Alpine. Another option would be to use the other build scripts in ci/.
* *: rename master branch to mainTimothée Ravier2021-05-071-1/+1
|
* travis: Don't ask any debconf questions when installing packagesDan Nicholson2021-04-081-0/+4
| | | | | | | | | Currently the Ubuntu builds are stuck waiting for an answer on what timezone to use. That could be fixed, but generally the way to do these types of installs is to set the DEBIAN_FRONTEND environment variable to `noninteractive` so that debconf just chooses a default. This is what debootstrap does, for instance. I tested installing tzdata on a local focal container this way and it just chooses `Etc/UTC` as the timezone.
* installdeps: Drop PyYAMLColin Walters2021-03-311-1/+1
| | | | Doesn't exist anymore in f33 and we don't depend on python2 anymore.
* Add --enable-sanitizers, fix `make check` with itColin Walters2021-02-031-2/+1
| | | | | | | | It's cleaner if this is an build option rather than being kludged into the CI layer. Notably we can't use `LD_PRELOAD` anymore with ASAN, so update our tests to check for `ASAN_OPTIONS`.
* ci: Add new build-check-sanitized.shColin Walters2021-02-021-0/+12
| | | | | | All C/C++ projects should use the sanitizers (and static analysis) in their CI. We had this but lost it in one of our CI shuffles; let's readd it.
* ci: Don't install deps if running as non-rootColin Walters2021-02-021-1/+1
| | | | This way we run in Prow too.
* ci: run ci-release-build.sh on GitHubLuca BRUNO2020-11-161-1/+2
| | | | | This adds a GitHub action in order to run ci-release-build.sh on release PRs (detected via the `kind/release` label).
* travis: Add a 32 bit buildColin Walters2020-10-151-4/+4
| | | | | In the past we've had 32 bit bugs that were caught by the compiler, let's add this to Travis.
* ci: Barf on unset umaskColin Walters2020-08-051-0/+5
| | | | | Since it's just not a sane thing to do and will cause various failures in our test suite.
* ci: Constrain parallel build jobsJonathan Lebon2020-07-161-1/+1
| | | | | | | | | | | | The default `_NPROCESSORS_ONLN` heuristic we have isn't cgroups aware. So it thinks it has e.g. 40 CPUs when running in a k8s pod. This can then blow through our allocated resource limits. Declare some modest amount of RAM and CPU resources and override `make` parallelism. This matches what rpm-ostree now does in https://github.com/coreos/rpm-ostree/pull/2155.
* ci: Remove libpaprci/ directoryJonathan Lebon2020-06-1711-10/+9
| | | | | | And move everything that was in it directly in `ci/`. There's a bunch more cleanups here that we need to do (and more changes to upstream from the rpm-ostree copies of this).
* ci: Import latest ci-commitmessage-submodules from rpm-ostreeJonathan Lebon2020-06-171-9/+26
| | | | Especially for https://github.com/coreos/rpm-ostree/pull/2079.
* Add the same config options for distcheckDenis Pynkin2020-04-161-1/+1
| | | | Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
* Fix the lost line separatorDenis Pynkin2020-04-161-1/+1
| | | | Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
* Add ci_pkgs to travis-install.shDenis Pynkin2020-04-161-0/+3
| | | | Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
* travis: Add some libsodium coverageColin Walters2020-04-162-1/+3
| | | | | | As far as I can tell we're not gating on this right now. From a quick glance, it looks like Debian stable has `libsodium-dev` but only Ubuntu eoan does which we're not testing right now.
* Add .cci.jenkinsfileColin Walters2020-02-031-2/+4
| | | | | | See https://github.com/jlebon/coreos-ci This is just a start to test, cut down from the rpm-ostree version.
* ci/flatpak: Patch GPG error assertions from OSTreeDan Nicholson2020-01-242-0/+71
| | | | | | | | Some of the flatpak tests assert on GPG error strings that come from OSTree. Those are being changed here, so patch the cloned flatpak 1.4.1 to accommodate the new error strings. When this work lands, I'll send a patch upstream to flatpak that will eventually trickle back here in a tagged build.
* ci/rpmostree: Bump to 2019.4Dan Nicholson2020-01-211-7/+9
| | | | | | | | | | | | | | | The vmcheck tests in 2019.3 fail because of an SSH control socket issue on overlayfs. This is fixed in 2019.4[1]. That has some other changes such as using Python 3 in tests. The package dependencies have been synced from the rpm-ostree CI for that. Unfortunately, this is no longer a totally representative test of f29 since it has 2019.3 in updates. But that's the price you pay for exercising someone else's CI from your own CI. 1. https://github.com/coreos/rpm-ostree/commit/c89f81c1385ef095616b0e7001926572a20057b2 Fixes: #1994
* Revert "Always enable trivial-httpd for tests"Alex Kiernan2019-10-192-6/+0
| | | | This reverts commit 82699a67dbb6bfcc9452bb969e7872809232a84f.
* Merge pull request #1912 from akiernan/us-fix-trivial-httpdOpenShift Merge Robot2019-10-162-0/+6
|\ | | | | Gate ostree-trivial-httpd on BUILDOPT_TRIVIAL_HTTPD
| * Always enable trivial-httpd for testsAlex Kiernan2019-10-092-0/+6
| | | | | | | | | | | | | | When running tests we always need ostree-trivial-httpd, so enable it unconditionally Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
* | ci: Skip all yum operations if SKIP_INSTALLDEPS is setColin Walters2019-10-161-0/+8
| | | | | | | | | | | | | | | | | | This is used by our OpenShift Prow job; we use the cosa buildroot container: https://github.com/coreos/coreos-assembler/pull/730 And using `yum` at all means we can flake on fetching rpm metadata.
* | ci: Make ${ARTIFACTS} directoryColin Walters2019-10-141-0/+1
| | | | | | | | It may not exist in OpenShift Prow by default.
* | ci: Honor ARTIFACTS environment variableColin Walters2019-10-111-1/+3
|/ | | | | | | | | | This is set by the OpenShift Prow pod-utils: https://github.com/openshift/test-infra/blob/master/prow/pod-utilities.md Prep for having OSTree use that. Closes: #1930 Approved by: jlebon
* ci: Add prow/ subdirectory with DockerfileColin Walters2019-08-292-1/+11
| | | | | | | | | | | | | | | | | I'd like to add OpenShift's prow to this repository. Let's start by adding a Dockerfile - it doesn't really do anything besides build. However...I've lately been thinking about e.g. shipping the ostree tests as an image, and then e.g. we could test FCOS by running that container (which would orchestrate the *host's* ostree). Anyways, not doing that right now but this is a start. Also this cherry picks the fix from rpm-ostree CI for the sad Fedora release package brokenness. Closes: #1906 Approved by: cgwalters
* ci/rpmostree: Bump to 2019.3Dan Nicholson2019-07-271-1/+1
| | | | | | | | | | | | The test-ucontainer.sh test in rpmostree 2019.1 is failing for non-ostree reasons. This is fixed in [1], which is part of 2019.3. I believe this is still a relevant test of f29 since that's what's shipped in f29-updates. 1. https://github.com/projectatomic/rpm-ostree/commit/45b6186be0826889d805ba55bee3be75b042ed35 Closes: #1892 Approved by: jlebon
* ci/flatpak: Bump FLATPAK_TAG to 1.4.1Robert Fairley2019-06-211-1/+1
| | | | | | | | | | Bump the flatpak version used in CI to avoid a repeated definition of `renameat2()` in libglnx and glibc. See: https://github.com/ostreedev/ostree/pull/1871#issuecomment-503768062 Closes: #1871 Approved by: jlebon
* ci/build-check: Remove unused-command-line-argument diagnosticRobert Fairley2019-06-211-2/+1
| | | | | | | | | | | | Since `clang-4.0` is no longer being used, it should be safe to remove use of this diagnostic for clang. This enables using `gcc` as a workaround for `g-ir-scanner`, as `unused-command-line-argument` is not recognized by `gcc`. See: https://github.com/ostreedev/ostree/pull/1871#issuecomment-503765624 Closes: #1871 Approved by: jlebon
* ci: Use Fedora 29 artifactsRobert Fairley2019-06-212-9/+8
| | | | | | | | | | | | Use Fedora 29 artifacts instead of Fedora 28, since 28 is now end-of-life. Also rename `ci/fah28-insttests.sh` -> `ci/fah29-insttests.sh` and use the https://getfedora.org/atomic_qcow2_latest redirect URL for the latest Fedora Atomic Host 29 image. Closes: #1871 Approved by: jlebon
* ci: Split out installdeps.sh from build.shRobert Fairley2019-05-272-15/+24
| | | | | | | | This script is useful to run individually when setting up a development environment for OSTree. Closes: #1865 Approved by: jlebon
* travis: Update to Debian StretchRobert Fairley2019-04-231-1/+1
| | | | | | | | | | | Update to Stretch to use updated version of glib2.0. Fixes CI failure when parsing error output in tests/test-config.sh. See: https://github.com/ostreedev/ostree/pull/1838#issuecomment-482186680 https://api.travis-ci.org/v3/job/518830164/log.txt Closes: #1839 Approved by: cgwalters
* ci/rpmostree: Bump to 2019.1Colin Walters2019-03-011-1/+1
| | | | | | | Should fix the issue that CI broke due to libsolv not being sync'd. Closes: #1806 Approved by: jlebon
* ci/rpmostree: Fix use of `fatal`Colin Walters2019-03-011-1/+1
| | | | | | | We're not using libtest, just inline it. Closes: #1806 Approved by: jlebon
* ci: Bump rpm-ostree tag to 2018.8Jonathan Lebon2018-09-281-1/+1
| | | | | | | | | 2018.7 started failing `test-ucontainer.sh`. I don't have the cycles to look more deeply into what was going on there, but bumping to 2018.8 fixes it at least. (And of course, it's passing in rpm-ostree too.) Closes: #1728 Approved by: cgwalters
* ci: Bump rpm-ostree tag we build for testsJonathan Lebon2018-08-191-2/+2
| | | | | | | | | | The latest rpm-ostree release no longer requires `python3-devel` so `dnf builddep` here is no longer pulling it in, subsequently causing issues when building an older rpm-ostree release. Let's just bump the release tag so we don't have to also start keeping track of older dependencies. Closes: #1708 Approved by: cgwalters
* ci/flatpak: Fix to use built ostree versionColin Walters2018-06-291-4/+18
| | | | | | | | | | Noticed as part of a random failure in this PR: https://github.com/ostreedev/ostree/pull/1655 that we weren't actually testing the version of ostree we built in git. Probably we should be generating RPMs but...later. Closes: #1662 Approved by: jlebon
* ci: Workaround getfedora.org/atomic_qcow2_latest being 404Colin Walters2018-06-271-1/+2
| | | | | Closes: #1652 Approved by: cgwalters
* ci: Use master branch as flatpak tagMatthew Leeds2018-05-311-19/+5
| | | | | Closes: #1607 Approved by: jlebon
* ci: Drop gpgme and libgcrypt hacksJonathan Lebon2018-05-291-10/+0
| | | | | | | These shouldn't be needed anymore in F28. Closes: #1601 Approved by: cgwalters
* ci: Bump to f28, except flatpakJonathan Lebon2018-05-293-2/+7
| | | | | | | | | 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
View Lorry Controller Status