forked from suse-edge/Factory
Nicolas Belouin
cf3153e074
Signed-off-by: Nicolas Belouin <nicolas.belouin@suse.com> (cherry picked from commitd6d501ad99) (cherry picked from commit4d824b71cc) (cherry picked from commit0d3c83fca1) (cherry picked from commit5a73d61002) (cherry picked from commit34687fb5e9) (cherry picked from commit4a99805fde) (cherry picked from commit331f08255c) (cherry picked from commit3dea69443d) (cherry picked from commitd97e434fce) (cherry picked from commit9e41ee25d9) (cherry picked from commit8f20b3433e)
1.4 KiB
1.4 KiB
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)