GITFLOW ISN'T COMPATIBLE WITH CONTINUOUS DELIVERY | Bryan Finster On CD and Gitflow's Definition
ฝัง
- เผยแพร่เมื่อ 1 ต.ค. 2024
- Bryan Finster talks about how he got Atlassian to CHANGE GITFLOW'S DEFINITION to admit that it is incompatible with Continuous Delivery.
This is a clip taken from Bryan's FULL Engineering Room episode, watch HERE ➡️ • Continuous Delivery vs...
--------------------------------------------------------------------------------------
⭐ PATREON:
Join the Continuous Delivery community and access extra perks & content!
JOIN HERE ➡️ bit.ly/Continu...
-------------------------------------------------------------------------------------
👕 T-SHIRTS:
A fan of the T-shirts I wear in my videos? Grab your own, at reduced prices EXCLUSIVE TO CONTINUOUS DELIVERY FOLLOWERS! Get money off the already reasonably priced t-shirts!
🔗 Check out their collection HERE: ➡️ bit.ly/3vTkWy3
🚨 DON'T FORGET TO USE THIS DISCOUNT CODE: ContinuousDelivery
_____________________________________________________
📚 BOOKS:
📖 Dave’s NEW BOOK "Modern Software Engineering" is available as paperback, or kindle here
➡️ amzn.to/3DwdwT3
and NOW as an AUDIOBOOK available on iTunes, Amazon and Audible.
📖 The original, award-winning "Continuous Delivery" book by Dave Farley and Jez Humble
➡️ amzn.to/2WxRYmx
📖 "Continuous Delivery Pipelines" by Dave Farley
Paperback ➡️ amzn.to/3gIULlA
ebook version ➡️ leanpub.com/cd...
-------------------------------------------------------------------------------------
🙏The Engineering Room series is SPONSORED BY EQUAL EXPERTS
Equal Experts is a product software development consultancy with a network of over 1,000 experienced technology consultants globally. They increase the pace of innovation by using modern software engineering practices that embrace Continuous Delivery, Security, and Operability from the outset ➡️ bit.ly/3ASy8n0
Gitflow is a legacy Git workflow. Who even uses gitflow in 2023?
Someone in my org literally found gitflow for the first time a few weeks ago and put a message saying how great it looked and how we would increase velocity so much if we used it, even though we already use CI, for a saas product. The cherry on top was that they linked to the atlassian article on it that calls it a legacy workflow and was documented for historic purposes.
They weren't even trolling, they really argued for it at length.
@@georgehelyar You'd be surprised! I often get people asking if they should adopt it.
@@georgehelyar I worked with a friend of mine who had joined Atlassian recently to get that edit in. 🤣
I've met too many people dead sure that GitFlow is considered "best practice" and not following it is "breaking the rules" and a sign of "chaotic, unorganized process".
@@w__m when bad things are well documented, they can look good. The diagram should be a giveaway though.
Is this a response to theprimegean video?
No, but it may be a "reaponse". Sorry, I couldn't resist.
i thought the same, as i saw Dave commenting in that videos comment section 😅
@@animanaut really? I have to check on that. I do think that Prime missed the point in many ways but one thing he said that I do agree is that CD burns out cash faster since users often need to download a new bundle from the CDN.
What response? Prime does zero research hot take twitch streams. Imagine a civil engineer watching a video of a guy who has build a lot of bridges pointing out process issues, and therefore that civil engineer makes a zero research flow of consciousness reaction video. He would be shred to pieces by the profession. But not on software youtube…. Zero science, little engineering and lots of kids.
Probably :)
I'll admit to having been a bit worried that my platform doesn't support Gitflow. Not because I think my platform needs it but because too many developers swear by Gitflow, so it'd be an added task to get them to see the world differently. However, I plowed ahead with what works for my CD model. Gitflow worshipers be damned. So, this video is has been yet another validation for me. Thanx again, Dave!
When we built a central platform at Walmart in 2016, one of the product goals was to incentivize CD workflows. You could force the platform to use GitFlow, but it would be constant toil to do so. To this day, some teams still request better GitFlow support from the platform. The response continues to be, "that's not on our roadmap." 😂
@@bryanfinster7978 😅!
3:05 eh, Atlassian have not changed their definition, they *still* write that:
"Gitflow can be used for projects that have a scheduled release cycle and for the DevOps best practice of continuous delivery."
Where? Their GitFlow page has an update at the top to not use it.
the problem is, it sounds good and may be even a good starting point ... at first. but once it is in place it is really really hard to get rid of
hey i follow this channel as a hobby (i program for fun), and wondering if you could let me in on the inside joke? like i know what CD is about, it's mainly about minimizing conflicts and getting people on the same page just about as soon as the code is written.
@@Layarion i was referring to gitflow with my comment, not CD. in bigger or sometimes even in smaller teams you always will find that some people don't like change that much. established processes are just hard to get rid of sometimes. this is more a social than a technological challenge sometimes. try to argue to lower the amount of code reviewers needed for an approval if you need a challenge :D you can bring up all logical reasoning to the discussion and some will still insist it is too big of a risk to try
@@animanaut in trying to understand what the joke about gitflow is
@@Layarion sorry, i'm not getting it. what inside joke are you refering to exactly?
Your mum is not compatible with continuous delivery. After she had you, she decided to stop.
Child.
The only issue i have with continues delivery is that when people branch out make a feature then delivere buy never return to master.
Then instead of maintain 1 software you suddenly have 10 to 20 variations of that software.
Maybe they should use CI/CD, instead of whatever it is that you would call what they are actually doing.
That isn't CD! CD is "Working so that your SW is always in a releasable state" it isn't really in a releasable state if it omits bug fixes.
So my analyst and I decided to change how we do things without asking permission..... now we start with writing tests rather than finishing with him performing manual QA..... but the fukn thing is the goddamn team just hired a fukn release manager WTF
lol
i understand the test thing, what is a release manager? asking as someone who's never had a programming job
@@Layarion basically what they do is organize jira epics/tickets and create a new epic for a scheduled release and they'll have all cards that were worked that go into the release attached, and they make sure all the work is in the appropriate environments and such. It's a bunch of vogon shit.
Btw there are github repos and also sql scripts that need a special request made to the database team, because we don't have schema update perms for prod env