On 22 Jan 2016, at 21:08, Kei Nohguchi wrote:

I also have an experience with gitlab at the last project. It's closer to the github.com experience. Here is one example of the open one (NTPsec)

https://gitlab.com/groups/NTPsec

What's your experience of GitLab? I havn't used it in anger really. It looks good. What would you say the downsides are?

Hi Paul and all,

I liked it. It's just like github. One thing I didn't experience during that time was CI integration, which was done through their in-house CI system.

But based on their web, it's integrated.

https://about.gitlab.com/gitlab-ci/

Hosted CI systems don’t work for my tests. In general, the issues are:
        - Limited OS support for build.
They may support “Linux”, but try building on specific versions i.e., Ubuntu 12.04, CentOS 6, etc and good luck finding support for specific versions of FreeBSD, OpenBSD or even Solaris.

- Support for Unittests only, most of them don’t support multi-host setups for testing to simulate
        and test network topology

- Most of my tests (i.e. the Compliance Tests, Fuzzer etc) require dedicate test equipment to run. I’m using equipment and software from Spirent, Ixia etc for my testing

(PS: I’m giving a talk about the challenges on testing Quagga at the Netdevconf in Sevilla at the beginning
of february)

It's looks like similar what zuul/jenkins can offer for gerrit but I can't comment on it much, as I haven't play with it yet.

http://docs.openstack.org/infra/zuul/

My CI system is a locally hosted Atlassian Bamboo.

By the way, why github is not the option? I believe we've already talked about it, but just curious.

I prefer something which is self-hosted. Usually more flexible to customize and add hooks as needed (i.e. hooks into my CI system). Not sure what other think, but my impression that at this time we mainly discuss choices for code
review and focus on choices which can be self-hosted

- Martin Winter


_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to