forked from suse-edge/Factory
ef6989b0d84c049328f662f21e5c89d9911667b1f2dc12e973e76c853d155935
It is now possible to bring back the original directory structure for config (/ironic-config) files and scripts (/scripts). This will make updates to re-align with upstream easier. Signed-off-by: Marco Chiappero <marco.chiappero@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.py
file (e.g. fromisv:SUSE:Edge:Factory
toisv:SUSE:Edge:3.2
) - Change the branch reference in
.obs/common.py
file (e.g. frommain
to3.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 release
of the project for it to be copied over in theToTest
section - Hand over to QA to test whatever is in
ToTest
. (You can continue to work on the base branch if needed meanwhile)
Description
Languages
Shell
32.1%
Dockerfile
22.9%
Smarty
22.3%
Jinja
11%
Python
10.3%
Other
1.4%