Re:AWS is playing chess, Cloudflare is playing Go
by gls2ro on Monday October 18, 2021 @11:59AM
(#28906921)
Great point about CI/CD pipelines being hard to move between cloud providers. I wish someone will do for CI/CD what Docker/k8s did for cloud deployment and provide a non-proprietary structure that can be easily transferred.
Re:AWS is playing chess, Cloudflare is playing Go
by adamgordonbell on Monday October 18, 2021 @12:57PM
(#28907718)
We are building that layer for CI at Earthly.
But, depending on your use case, you could also try to describe your build process is some combination of make files and dockerfiles and then just call that from whatever CI you are using.
Re:AWS is playing chess, Cloudflare is playing Go
by forty on Monday October 18, 2021 @01:31PM
(#28908123)
First time I discovered earthly I found it looked cool, but then I encountered the issue that it needed privileged docker which is not really practical in our setup, as this would require launching one VM per build job (we are using gitlab CI)
Is it still an issue? If yes, any plan to lift this limitation?
Re:AWS is playing chess, Cloudflare is playing Go
by adamgordonbell on Monday October 18, 2021 @03:41PM
(#28910560)
It is a limitation we want to lift where we can and that we are working on. I'd love to hear more about your use-case. Email is in profile.
I tend to feel the same as you - preferring portable solutions that I can host anywhere. However, the reality that we're all building CI/CD pipelines as much as we are actual software nowadays, and moving those from one cloud provider to another is no small feat. Even if you're using some infrastructure-as-code tool to manage all of your resources (e.g. terraform), you can't really `SET TARGET=GCP` and re-run the script (so to speak).
I guess the lesson is: spend as much time picking your infrastructure provider as you do your core technical stack. They're not easy to replace! :-)