On 09/15/2016 05:38 PM, Pierre Tardy wrote: > > Well. That far is not that difficult. It just integrated github > reporter api so that there is a link for each test of the matrix. > > There is no support for gitlab yet. I'm not sure there is such a > demand for that as gitlab Ci looks already quite good (on paper..I > never actually tried it) > For the record, I'm working these days with a team that started using Gitlab CI yesterday ! This is a mild disapointment, because I've been mentioning buildbot for a while to them (well and CI in general). I didn't get a demo yet, but I can take the opportunity to look at it.
Personnally, I'd be more interested with integration with Kallithea. It's certainly on my list of potential midterm developments. > > It won't be very difficult to implement as there are already many > gitlab components in buildbot. > > > Le jeu. 15 sept. 2016 00:14, Dan Kegel <d...@kegel.com > <mailto:d...@kegel.com>> a écrit : > > On Wed, Sep 14, 2016 at 2:36 PM, Pierre Tardy <tar...@gmail.com > <mailto:tar...@gmail.com>> wrote: > > buildbot travis is an experimental buildbot setup that focuses > on having the > > UI directly in github or gerrit rather than in buildbot itself, > this is why > > it might be a little bit confusing. > > People are supposed to be pointed at buildbot only when there is > a failed > > build, and directly in the problematic page. > > Well, well, well. That's interesting. I had seen > https://github.com/buildbot/buildbot_travis but hadn't realized it > went that far. > > Do you have an example install of gitlab with a corresponding buildbot > doing the build work? > And how does this compare to using gitlab ci? > > > > _______________________________________________ > users mailing list > users@buildbot.net > https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users
