Re: Please stop committing on a broken build! ([Testbot] Plone 5.0 - Python 2.7 - Build # 1925 - Regression! - 6 failure(s))

>
> We can't just merge features and then keep the build broken for weeks.
> People are committing anyways, breaking more stuff without notice and in
> the end someone has to clean up that mess. The longer we keep the build
> broken the harder it gets...
>
> I try to keep track and remind people if they break things, but that
> only works well if the build is green in the first place.


Would it be possible to get tests running on feature branches as well as
master / version branches? It seems unavoidable that occasionally checkins
will break the build, but if those checkins are always made to a feature
branch and merging of the feature to master happens only after looking at
the build status then master should stay green. (Ideally one first merges
from master to the feature branch to ensure the merge back is clean.)

I realise the above is very tricky for a system as complex as Plone, but
I've found it to be a great help in my (much smaller) current project.

Laurence

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers