Mailinglist Archive: opensuse-factory (1029 mails)

< Previous Next >
Re: [opensuse-factory] O Factory - Where art Thou?
Am Freitag, 29. November 2013, 12:34:59 schrieb Josef Reidinger:
On Fri, 29 Nov 2013 11:49:24 +0100
Adrian Schröter <adrian@xxxxxxx> wrote:

Am Freitag, 29. November 2013, 11:43:54 schrieb Stephan Kulow:
On 29.11.2013 11:26, Adrian Schröter wrote:
* Integration means testing, and testing may be a
gate/decision point whether further builds make sense at all
(think rings). This tracking of test status is not in the
tool. And tests should gate further work based on test
status. And tests, automatic or manual, have a smart and a
stupid order doing them.

What would be really nice here, is to have hooks in BS like
github. If new pull request is created, then there is hook that
can told it to CI like


I knew you would jump on it but hooks for github are something else
than hooks like github ;)

When offering also this for reviews, these review hooks can run

We can also discuss to run them within OBS, but I think other
possibilities, like rpmlint or source services are the better
approach then.

I mean it other way - submit requestion on BS -> call hoooks -> get
back result so something like factory_auto and others. I don't know how
easy or hard is to add such reviewers, if I want to use it outside of
factory for my own project.

You can define default reviewer in any project or package. Means, a new
request for this project/package gets this reviewer by default.

When your external

From reviews at it looks
like you need to create fake user for it.

or a group. this group would define which users can act on behalf of the group.
We could also add the token/trigger system there.

Our solution for that are at the moment automatic reviewers that
poll for new reviews to do and then queue something. So if you do a
new SR factory-auto, legal-auto, repo-checker run on it and do
their CI. We can extend that heavily - but nothing of that will be
"Source update" ;)

right, but the /trigger route could also be used to do other defined
tasks. For example like changing the review state. That was what I
proposed here.

So if I get right how reviews work, then if we have e.g. security
scanner, then if new thing appear he must open review for someone to
manual check new detected issue, right?

That is one way to do it.


Adrian Schroeter
email: adrian@xxxxxxx

SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284
(AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg

To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >