-----BEGIN PGP SIGNED MESSAGE-----
Am 29.11.2013 11:26, schrieb Adrian Schröter:
Am Freitag, 29. November 2013, 10:36:38 schrieb Josef
On Thu, 28 Nov 2013 18:32:56 +0000 Susanne
Stephan Kulow <coolo(a)suse.de> writes:
The build server is what it says: a *build* server.
We use it as an integration server, quite successfully, and it
comes close, but it is not explicitely targeted at
So it is missing a few features to better support integration:
* Tools like git support 'merge' tracking of changes in
branches back to mainline and from progress in mainline back to
the branch. This then also allows to bisect regressions to the
+1, I really miss some features from git and easy merging is one
a git backend is there, but not finished. git can not replace our
source server entirely due various issues, but we could offer also
to store sources in a git repo on the server.
* 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
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 https://travis-ci.org/
or code quality metter like
response set status for such request so you immediatelly see if
request passes tests or if quality of code goes up or down ( I
think it will be really useful for e.g. rpmlint warnings, now I
don't see if submit request increase or decrease number of
warnings ). Now it is partially done in BS itself with their own
check if rpm build. And if it is generic, then we can easily add
different services in future like attach to project security
scanner and check if in new version is new security warning. I
prefer component system before monolitic application.
Yes, my idea here is to offer also such a trigger mechanism as
described in the blog URL above to handle review states in
So, an external tool can be used more easily without the need to
store user credentials on that system.
Would this be a solution?
It would be good, if OBS could trigger webhooks (that is send out a
HTTP GET request to one or more predefined URLs with some JSON details).
This would be useful for many events that were signalled through
* publish of a repo
* SR new or changed state
* build finished
* source checkin
you could even rewrite hermes as a receiver of such webhooks.
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org