> One way to reduce load is to figure out a way to award +1s to parent > patches when a dependent patch passes regression. It is recommended > that a change be split into as many smaller sets as possible. > Currently, if we send 4 patches that need to be serially merged, all 4 > have to pass regressions. Instead, if Jenkins offered a way to block > merging of subset of patches and made it possible to take all 4 in in > one go, we could run tests only on top of these patches. The last time > I checked, such a feature did not exist in Jenkins. How hard would it be to make it so that regression votes for a patch at the top of the stack get propagated to all as-yet-unmerged ancestors, or at least those without votes of their own? With that little piece, I think the rest could be handled as a matter of process/convention. _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
