Re: Buildbots

[Graham Bloice <graham.bloice () trihedral com>]

There's also the:

2.0 buildbot - https://buildbot.wireshark.org/wireshark-2.0/waterfall
1.12 buildbot - https://buildbot.wireshark.org/wireshark-1.12/waterfall
Debian LTS buildbot - https://buildbot.wireshark.org/wireshark-lts/waterfall

These are all listed on the develop page -
https://www.wireshark.org/develop.html#buildbot

I believe they are automatically triggered on commits to the respective
branches.



On 19 November 2015 at 16:48, Evan Huus <eapache () gmail com> wrote:

> As you said, petri-dish is triggered by core devs for unmerged gerrit
> changes to test them before merging. Master is triggered on every merge to
> build the actual git master branch.
>
> On Thu, Nov 19, 2015 at 11:45 AM, Dario Lombardo <
> dario.lombardo.ml () gmail com> wrote:
>
> > I've found 2 different buildbot projects for wireshark
> >
> > https://buildbot.wireshark.org/petri-dish/
> >
> > and
> >
> > https://buildbot.wireshark.org/wireshark-master/
> >
> > Can anyone explain me the difference? I've understood that petri-dish is
> > manually triggered by core-devs from gerrit. Who triggers the
> > wireshark-master?
> > Sorry if it's a stupid question, but I like to understand all the code
> > audit tools that run around wireshark.
> > Thanks.
> > Dario.

-- 
Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe