17b108ef3dfa59e2b2f327b8c92fa7edf9a3dd9453d2c8f8d41a9f318bb8456d
All checks were successful
Build PR in OBS / Build PR in OBS (pull_request_target) Successful in 10s
Aligns with latest 0.9.4 version on this branch
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%