Skip navigation

Developer Community

3 Posts authored by: james.owen Employee

One Brick at a Time

Posted by james.owen Employee Apr 19, 2015

 

I like to say that the wall between Dev and Ops is built by many masons, over many development cycles. Most individuals start their new company, product, or service with agility in mind. Time to market is a top priority – Process that increases lead time is minimized.

 

Then a mistake happens and a brick gets mortared in. Dev gives Ops a bad build. Ops upgrades a server that accidentally impacts a critical business service. New site content makes it all the way to Test, but is skipped in a manual deployment step to production.

BangHead.jpeg

 

 

 

Often the mistakes are embarrassing, but sometimes they can be disasterous.

 

Pretty soon more insults than bits are hurled over the wall and heads start banging.

 

 

 

 

 

Everyone recognizes the wall needs to come down, but like the Winchester Mystery House, understanding why some of the bricks are there and how to remove them can be baffling.

thehouse.jpg

 

 

At ServiceNow, we’re on a mission to help DevOps teams remove bricks from the walls and better enable agility with governance. This week at Knowledge 15, we’ll be sharing our current process and automation solutions, as well as a sneak peak at our Continuous Service Delivery vision. Please stop by the “Future of Now” booth, help us better understand your DevOps goals, and learn more about our road ahead.

XOdYg11ZAMno.png


That's what our recent webinar with over 500 attendees proclaimed. And based on the feedback we received during the event, there is strong agreement! Unfortunately, we couldn't get to all of the questions submitted so we plan to re-post them here, to the Creator Community. If you have additional questions on the topics covered (or any question we missed), please post and we'll do our best to ensure a response. Thanks!

Join the Discussion


There is an "I" in "TEAM"

Posted by james.owen Employee May 22, 2014

George Takei posted this fan's drawing a while back, pointing out the hidden “i” in “TEAM”. And if you take a closer look at Team Development, you’ll find another hidden I. (Not all features require a team!)

Team.png

The ability to compare instances is one such example. Let’s say you follow the standard process for retrieving update sets through to production, usually. You know that making changes directly in production is frowned upon, but you’ve had high priority, low risk fixes where you’ve bent the rules. Could your production instance have updates that aren’t on your development instance?

Compare.png

Now there’s a simple way to find out! From development, add a remote instance to production. From the Team Dashboard, choose “Compare to…” and select your production instance.


Team.png

You’ll then get a list of changes on production that aren’t on development, and the changes on development that aren’t on production as well.

 

Voila, no team required!

 

Screen Shot 2014-05-22 at 9.06.44 PM.png

Filter Blog

By date: By tag: