Nicolas Belouin
98fa8835f7
All checks were successful
Build PR in OBS / Build PR in OBS (pull_request_target) Successful in 18s
- Make the different ipa-ramdisk packages installable side by side - Clean the ipa-downloader Dockerfile from what seems to be unneeded - Get both images in - Use zstd instead of xz for better speed - Check sums before redoing certs integration - Add value to metal3 chart to select between architectures - Get the two ESP available as well Signed-off-by: Nicolas Belouin <nicolas.belouin@suse.com>
Factory
Contains the definition of the packages built on OBS for the SUSE Edge Solution (WIP)
This repository is linked to an OBS project: https://build.opensuse.org/project/show/isv:SUSE:Edge:Factory Every directory in this repository represents a package in that OBS project, those should be synced automatically from this repository.
Testing a fork or a development branch
You can create a project in your home space in OBS, use the same prjconf as the one of "isv:SUSE:Edge:Factory", and copy the repositories part of the metadata (adjust self references). Then add a scmsync stanza to your metadata like this (adjust repository path and branch):
<scmsync>https://src.opensuse.org/suse-edge/Factory#main</scmsync>
This is done automatically for any PR filed against this repository.
Cutting a release version branch
- Do the appropriate git branch command
- Change the project path in
.obs/common.pyfile (e.g. fromisv:SUSE:Edge:Factorytoisv:SUSE:Edge:3.2) - Change the branch reference in
.obs/common.pyfile (e.g. frommainto3.2) - Commit those changes to the new branch and push the new branch
- Go take a few cups of coffee/tea/mate/... while waiting for OBS to build everything
- Once built do an
osc releaseof the project for it to be copied over in theToTestsection - Hand over to QA to test whatever is in
ToTest. (You can continue to work on the base branch if needed meanwhile)