Jenkins • Continuous Integration • Continuous Delivery • Build Pipelines

Embracing failure by virtue of A/B split testing


YourAvatar-5

Pushing the envelope, and thinking outside of the box by navigating uncharted waters is how the human species innovates. Undoubtedly some attempts to innovate have less than stellar results. Some attempts fail in the most spectacular ways (think the Hindenburg). Others simply sputter out (but still fail)… But every once in a while an attempt succeeds and innovation inches foreword. One of the more recent examples is the notorious SpaceX rocket landing attempts. Conducted in June of 2015, the first attempts at landing a SpaceX rocket failed spectacularly. With a determination to succeed and willingness to innovate the SpaceX team would eventually pave the way for a monumental success. In December of 2015 SpaceX safely landed a rocket on a landing pad, thus creating the first reusable rocket in history. […]

READ MORE

Continuous Integration within the software industry


YourAvatar

The state of Continuous Integration & adoption within the industry. Implementing Continuous Integration [CI] at an enterprise software organization can be just as controversial as it is valuable. The CI engineering paradigm colloquially aspires to increase software release quality through frequent code integrations (merges), smaller batch sizes, and immediate feedback surrounding changes introduced to a software system. Arguably the most controversial segment of CI surrounds development personnel and their religious views of branching patterns. Developers can be fairly cranky when it comes to fundamental alterations in the way they work. Motivating strong-minded individuals who are introverted and shy to communicate more and expose risk earlier is no easy feat. The concept of CI received numerous accolades and realized significant traction soon after it was introduced as a development best practice […]

READ MORE

Security and Compliance VS DevOps


YourAvatar-6

How can you bake-in security and compliance into your DevOps processes, and how can DevOps and automation help you pass your next audit? Last Tuesday I participated in an online panel on the subject of Security & Compliance as part of your DevOps Processes, as part of Continuous Discussions (#c9d9), a series of community panels about Agile, Continuous Delivery and DevOps. Watch a recording of the panel: Continuous Discussions is a community initiative by Electric Cloud, which powers Continuous Delivery at businesses like SpaceX, Cisco, GE and E*TRADE by automating their build, test and deployment processes. Below are a few insights from my contribution to the panel: Dev-QA-Sec-Ops: Best Friends Forever Now? “In some cases I think there’s been a lot of strides made in the direction of collaboration. In […]

READ MORE

DevOps Packaging – A Measure of Collaborative Efforts [ContinuousAutomation.com]


YourAvatar-5

Deploying a final release to production is a huge achievement in software development. It represents a final delivery to the business and the beginning of business value (Return on Investment [ROI]).  Developers at this point usually get to breathe a sigh of relief and often times take a moment to reset the proverbial factory line. For operations and technical support a release represents the beginning of their efforts.  The moment software is deployed and clients begin using it marks the visibility for bugs and defects increases. This can be a stressful time for the people who are supporting, selling and maintaining the software r elease.  But does it need to be? From engineerings perspective, the deployment was successful (zero return code), so software/platform must work right? Not so fast! While obvious to most […]

READ MORE