Bringing Valuable Information to DevOps Professionals

DevOps Journal

Subscribe to DevOps Journal: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get DevOps Journal: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


DevOpsJournal Authors: Automic Blog, Elizabeth White, Dalibor Siroky, Mehdi Daoudi, XebiaLabs Blog

Related Topics: IT Strategy, DevOps Journal

DevOpsJournal: Article

Jenkins World 2017 Musings

Jenkins World 2017 Musings

Read the full, original post here.

Jenkins World happened recently in San Francisco.  It was good to see familiar faces and meet new friends.  The exhibition hall was busy all day long with lively conversations at every turn.

As the baseball season heads into September and the scramble for the playoffs heats up, Yogi Berra comes to mind.  Some of his classic sayings apply to our experience at the conference.

Here are a few of our observations from watching the activity at Jenkins World:

People want more

While Jenkins is the de facto tool for continuous integration, and, it appears, the attempted de facto tool for continuous delivery and release automation, the vast majority of attendees are looking for more from their efforts: More control. More visibility. More auditability. Etc.  Those demands came from DevOps managers as often as they did from Jenkins administrators.

Apparently, adding more scripts, more instances, and more plug-ins doesn’t solve all the problems of getting high-quality software to market in a timely manner.  Being able to reliably automate more steps in the process, immediately knowing the value of software in the pipeline, having a compliance audit be little more than a couple clicks, etc., is still a long way off for many Jenkins shops.

People want less

n theory, the whole point of automating development and operations is to eliminate bottlenecks, errors, etc.  Yet, based on comments and questions by attendees, the practice hasn’t been all that successful.

One DevOps manager from a shop with multiple Jenkins masters, about 20 development teams and “lots” of scripts admitted that managing the whole affair was a major pain in his Anterior Spinal Section.  He wanted less pain, fewer errors, and less time chasing up problems.  In his shop, jobs that fail are automatically restarted ad infinitum and get logged.  Reports are handed out at the weekly stand up meetings with directives to “go fix your broken Stuff Hindering Impending Triumph.”  He wasn’t alone.

 

Read the full, original post here.

More Stories By Anders Wallgren

Anders Wallgren is Chief Technology Officer of Electric Cloud. Anders brings with him over 25 years of in-depth experience designing and building commercial software. Prior to joining Electric Cloud, Anders held executive positions at Aceva, Archistra, and Impresse. Anders also held management positions at Macromedia (MACR), Common Ground Software and Verity (VRTY), where he played critical technical leadership roles in delivering award winning technologies such as Macromedia’s Director 7 and various Shockwave products.