Whenever the words “Continuous Delivery” and “Enterprise IT” are used in the same sentence it rapidly turns into a page or at least a paragraph. That is because “Enterprise IT” generally means a big, diverse set of heterogeneous infrastructures glued together across many teams and locations that use many different tools and processes to develop and deploy software. Each enterprise has its own unique DNA that has organically evolved through generations of applications and technologies with its own historic set of artifacts and
DevOps is something that is talked about frequently but what does it really mean? How would you react to the folowing statements and questions?
What if I said all of the above were at least partially true?
Now that you are
In February, Infrastructure as Code takes center stage in Europe. On February 3rd and 4th in Gent Belgium there is a Configuration Management Camp. As expected the leading providers of infrastructure as code solutions will be there. There is a lot of innovation in this space and these solutions fit in nicely with
Last week I was at DevOpsDays Portland. As expected, the open space topics were really interesting. Two in particular stood out for me. The first was about fitting DevOps into your organization. DevOps teams seemed to be the way people were going. If you have been to other events with prominent figures of the DevOps community present, you may have noticed how the mention of “DevOps teams” can spur heated
Recently I attended a workshop hosted by Dominica Degrandis on using Kanban in an organization working in a DevOps-like manner. The workshop was full of practical advice not only on why Kanban can help you but also on how to be successful in your implementation. Attendance was good; people came from the east coast to attend what I thought was a local workshop.
As we discussed things that we had each tried in our organization, it became apparent that some of us had
This is my first time attending the tutorial day at a Velocity conference. It’s a small world as I’ve already met someone I met at DevOpsDays Atlanta and a couple of people I met at a Kanban for DevOps workshop back in Santa Clara a few weeks ago.
The first session of the day covered using Jenkins in operations. I’m a big believer of using the right
I am on my way back from DevOpsDays Atlanta. It was the first DevOpsDays event in Atlanta and most of the attendees had never been to a DevOpsDays before. As Serena is supportive of the DevOpsDays events I’ve been to a fair few now and I was starting to see the same faces and topics over and over.
I recently read a fantastic article by Jens Segers on infrastructure as code. I’m already a big believer in infrastructure as code and agree with Jens that it doesn’t matter which tool you use as long as you strive to have an infrastructure as code initiative.
That leads to an interesting question. Where do infrastructure as code tools such as Puppet or
Last week I had the pleasure of working in the Serena booth at Agile2013 (me and a Shania Twain look-alike in picture to the right). While there were quite a few booths, some very creative, it was a fairly low energy expo area. That doesn’t mean we didn’t have some great conversations.
Agile2013 had a DevOps track. There were plenty of people who stopped by our booth who wanted to learn more about DevOps. They were
I’m going to open with a fact that should hopefully be obvious: Few organizations have a completely manual software release process.
I can imagine you saying things like “Duh! So what? What’s your point?”
The fact that partial solutions to software release problems are already in place poses an interesting problem for software vendors. Some vendors pursue a policy of attempting to replace existing tools with their own products. Others, including Serena, believe in co-existing with and adding value to solutions they have already invested