> A lot of failed builds were caused by missing (suddenly deleted/disappeared) artifacts
> not by incoming model changes.
> So autovalidation by Jenkins will probably prevent maintainers to submit a patch which
> fixes, but depends on the broken master state.
Item #2 from my writeup (mirroring of contributions) would ensure aggregation cannot be affected by deleted or changed repositories.
Auto validation does not prevent a fix from being contributed if somehow aggregation does break. By definition, a broken base state plus a good fix results in passing aggregation. Auto validation does prevent unrelated contributions from going through in a broken base state, but that’s a good thing, since the broken base state needs to be addressed first.
- Konstantin
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Dennis Hübner
Sent: Tuesday, July 09, 2013 3:00 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] 6 month release cycle
Am 09.07.2013 um 11:41 schrieb Mickael Istria:
On 07/08/2013 09:49 PM, Konstantin Komissarchik wrote:
1. New contributions are piled on, aggregation happens, problems are found and need to be sorted out manually. Meanwhile, aggregation is broken and more contributions pile on. The solution is to remove direct access to aggregation metadata and process one contribution at a time. When a contribution request is made, aggregation is performed. If it fails, the contribution is rejected and the contributing project gets to figure out what’s wrong without affecting anyone else.
Seems like using Gerrit to process contributions into aggregator would help. However, it means that someone has to review and merge this contributions manually; but if this Gerrit review also triggers a Jenkins build that validates the aggregation (without publishing it), it wouldn't be too difficult to maintain as it would spot some errors early and automatically.
A lot of failed builds were caused by missing (suddenly deleted/disappeared) artifacts not by incoming model changes.
So autovalidation by Jenkins will probably prevent maintainers to submit a patch which fixes, but depends on the broken master state.
So IMHO gerrit would not eliminate the problem in the whole, but can probably make the maintenance not that easy
Best regards,
Xtext Commiter / Build Engineer
Mobile: +49 (0) 151 / 17 39 67 07
Telefon: +49 (0) 431 / 990 268 70
Fax: +49 (0) 431 / 990 268 72
itemis AG
Niederlassung Kiel
Am Germaniahafen 1
24143 Kiel
http://www.itemis.de/
Rechtlicher Hinweis:
Amtsgericht Dortmund, HRB 20621
Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus
Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus
