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, Dennis Hübner 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
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
