Willy, Am 16.05.19 um 09:42 schrieb Willy Tarreau: > It would be nice next time to give a bit more information. Maybe for > you this cirrus stuff is legacy, but I never heard about it before, am > not used at all to this type of tools, and don't even know why this one > and not another one. And can't we use just one instead of fragmenting > the build results between multiple sites ? These are typically the
Sorry for the duplicate email. I thought the part of "why do we need two services" was in another mail and I stripped the paragraph without checking: The reason is simple. These CI services only support a limited number of operating systems. For Travis this is Linux and Mac. Since a few months Windows as well. Cirrus appears to supports Linux, Mac and FreeBSD (which probably would have been sufficient). But honestly: I never heard about Cirrus before, while Travis is very well known in the GitHub community. This makes it easier to find Travis expertise in case something goes wrong. Personally I also find Travis' UI cleaner. So while Travis technically is redundant now it has some nice user experience benefits compared to Cirrus. And as Travis is set up anyway we may as well leave it enabled. Best regards Tim Düsterhus
