On Thu, Apr 21, 2016 at 6:14 AM, jan iversen
<jani@documentfoundation.org> wrote:
Sorry for double mail, to this theme, but speaking with a good friend of mine (who runs a very
big ci system), I got an idea, which might solve the problem for good.
Whenever jenkins builds a gerrit job, jenkins master knows when all platforms for that patch is
compiled
Nope.
as I explained earlier.. tb job are per platform/config and are not
linked... so there is no garanteed that a given commit will get a tb
build on every config
one reason among other is the huge disparity in build time... so the
setup favor quick turn around per platform/config and maximal coverage
rather than big blocking check-all on the same commit setup
But ultimately the solution is to concentrate on gerrit build
verificatio, ot add the same coverage than tb there.. and leave the tb
as they are..
that way if something pass gerrit build verification it _will_ pass tb
so always green tb become a 'always gerrit workflow'
Norbert
Context
- Re: Broken master and newcomers. (continued)
Re: Broken master and newcomers. · Norbert Thiebaud
Re: Broken master and newcomers. · Refaeliadria
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.