Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
After the feature gets approved, it usually takes like 5 mins for me to deploy it.
The hard part comes after that which is to sit in the front of the terminal for an hour or two, hoping that the system doesn't just explode/implode.
There is no fixed intervals for releases, sometimes it's quick sometimes it takes like 3 weeks to release. -
Pro max 😎
Code changes
Think of testing
Then become lazy
Push the code in production
Test on production
If its breaking things revert back and then test on local
Otherwise we good to go
Dev to production time near real time in most cases
Who needs adventure when we have deployment -
Every 2 weeks, we have to go to a committee to verify the risks and our strategy, so we usually deploy medium-sized chunks
-
Full CI/CD run with deployment to 3 environments takes about 15 minutes
Avg frequency: 3x/week - 1x/2 weeks (depending on how "demoable" the work is)
Related Rants
-
github14That's the exact question that came to me 2 years back when I was also going to go to sleep early tonight
-
screamingwtf3Found on 2019's Stack Overflow Annual Developer Survey
-
jdevs17I am Computer Science Student Yesterday I asked question to my classmates, what is Linux, here's some(non-fo...
Dev poll: how long does it take your team to deploy a release and how often do you release?
random
survey
curiosity
cicd
question