Go to file
Nicolas Belouin cf3153e074 Sync metadata, revamp PR jobs
Signed-off-by: Nicolas Belouin <nicolas.belouin@suse.com>
(cherry picked from commit d6d501ad99)
(cherry picked from commit 4d824b71cc)
(cherry picked from commit 0d3c83fca1)
(cherry picked from commit 5a73d61002)
(cherry picked from commit 34687fb5e9)
(cherry picked from commit 4a99805fde)
(cherry picked from commit 331f08255c)
(cherry picked from commit 3dea69443d)
(cherry picked from commit d97e434fce)
(cherry picked from commit 9e41ee25d9)
(cherry picked from commit 8f20b3433e)
2025-02-24 16:00:18 +01:00
2025-02-24 16:00:18 +01:00
2024-10-22 16:43:48 +02:00
2024-11-19 16:50:59 +00:00
2024-10-22 12:26:29 +02:00
2024-10-22 16:14:46 +02:00
2024-10-22 16:14:46 +02:00
2024-11-20 19:31:00 +02:00
2024-10-22 16:43:48 +02:00
2024-10-22 11:56:05 +02:00
2024-10-17 14:01:57 +02:00
2025-02-24 15:59:45 +01:00
2025-02-24 16:00:18 +01:00
2024-10-22 14:31:29 +03:00
2024-10-22 16:43:48 +02:00
2025-02-24 16:00:18 +01:00

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)
Description
No description provided
Readme 270 MiB
Languages
Shell 32.1%
Dockerfile 22.9%
Smarty 22.3%
Jinja 11%
Python 10.3%
Other 1.4%