Post ASCtx4wLIIZ7Mm7Uwq by bagder@mastodon.social
 (DIR) More posts by bagder@mastodon.social
 (DIR) Post #ASCtx4wLIIZ7Mm7Uwq by bagder@mastodon.social
       2023-01-31T07:57:19Z
       
       1 likes, 0 repeats
       
       The #curl project has now "abandoned" a second CI service as we no longer use Zuul CI anymore as of yday. We dropped Travis CI in mid-2021.We are still using five separate CI services as we speak, with GitHub Actions doing the most.
       
 (DIR) Post #ASDNE7OGKnRaYkelpA by akira28@mastodon.social
       2023-01-31T18:09:52Z
       
       0 likes, 0 repeats
       
       @bagder wouldn't be less cumbersome to have just one or two CI? Out of curiosity what's missing from Github Actions that the other services have?
       
 (DIR) Post #ASDNE85Vk02SistJEe by bagder@mastodon.social
       2023-01-31T21:27:26Z
       
       1 likes, 0 repeats
       
       @akira28 sure, and if we remove all CI jobs it would be even less cumbersome!
       
 (DIR) Post #ASDNJ6EM4e7aPVOimW by satan@hell.social
       2023-01-31T21:33:59.808Z
       
       0 likes, 0 repeats
       
       @akira28@mastodon.social The thing that is missing from GitHub actions is the absence of the slimy fingers of Microsoft @bagder@mastodon.social
       
 (DIR) Post #ASELWLr1I87psedNOC by bagder@mastodon.social
       2023-01-31T22:35:24Z
       
       1 likes, 0 repeats
       
       @akira28 @satan platform support is the main one (plus increased parallelism and redundancy), but there are feature reasons too - I don't have them off the top of my head now though. For example we couldn't move our azure pipelines jobs to GHA even though they're run by virtually the same company...
       
 (DIR) Post #ASELZaKLwAQRdXtcsS by bagder@mastodon.social
       2023-01-31T22:36:29Z
       
       1 likes, 0 repeats
       
       @akira28 @satan besides, what we have is a working and functional setup. it is work to change it, so why would we do that just for the sake of using fewer CI services?