summaryrefslogtreecommitdiff
path: root/.cci.jenkinsfile
Commit message (Collapse)AuthorAgeFilesLines
* *: rename master branch to main (external repos)Timothée Ravier2021-05-071-1/+1
|
* *: rename master branch to mainTimothée Ravier2021-05-071-2/+2
|
* build-sys: Remove --enable-experimental-apiColin Walters2021-04-071-1/+1
| | | | | | | | | It was added for the collections bits, but we made that stable. It's now just cruft and we're very unlikely to reuse the infrastructure again. Motivated by a unit test failure when running from a tarball: https://github.com/ostreedev/ostree/issues/2313
* cci: Update for buildroot changesColin Walters2021-03-311-19/+23
| | | | See latest in https://github.com/coreos/fedora-coreos-tracker/blob/master/docs/ci-and-builds.md
* Drop minimal rust/ libraryColin Walters2021-03-181-5/+0
| | | | | | | | | | | | | | | | | | | This was my first experiment with using Rust in this way; I gained a lot of knowledge from it. But, we don't really gain anything from the code as it is today - while it is "bit fiddling" code, the C code is well tested. We have a lot of compile-time options, and trimming them will be helpful. We've also gotten pushback on hard requiring Rust client side. Instead, what I'd like to do is hopefully soon create an `ostree-system` crate that uses the existing `ostree` library and can contain code drained from the rpm-ostree Rust and used by other projects perhaps. So the goal here is really more Rust, but we need to focus our efforts on where it's most valuable.
* ci: Drop var mount testColin Walters2020-09-031-6/+0
| | | | Merged in https://github.com/coreos/fedora-coreos-config/pull/586
* ci: Temporarily import kola test from jlebon's FCOS forkJonathan Lebon2020-08-281-0/+6
| | | | | | | | | | That test will not make it into the fedora-coreos-config repo until the libostree fix gets percolated down. PR is: https://github.com/coreos/fedora-coreos-config/pull/586 But we want to make sure that the fix does work and that we don't regress on it. So manually fetch it for now.
* tests/inst: Add destructive test frameworkColin Walters2020-08-171-0/+2
| | | | | | | | | | | | | | | | This adds infrastructure to the Rust test suite for destructive tests, and adds a new `transactionality` test which runs rpm-ostree in a loop (along with `ostree-finalize-staged`) and repeatedly uses either `kill -9`, `reboot` and `reboot -ff`. The main goal here is to flush out any "logic errors". So far I've validated that this passes a lot of cycles using ``` $ kola run --qemu-image=fastbuild-fedora-coreos-ostree-qemu.qcow2 ext.ostree.destructive-rs.transactionality --debug --multiply 8 --parallel 4 ``` a number of times.
* ci: add pxe-offline-install testiso scenarioStephen Lowrie2020-08-111-1/+1
|
* ci: Fix ISO testingColin Walters2020-08-021-3/+3
| | | | | | | | | | | | Regression from https://github.com/ostreedev/ostree/pull/2158/commits/5d7f897908dbf7f471ddfdbd6c29a84ac6bc0bda I'm not sure how (or if) this passed before, the job logs have been GC'd. This is a bit confusing but basically right now ostree/rpm-ostree's CI jobs don't use `/srv/fcos` - it might make sense to port these to `fcosBuild` but that needs investigation.
* ci: test FCOS PXE and ISO installBenjamin Gilbert2020-07-311-1/+15
| | | | | Make sure we don't break the FCOS live image. PXE is probably sufficient, but also test the ISO image for good measure.
* ci: Constrain parallel build jobsJonathan Lebon2020-07-161-5/+7
| | | | | | | | | | | | 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.
* Add new Rust-based testsColin Walters2020-05-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | There's a lot going on here. First, this is intended to run nicely as part of the new [cosa/kola ext-tests](https://github.com/coreos/coreos-assembler/pull/1252). With Rust we can get one big static binary that we can upload, and include a webserver as part of the binary. This way we don't need to do the hack of running a container with Python or whatever. Now, what's even better about Rust for this is that it has macros, and specifically we are using [commandspec](https://github.com/tcr/commandspec/) which allows us to "inline" shell script. I think the macros could be even better, but this shows how we can intermix pure Rust code along with using shell safely enough. We're using my fork of commandspec because the upstream hasn't merged [a few PRs](https://github.com/tcr/commandspec/pulls?q=is%3Apr+author%3Acgwalters+). This model is intended to replace *both* some of our `make check` tests as well. Oh, and this takes the obvious step of using the Rust OSTree bindings as part of our tests. Currently the "commandspec tests" and "API tests" are separate, but nothing stops us from intermixing them if we wanted. I haven't yet tried to write destructive tests with this but I think it will go well.
* tests/kola: Move to tests/kolainstColin Walters2020-05-271-3/+2
| | | | | | Follow the precedent set in https://github.com/coreos/rpm-ostree/pull/2106 and rename the directory, to more clearly move away from the "uninstalled" test model. Prep for Rust-based tests.
* ci: Install kola testsColin Walters2020-05-151-0/+3
| | | | | | | | | | | This builds on https://github.com/coreos/coreos-assembler/pull/1441 to install our tests rather than running them from the source directory. This model will more cleanly allow us to ship our tests along with a test container or elsewhere, separate from the source directory. Also prep for https://github.com/ostreedev/ostree/pull/2048
* deploy: Add --no-mergeColin Walters2020-04-221-0/+1
| | | | | | | | | All of the underlying libostree APIs have supported passing `NULL` for a merge deployment for...a long time. But we never plumbed it up into the CLI. Add a `--no-merge` option to aid people who want to do a "factory reset": https://github.com/ostreedev/ostree/issues/1793
* ci: Build minimal without libsodium tooColin Walters2020-04-161-1/+1
| | | | | | The goal is to test "no options" build - and eventually tests. (We're not actually including libsodium in the cosa buildroot right now, but we may in the future)
* ci: Adapt to use new fcosKola semanticsJonathan Lebon2020-04-151-1/+1
| | | | | | This was changed recently and broke us since we do explicitly call `fcosKola` instead of implicitly via `fcosBuild`. Adapt to the new semantics.
* ci: use `fcosKola` for running kola testsJonathan Lebon2020-03-131-14/+1
| | | | | | | | | We were using `--no-test-exit-error` for upgrade tests but weren't actually checking for test failures after. Instead of running kola directly, just use the `fcosKola` custom step which automatically takes care of e.g. running tests in parallel and archiving results.
* ci: Test kola --upgradesColin Walters2020-03-131-0/+9
| | | | This one is very relevant for ostree.
* ci: migrate to new coreos-ci projectJonathan Lebon2020-03-021-44/+31
| | | | | Use the new custom steps. I think we could simplify things further by using `fcosBuild` but let's start with this for now.
* ci: Replace PAPR with CoreOS CIColin Walters2020-02-061-2/+84
| | | | | | | | | | | Move the alternative builds into the Jenkinsfile. Update it to do a FCOS build + kola run. We drop the flatpak/rpm-ostree runs for now; the former will needs some work to do the automatic virt bits. The latter I think we can circle back to when we e.g. figure out how to include rpm-ostree's tests in kola runs.
* Add .cci.jenkinsfileColin Walters2020-02-031-0/+36
See https://github.com/jlebon/coreos-ci This is just a start to test, cut down from the rpm-ostree version.
View Lorry Controller Status