Once the developer checks in a change, how long does it take your organization to deliver it to the customer? The path to production can take many turns, have many dips, and fall short in terms of quality and expectations. IT organizations struggle with major process and toolchain gaps between develop, build, deploy, and release. Come join us at the December Serena DevOps Drive-in as Julian
We are looking for new and innovative uses of Serena Deployment Automation Community Edition and are announcing a new contest with a chance for a $1,000 Amazon gift card!
The world of configuration management is no longer just about servers in the data center. It is rapidly expanding and supporting other environments including cloud, mobile devices, embedded devices, BYOD and devices in the car and home. All these environments need to be configured as a broader system tying into a business platform or application. Everything is growing and becoming increasingly pervasive,
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.
Deploying software in today’s enterprise environments is an extremely expensive and inefficient process. The cost in terms of resources, time and revenue lost is actually astounding. I was on the phone with a large insurance company recently that was struggling with high costs and time to market issues with their main retail application. Their DBAs were spending over 50% of their time manually deploying 3 releases a day.
Do you have high cost, highly skilled team members deploying software? It shouldn’t be that hard.
Serena has partnered with CloudBees, the enterprise Jenkins company, to bring you live full-day summits with industry experts on Continuous Delivery. The first four summits have been sold out and well reviewed.
Please join us at one of the upcoming summits in a city near you:
Like most jobs in life, preparation is the key to success. After getting to know the Serena Deployment Automation technology by working with the free version (download from the Serena website) for a few hours (see yesterday’s post) I decided it was time to try for real.
My application was a Library Management System I developed a while ago
“Drinking our own champagne” is how we approach technology here at Serena. If we have a our own tool that supports part of the application development lifecycle we use it for our own development efforts. In fact the Serena development teams deploy the beta versions of our solutions straight into their production environments because they want exploit the cool-new-stuff just as much as you do!
When I sat down today to start writing about automated deployment in modern enterprises I thought I’d follow the Serena mantra and “drink our own champagne” too. So I
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