osbuild: store outputs in objectstore
Treat outputs like we treat trees: store them in the object store. This simplifies using osbuild and allows returning a cached version if one is available. This makes the `--output` parameter redundant. Remove it.
This commit is contained in:
parent
cb173f7d3c
commit
83475cc9f4
9 changed files with 27 additions and 34 deletions
|
|
@ -21,8 +21,8 @@ jobs:
|
|||
- name: pipeline-noop
|
||||
before_install: sudo apt-get install -y systemd-container
|
||||
script:
|
||||
- sudo env "PATH=$PATH" python3 -m osbuild --libdir . --output . samples/noop.json
|
||||
- sudo env "PATH=$PATH" python3 -m osbuild --libdir . --output . samples/noop.json
|
||||
- sudo env "PATH=$PATH" python3 -m osbuild --libdir . samples/noop.json
|
||||
- sudo env "PATH=$PATH" python3 -m osbuild --libdir . samples/noop.json
|
||||
- name: f30-boot
|
||||
before_install: sudo apt-get install -y systemd-container yum qemu-kvm
|
||||
script: sudo env "PATH=$PATH" python3 -m test --case f30-boot --build-pipeline samples/build-from-yum.json
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue