suse-edge/Factory
SHA256
11
0
Fork 6
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Factory/README.md
Nicolas Belouin 8f20b3433e
All checks were successful
Synchronize Project Config / Update prjconf in OBS (push) Successful in -5s
Details
Synchronize Project Metadata / sync-prj-meta (push) Successful in 3s
Details
Fix PR closed workflow 
Signed-off-by: Nicolas Belouin <nicolas.belouin@suse.com>
2025-02-24 15:44:23 +01:00

1.4 KiB
Raw Permalink Blame History

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

  1. Do the appropriate git branch command
  2. Change the project path in .obs/common.py file (e.g. from isv:SUSE:Edge:Factory to isv:SUSE:Edge:3.2)
  3. Change the branch reference in .obs/common.py file (e.g. from main to 3.2)
  4. Commit those changes to the new branch and push the new branch
  5. Go take a few cups of coffee/tea/mate/... while waiting for OBS to build everything
  6. Once built do an osc release of the project for it to be copied over in the ToTest section
  7. Hand over to QA to test whatever is in ToTest. (You can continue to work on the base branch if needed meanwhile)