
On Donnerstag, 20. Juli 2023, 14:20:37 CEST Dan Čermák via openSUSE Factory wrote:
Hi Filippo and Dirk,
Filippo Bonazzi <fbonazzi@suse.de> writes:
On Thu, Jul 20, 2023 at 01:57:39PM +0200, Dirk Müller wrote:
Yes, this sounds very desirable. Ideally the bot would create a test project on OBS, build the forked Git repo head (at least) and make the results (OK/KO, built RPMs and rpmlint / build log) available. Other than the green/yellow/red dot, the bot could add links the build artifacts e.g. in a comment on a commit.
you can have that by using the already existing git scm workflow, no need to reinvent the wheels in the scm-staging bot. What I'm saying is, I feel like this functionality should be available by default in a new Git-based workflow, as it would be the only way to have access to build results when working outside of OBS. Having to set up Git<->OBS integration manually for every fork of every repo I would ever interact with on src.opensuse.org sounds like a lot of work.
I agree with Filippo here, setting up the integration yourself for every fork is pointless busywork and makes the git based workflow *worse* than the existing workflow on OBS.
Absolutely, but we have to keep in mind that we want to support scenarios where a package git is build in multiple projects, offering multiple flavors based on the config there (eg. switching on/off certain functionality). So a simple branch mechanism as we had it so far would not be sufficient. The other freedom, which we want to achieve is that you can easily do these test builds in non-OBS infrastructure (eg. because you have your QA systems there as well). For the ALP project we have already a config which allows to run "pbuild" in any place (however, also a lot is missing there as well). Neverthless we should also aim to support this kind build setups where you can build a set of packages reproducible as in OBS IMHO (also for Factory, for ALP we definitive will). The question for me is how to allow users to create these kinds of setups easily. Doesn't have to be bound to OBS, might be created with some dedicated small tooling though. On the other side, we should try to keep the setups for our users centralized where one can get newer software stacks of Factory also for older or foreign distros IMHO. I personally consider these as the main benefit for users and also for factory developers as our devel projects give benifits to both parties. -- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev