[Graham Bloice <graham.bloice@xxxxxxxxxxxxx>]

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@xxxxxxxxx> 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@xxxxxxxxx> 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