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. Cheers, Dan -- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman