Microsoft Is Mobilizing DevOps – Redmondmag.com

Microsoft Is Mobilizing DevOps – Redmondmag.com

Advanced Search
In-Depth
How a focus on DevOps is helping Microsoft win the loyalty of incumbent dev shops as they move increasingly to mobile app development.
Delivering apps in the enterprise can be an exercise in grenade throwing. Developers throw their code over the wall to testers, who toss it back for updates to developers, who pitch it over another wall to operations for deployment and maintenance. The process can be inexact, unrefined and fraught with conflict. But with the rapid shift toward mobility, cloud and consumerized IT, enterprises find they must be more responsive to constituencies and customer bases. From governments and schools to businesses of every kind, the focus on agility has prompted an effort to bring IT operations and developer organizations together, through a model described as DevOps.
Over the past two years, Microsoft has urged organizations to join it in shifting to a DevOps model. The company has been — to repeat a phrase used by Redmond over the years — eating its own dogfood as it applies DevOps practices to the development of products such as Windows, Office 365, Azure, SharePoint and its Visual Studio developer tools. Now the effort is extending to mobile, as Microsoft aims to persuade organizations to center their cross-platform, mobile app development and management activities around Microsoft tooling and practices.
The push comes as mobile apps emerge as an area of strategic concern for enterprise IT organizations. In the Enterprise Mobility Suite (EMS), Microsoft has delivered a well-regarded tool for cross-platform, mobile device and app management, with the company claiming the product as its fastest-growing offering ever. Another shoe dropped earlier this year on Feb. 24, when Redmond announced an agreement to buy cross-platform tools and platform maker Xamarin for $400 million — a deal that drew a collective cry of “What took you so long?”
That’s what Eric Shapiro, founder and CEO of ArcTouch, now a unit of global media agency Grey Advertising, said back in March (bit.ly/1sN8ihb). “I’ve been predicting for over a year this would happen,” said Shapiro, whose mobile creative design and app development shop builds apps for large consumer brands such as Audi of America, CBS, Salesforce.com Inc. and Yahoo! Inc.
After all, Microsoft had long encouraged Xamarin in its effort to provide software for developers using the Microsoft C# programming language, enabling native code that can run conveniently across Windows, Mac OS X and iOS, Android, and Linux. The acquisition was an urgently needed win for Microsoft in the mobile app arena. The company’s Windows Phone platform has languished behind Apple iOS and Google Android, with Microsoft just last month writing off its $7.2 billion acquisition of the Nokia handset business in 2014. The struggles risk eroding Microsoft’s dominance in the businesses sector, as growing ranks of mobile programmers targeting iOS and Android learned to live life completely free of Microsoft.
That changed when Xamarin came on board.
“Microsoft smartly recognized the role of mobile in the software development process and saw that it is becoming strategic,” says Al Hilwa, program director for Software Development Research at research firm IDC. “It is interesting that the very weakness of [its] own mobile platform could result in early traction in [the company’s] cross-platform approach.”
Microsoft was quick to strike while the iron was hot. At the Build conference in San Francisco in March, Scott Guthrie, executive vice president of the Microsoft Cloud and Enterprise Group, announced that Xamarin would be made available for free in every version of the Visual Studio integrated development environment (IDE). He also announced that access to the Xamarin Studio IDE, used by many incumbent Xamarin developers, would be included with Visual Studio license subscriptions. The move eliminated one of the top barriers to entry for the Xamarin tool suite — its cost.
The DevOps Directive
Analysts expect the acquisition to lift Microsoft’s profile among mobile programmers, particularly in IT shops where traditional client and server development is aligned with the Microsoft .NET Framework and C# programming language. Just as important, the Xamarin buy completes the Microsoft DevOps tool chain that allows organizations to manage the flow of work, code and assets during software development, from initial planning to distribution of applications and beyond.
DevOps, of course, is short for developer/operations and describes the effort to improve software development and delivery by redefining the relationship between development, IT and end customers. Steeped in Agile practices that value decentralized organization and iterative processes informed by constant feedback, DevOps leverages tooling, practices and cultural alignment to speed and improve software delivery. It may sound like a mouthful, but DevOps is taking off.
Research firm Gartner Inc. targets 2016 as the year when DevOps goes from niche movement to mainstream, with one-quarter of Global 2000 organizations expected to adopt DevOps practices. An earlier 2014 Gartner report projected strong growth in the DevOps tool sector, with spending set to rise more than 20 percent from $1.9 billion in 2014 to $2.3 billion last year.
A key driver of the uptake: rising infrastructure complexity and the heightened pace of work enabled by cloud services and business models. Software assets that in the past were updated once or twice a year, and packaged for distribution to users, now are being updated on monthly or weekly schedules and automatically pushed to client systems. Traditional waterfall processes, with their emphasis on extensive pre-planning and scripted action, are poorly matched to the new cadence.
Now, says IDC’s Hilwa, enterprises are starting to incorporate DevOps into mobile app scenarios.
“We are seeing increased initiatives in larger enterprises, which show that they have begun to take mobile development more strategically and approach it more systematically,” he says. “The reality is that DevOps is still in the early stages of adoption in large enterprises, with most of them practicing it only in new projects and with Center of Excellence or Transformation Center teams often set up to handle the disrup­tion they’re expecting.”
The tooling that enables DevOps reflects the nascent character of the sector. IT organizations often assemble tool chains from a mix of commercial and open source point solutions. Promising startups and incumbent pure-play vendors vie for market share as large providers fill out their portfolios with timely acquisitions.
“It is early days, in fact, very early days, in the DevOps end-to-end tooling world. I think companies like Microsoft and IBM have made great investments, but there are other strong players that have strong holds on other parts of the space and are actively investing,” says Hilwa.
Plumbing the Microsoft DevOps Stack
The Microsoft DevOps story is supported via the twin suites of Visual Studio Team Services (VSTS), which is cloud-based, and Team Foundation Server (TFS), which is on-premises. These solutions provide a collaboration hub that comprises the end-to-end tool chain, from management of the code base to the release and monitoring of finished applications. IT organizations have the option of swapping in specific point solutions, for instance replacing Team Foundation Version Control (TFVC) with Git, or the integrated Xamarin Test Cloud device testing service with Perfecto Mobile.
What goes into an end-to-end DevOps tool chain on the Microsoft stack?
Microsoft has been busy burnishing its DevOps infrastructure, rebranding the former Visual Studio Online (VSO) cloud solu­tion as VSTS and establishing feature parity between VSTS and the on-premises TFS suite. The company has also worked to extend support beyond the .NET Framework to enable full cross-platform coverage.
Donovan Brown is a DevOps senior program manager at Microsoft. He says the focus of the VSTS and TFS teams can be boiled down to four words: “Any language, any platform.”
“I literally say that every day of my life, because I want to make sure that everything that we produce works for any language and for any platform,” Brown says. “And any platform includes iOS, Android, Windows Phone, Xbox, you name it. If you can write for it, I want to make sure Visual Studio Team Services is the best tool and the best product to get you there.”
That commitment can require some gymnastics. Developers targeting Mac OS and iOS, for instance, have no choice but to build and compile their applications on Macintosh hardware. To address the limitation, IT shops must register Mac OS systems as build agents inside the VSTS environment.
“When we identify we’re building an iOS or Xamarin application targeting iOS, we are able to then use that Mac to go perform the compilation for it, and then distribute that using HockeyApp,” Brown explains. “As soon as we go to build it, that’s the first time you realize that, OK, this is a special scenario, different from any other type of development, because I might need to use a specific piece of hardware to perform that compilation.”
Microsoft cited progress on enabling phishing-resistant authentications for organizations, in a Friday announcement.
Microsoft this month activated the OneDrive App for Teams for users of the “new Microsoft Teams,” per a Thursday announcement.
Break the habit of single-serving scripts to avoid unnecessary work.
Microsoft this week has made available the latest version of its suite of small language models (SLM), Phi-2, in the Azure AI Studio model catalog.
Windows 10 and Windows 11 users in the European Economic Area will be getting a new single sign-in notice, starting in January.
20 Easy Steps To Creating an AI Chatbot in 30 Minutes
The Definitive Ransomware Checklist Summit: REGISTER NOW!
NOW AVAILABLE ON DEMAND: Cloud Data Threat Outlook Summit
&#10006
Subscribe on YouTube
More Summits
More Webcasts
More Tech Library
Problems? Questions? Feedback? E-mail us.

source