CI/CD enables the best tech companies to improve their products many times per day. Here’s what you need to know to do the same.
What is ...
For further actions, you may consider blocking this person and/or reporting abuse
Could you elaborate on this point please:
Should feature branches be short lived so they stay closer in sync to master?
How do feature flags let you restrict unstable work from being used?
Feature flags are basically
So you don’t even load the related code unless the user is part of the dev team or a small group of beta testers. It can be totally unfinished, nobody will be affected. So you can work on it in small iterations and make sure each iteration is well integrated with the system as a whole. Much easier to deal with than a big-bang merge.
Thank you, looks good
Exactly. The longer it lives the higher the chance they will diverge and make it harder to integrate. Not just merge code on line by line level, but make sure it doesn’t introduce unforeseen bugs at runtime (because of how some APIs or dependencies changed in the meantime).
Great piece, Marko! CI/CD is one of the most powerful things to work on and to get right. But to get it right is really hard.
What I also experience is the difficulty in getting the implementation of CI/CD well known within the organization. I am one of the few who do maintain our pipelines and understand how to work on it. So, writing and documenting the implementation of CI/CD is good for future employees and people who never worked on it.
I like the usage of the twenty minutes rule. It also forces you to keep changes small, and let the process of delivery be short.
Would there be a manual check in a Continuous Deployment process? We always do a last check before going to production.
Thank you!
Technically if you have a manual check it’s not “Continuous Deployment” but if it goes fast it doesn’t make much of a difference in my view.
Btw, on the difficulty that you describe, is it about getting devs to collaborate on configuring the pipelines for their projects, or something else?
Great breakdown and explanation of CI/CD Marko! I enjoyed reading about how the two differ and then how the two can coexist. Thanks for sharing your knowledge on the subject.
If you have any sort of branching then you are not doing CI, you are doing promiscuous integration but not continuous integration.
I’m aware of this ideology but I think that branching has too many practical and psychological benefits. :)
I’d be curious to hear how it works in practice with a specific project and team.
If you merge multiple times per day, it implies that average lifetime of branches is less than a day, and that’s as continuous as you can do imo.
Branching generates a lot of integrational and operational cost to the software development process.
why branching on git is wrong
Adrián Norte ・ Oct 27 '18 ・ 1 min read
In there I explained my point of view.
Do you mean it's better to work on
masterand/or a monorepo approach?yes, absolutely.
Gatsby + Netlify: netlify is linked to the git commit, as soon as I commit the repo, it appears on Netlify. Trigger deploy -> job done. I like the sleek workflow like this.
For that kind of a project, that’s a perfectly fine setup!
abusalem.dev - just launched a months ago