On Montag, 17. Januar 2022, 09:26:00 CET Dan Čermák wrote:
Hi Adrian,
first, apologies for the previous empty email, I hit the wrong key…
Adrian Schröter <adrian@suse.de> writes:
If you want to test the existing examples you need to use a forked osc. You get it the tooling via the following commands, but be aware that I did not test much (even though I use it now permanent on my workstation):
# zypper ar https://download.opensuse.org/repositories/home:/adrianSuSE:/OBSGIT/15.3/ OBSGIT # zypper dup --from OBSGIT
This should update osc and the build package. Also the new obs-scm-bridge package gets installed.
How radical are the changes that you had to implement?
Not exactly sure what you mean here, but this support is a parallel code path in most places. So it is new functionality, but not changing any existing. Beside osc everything has been merged meanwhile. The packages in my project just may be newer sometimes.
On Project Level
You can use the same <scmsync> element to specify a git repository in project meta. Any directory there is considered to be a package.
Any build configuration parts (what you have in "osc meta prjconf" usually) can be stored in a file called '_config'.
We support this in multiple ways:
One plain single repository providing everything. You can find a real life example here:
https://build.opensuse.org/project/show/home:adrianSuSE:OBSGIT:Project-examp...
or the git repo here:
https://github.com/geckito/image-RaspBerryPi4-pi-hole
As you notice, it is a repositoy from our Geckito project. This means the same project can get build inside of OBS or it can be build entirely independend using the "pbuild" tool.
An example which is more likely to suite larger projects, like our distributions is using git submodules. You can find an example here:
https://build.opensuse.org/project/show/home:adrianSuSE:OBSGIT:Project-examp...
or the git repo here:
https://github.com/adrianschroeter/git-project-example-submodules
This is just referencing two git repositories from our earlier examples.
Both of the projects that you linked here do not have any packages visible via the obs webui. Is that a bug or a current limitation?
well, a current limitation. However, there is already a first step to allow access to build results and avoiding webui errors is here already: https://github.com/openSUSE/open-build-service/pull/12071 -- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev