which is absolutely true until you wire your CI pipeline through it. Now it’s a critical fucking deploy function for dev/stage/QA and maybe prod now with workflows.
There are more ways to set up a pipeline than there are ways to shuffle a deck of cards.
Everybody seems to like to tie back into online services. People like github workflows, and using NPMs and external DNS and docker Deps and JFrog. By the time you chain all those SLAs together you’ve got a bucket of risk the size of a small bus.
I try to push them as much as possible to use straight up bash scripts, and then call those with automation.
If it were solely up to me, I’d host my own repositories, but at some point, risk and safety end up losing out to some extent to features and feasibility.
You can do all that stuff without cloud services. Which IMO is the better way to do it. It’s absolutely insane to me what people send to cloud services
which is absolutely true until you wire your CI pipeline through it. Now it’s a critical fucking deploy function for dev/stage/QA and maybe prod now with workflows.
You can run the pipelines locally. But it’s complicated so it’s better have your own scripts and keep the pipeline short.
There are more ways to set up a pipeline than there are ways to shuffle a deck of cards.
Everybody seems to like to tie back into online services. People like github workflows, and using NPMs and external DNS and docker Deps and JFrog. By the time you chain all those SLAs together you’ve got a bucket of risk the size of a small bus.
I try to push them as much as possible to use straight up bash scripts, and then call those with automation.
If it were solely up to me, I’d host my own repositories, but at some point, risk and safety end up losing out to some extent to features and feasibility.
You can do all that stuff without cloud services. Which IMO is the better way to do it. It’s absolutely insane to me what people send to cloud services
Soo, don’t do that?