CICD should be boring and run anywhere

Continuous Integration and Continuous Delivery can be a pain point in the development workflow. We’ve all done it, we’ve searched for “how to run TravisCI/GitHub Actions/GitLab CICD on my local machine” with the typical dismal results. We’ve had times of frustration as we push commits repeatedly just trying to appease the build system to pass our tests. Stop banging your head and start building your CICD actions to run in any environment, especially locally so we can skip the commit-push-wait feedback loop. If you’re interested in saving time and resources in your CICD systems join us for a dive into how to build workflows that provide value and not just failed builds! We’ll explore options and show examples of migrating an application to run everything locally just as it would in CICD.

Comments

Comments are closed.