3 ms·
Yeah, this is fine for early stage startups, but eventually you don't want developers to deploy directly to production.
by throwaway894345 5y ago
Yeah, this is fine for early stage startups, but eventually you don't want developers to deploy directly to production.
- Abishek_Muthian 5y agoVery interesting, Can you give some specific examples of where CI/CD tools which works fine for large organizations for other programming languages don't work to your satisfaction with Go?
- throwaway894345 5y agoI think you’ve misunderstood the thread. I was arguing that you can get away with “dev builds image locally and pushes straight to prod” in an early startup, but in a mature organization you need CI/CD.
- Abishek_Muthian 5y agoI think I got that part correctly, > My only grievance with Go in the cloud is that it's tedious to have to set up a CI job or similar to build your binaries to deploy in your functions. So I thought your CI/CD works to your satisfaction for other programming languages, But you found Go tedious and so I wanted to understand some specific cases.