post-img

Quali Chalk Talk Session 01 – Sandboxes and CI/CD Tools

Posted by admin September 23, 2016
Quali Chalk Talk Session 01 – Sandboxes and CI/CD Tools

Welcome to our first of many Quali Chalk Talk Sessions! Quali's Chalk Talk Sessions aim to give you a deeper technical understanding of Cloud Sandboxes. In these sessions we'll explore various aspects of Quali's Cloud Sandbox architecture, how Cloud Sandboxes integrate with other DevOps tools, and provide tips and tricks on how you can effectively use Sandboxes to deliver Dev/Test infrastructure faster. We hope these sessions help you on your DevOps Journey!

In this Session we'll hear Maya, our VP of Product, talk about integrating Quali's Cloud Sandboxes with CI/CD tools like Jenkins Pipeline.

 

post-img

DevOps is a Journey, Not a Destination

Posted by admin September 22, 2016
DevOps is a Journey, Not a Destination

DevOps purists will tell you that you are not doing DevOps unless you are implementing full continuous deployment.  On the theoretical level, this has always rankled me because DevOps is a practice that is based on LEAN theory, which is really focused on continuous improvement.  So, wouldn’t a DevOps purist be focused on continuous improvement rather than reaching some “endpoint”?  In other words, it’s not about the destination, it’s about the journey.

But, I didn’t think that a theoretical argument really mattered.  It wasn’t until my colleague Maya Ber Lerner and I had the opportunity to speak at a couple of DevOps conferences this summer that we realized why the DevOps purist argument is so dangerous.  At each conference, we were besieged (in one case, an audience member grabbed my shoulders and shook me while saying “thank you”) by participants after speaking because we talked about why continuous testing is so difficult and why so many companies struggle with, and may never really achieve continuous deployment.  It was as if people were just happy to hear SOMEONE telling it like it is, and still encouraging them to continue with their journey toward DevOps.  In addition, the speakers who were the most popular were from companies that everyone believes have achieved DevOps nirvana – like Facebook and Netflix.  These speakers were talking about DevOps as their journey and in every single case, they talked about their continuing efforts to improve their processes, even after 5 years or more of working on DevOps.

So, the idea that you can’t be doing DevOps unless you are implementing perfect automation from the first line of code to deployment into production is just plain wrong.  Every company needs to deliver software faster – and every company is a software company nowadays – so they all need to work on DevOps.  But any step forward toward DevOps practices and automation will result in improved speed of delivery.  And the next step will result in more speed of delivery.

So, DevOps purists be damned, let’s all just get started with DevOps.  Because the journey will never end and it doesn’t have to.

post-img

DevOps Best Practice #1: Combining Continuous Integration with Cloud Sandboxes

Posted by admin September 14, 2016
DevOps Best Practice #1:  Combining Continuous Integration with Cloud Sandboxes

I have run the continuous integration demo so many times in the last couple of weeks that I am starting to dream about continuous integration!  So, I thought it would be good to share the wealth!

Continuous integration (CI) is the DevOps practice of running a set of regression tests automatically frequently during the development process – typically every time that new code is committed.  One of the most popular CI tool is Jenkins.  Jenkins allows users to describe actions that they want to be taken automatically whenever an event happens – like a commit of new code.

The only problem is that these automated tests would usually run in a test lab where the configuration of the environment would often be designed to look closer to the production environment than a typical development environment.  So, the challenge is:  How to also automate the infrastructure configuration that tests should run in and trigger that configuration along with the tests as part of a continuous integration process that runs every time new code is committed.

This is where Cloud Sandboxes come into the picture.  A cloud Sandbox allows the creation of a configuration that replicates the production environment – from the network to the virtual environment to apps and even public cloud interfaces.  This configuration can be set up automatically and on-demand.  Quali’s CloudShell product is a cloud sandbox that can be created via our RESTful APIs.  This allows sandboxes to be integrated with continuous integration tools like Jenkins and Travis so that a sandbox is triggered first and then the tests are trigger to run inside of the sandbox.

If you'd like to download the Jenkins plug-in, it's available on the Quali community:

http://community.quali.com/repos/548/cloudshell-pipeline-plugin-for-jenkins.html

jenkins-2