-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add content for "How do we CD with a mud ball?" #200
Comments
i think this would be a great thing to have experience reports for |
Creating a high level recommendation path to dig out from the hole many teams are in, I think that could help many . |
I'm going to write an article about this, because I get this question constantly, and I'll link it over here. |
Any updates on that article? :) |
I agree that this is an experience report as well as high level recommendations for addressing this. It is HIGHLY prevalent in my world. @bdfinst - Glad to coauthor or be a feedback provider. |
Discussed in #199
Originally posted by rlabercrombie April 15, 2022
Given the latest presentation at devnexus (great job by the way!) there were a few questions about 'how to get there' with tough architectures; in this example they mentioned having to have a many year long process of transitioning from VMs to x/y/z prior to being able to achieve (or it sounded like even start) minimal cd.
Would there be any interest in creating a new section or adding to existing sections for use-cases fitting the bill of 'getting to a minimum viable cd system: best practices (or examples... whichever would fit best)?
As an example of a use-case: You have a monolith with zero testing coverage. Separating out a small chunk of code - ideally on an appropriate domain/business seam - into its own project, adding some unit (or other) tests and getting a basic pipeline working as a way of an iterative process? Then you could have parallel work on improving that pipeline and pulling off another small chunk of code.
Or is this out of scope?
The text was updated successfully, but these errors were encountered: