We are delighted to have been recognized as a leader in Enterprise Service Management in Research In Action Selection Matrix.
Of particular note, the report emphasizes how Serena differentiates in realizing the importance of integrating Application Lifecycle Management and ITSM processes for the future of IT Service Management. For many years, we have seen
If you didn’t see the news yesterday, our friends at CloudBees, the enterprise Jenkins company, announced further strengthening of their partner program to delivery continuous delivery success to software development and IT organizations around the world.
Errors do occur. They occur for a reason. Often those reasons are out of our control. Someone changes an IP Address of a server. Someone changes the password to the back office system. Someone changes the name of a shared .DLL.
Of course in a well-managed and carefully controlled environment those kinds of things shouldn’t happen without the proper authentication, notification and approval. And the infamous “someone” is a responsible professional who calculates the impact of their changes and collaborates with everyone to minimize that impact. In a perfect world.
In the real world change is constant and calculating the consequences of change
Helicopters have been described as “10,000 parts flying together in close formation. It is the mechanic’s job to keep that formation as tight as possible.”
Modern software applications comprise of millions of parts when you consider the huge chunks of code we bind into our applications from the database, security, web server, communications, encryption and authentication vendors. Add to that the seemingly infinite numbers of dependencies on external web services and internal CRM and financial systems.There are 100 million lines of code in the Ford Taurus
But, just like the helicopter’s mechanic, the
“I don’t want to know why it happened: I just want you to fix it!” was what I was told early one morning by the Director of Sales. And she was right: getting the online store back online was the most important thing for the business. Blamestorming would come later.
There is a temptation at 3:00 am to just do whatever it takes to bring the system back on the air even if that means bypassing protocols and procedures designed to protect system integrity. Sales-and-Marketing and Audit-and-Compliance might not see eye-to-eye on this approach.
So why do emergency fixes have to be different? This myth is all about time. The time it takes to write the script.
I’m excited to announce that we’ve made Serena Deployment Automation free for everyone…and free forever. The Community Edition provides full product functionality with deployment to 5 virtual or physical servers. You can add more end points for the new low price of just $1,499.
You can learn more about Serena Deployment Automation and download the Community Edition for free at www.serena.com/freedeploy.
So, let’s get to the why, what and how of it all…
The exciting news of the day is the immediate availability of the Community Edition of Serena Deployment Automation.
If you want to simplify and automate software deployments, then download the Community Edition of Serena Deployment Automation. By the end of the day you’ll be enabling continuous delivery for your dev teams and production deployments for your ops teams. You’ll be enabling the deployment pipeline and reducing cycle times faster than you thought possible. With Serena Deployment
In the last post we talked about some of the myths about release and deployment. Perhaps the most telling comment there was the belief that “Every deployment is unique.”
Let’s break that apart and see what it really means and why it just doesn’t hold up in reality.
Deploying an application comprises of a number of parts: