Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 2
    +1, the key to cd isn't git or your gitflow but CI and delivery workflow. Commented Aug 15, 2014 at 12:51
  • Thinking a LOT about this. Thanks for the insight. FWIW, I specifically avoiding using the term CI because we don't use CI. Maybe we should, but we don't, it's just too cumbersome for the dozens of projects we work on in a given week, some short term, some long term. Commented Aug 15, 2014 at 21:53
  • 2
    @jb510 -- we've got a similar project setup, I would not dream of flying it without CI. Switching contexts is alot easier when all the dumb but fragile parts are scripted. Commented Aug 22, 2014 at 17:56
  • 1
    Sometimes, inability to implement CI easily is a sign of how much you need CI on a project. No unit tests? Deployment all manual? Lots of fiddly deploy steps? Needs examination. Commented Aug 10, 2015 at 15:14
  • 1
    I've followed this question and answer over the years. I'd hoped others would offer answers as well, but this is itself a great answer so finally marking it accepted (probably should have done that a long time ago) Commented May 23, 2017 at 3:04