/explore
|
You are here 
|
continuousdelivery.com | ||
| | | | |
blog.flurdy.com
|
|
| | | | | Continuous Deployment via Stack Overflow | The ramblings and ranting of Ivar Abrahamsen at flurdy.com. | |
| | | | |
agiletester.ca
|
|
| | | | | In Part 1, we showed how the quadrants can guide conversations to plan testing activities that support continuous delivery (CD). What about other tasks to support CD, like building a deployment pipeline? | |
| | | | |
blog.coryfoy.com
|
|
| | | | | [AI summary] The article outlines a software development workflow that moves from initial idea clarity to high production confidence through automated testing, integration, and deployment cycles. | |
| | | | |
mikecoats.com
|
|
| | | A common time-saving 'hack' of mine when building 'new-but-related-to-old' projects is to fork an existing code base and use it as the boot-strap for the new project. GitHub, however, does not provide the functionality on their website to fork your own project; you can only fork other people's projects. Here's how to work around that. | ||
