For as long as people have created and run software, the two sides—build and operations—have worked at cross-purposes. Developers want to go fast and deliver more frequently, while operations teams need to ensure the releases are secure, adhere to governance policies, and are available.
DevOps attempts to bridge those worlds, by empowering developers with more self-service capability; but this creates islands of ad hoc infrastructure creation that IT must deal with. Throughout a continuous software delivery lifecycle the infrastructure is fluid, and can change at each step, demanding it is understood, tracked, enabled, and managed safely and seamlessly by all DevOps team members—from agile planning through to production and back.
Join David Williams of Quali in a discussion on how organizations can find commonality between the build and run efforts, and how automation technology can help.
"The flexibility of CloudShell Colony and AWS has not only allowed us to innovate our solutions faster, but it also allowed us to build on top of the Colony software. Now, our developers can use a Slack integration that we built to reserve the dynamic application environments they need for testing all without the need for our DevOps teams to disclose sensitive passwords. This has resulted in reduced time to market, more productivity, and better visibility into our cloud usage."