devopsy.kinsta.cloud

Category: News

  • Mission, the New Nationwide Managed Cloud Services Provider, Launches Following Mergers of Reliam, Stratalux, and G2 Tech Group

    LOS ANGELES, October 10, 2018 – Mission, a managed services and consulting company for cloud platforms including Amazon Web Services (AWS) and Microsoft Azure, debuts today as the new company born from the recent mergers of AWS Partner Network (APN) Advanced Consulting Partners Reliam, Stratalux, and G2 Tech Group. Since these mergers, completed earlier in 2018, the combined organization has grown revenue sixfold, doubled its customer base to 175 enterprises, and more than tripled its headcount.

    Operating under the tagline “Mission – Let’s Achieve Yours,” Mission promises a uniquely immersive approach to understanding each customer’s specific cloud needs and long-term vision, and then expertly harnesses the power of the cloud to achieve those goals. Mission commands deep expertise in the architecture, migration, management, performance, and cost-optimization of cloud environments, and applies that acumen with a passionate belief in cloud technologies as the greatest tool for delivering effective and lasting business transformation. The result is a company that teams with organizations across industries to help them get where they need to go, and to help them develop more agile and more creative applications faster than ever.

    Building on the foundation of three well-established and thriving cloud service providers, Mission now features coast-to-coast geographic coverage with offices in Los Angeles and Boston. Mission’s uncommon breadth of AWS technical and strategic proficiencies includes more than 90 AWS certifications held among the company’s cloud operations professionals and solutions architects. Mission is also an APN Advanced Consulting Partner who has achieved Competency Partner status in DevOps, Healthcare, and Life Sciences. The company has particularly deep domain expertise across the media and entertainment, mobile gaming, digital media, education, consumer goods, marketing, ecommerce, and Software-as-a-Service (SaaS) verticals.

    With the new brand comes an updated and more robust cloud services structure. The core of Mission’s managed services – built to free organizations from the burden of cloud management and optimization so they can focus on building their applications and growing their businesses – includes:

    • Managed Cloud: 24x7x365 support, adherence to current best practices, automated maintenance, advanced monitoring, managed backups, expert consultation.
    • Managed DevOps: IT roadmapping, accelerated deliveries, advanced and rapid support, CI/CD, long-term consulting.
    • Managed Security: real-time data monitoring, compliance enforcement, data archiving, AI/ML protection, attack mitigation.
    • Managed Application Performance: real-time metrics, proactive performance management, alert response.
    • Professional Services: AWS Well-Architected Reviews, migrations, configuration management, architecture, best practices implementation, cloud transformations, strategic consulting.
    • Cloud Optimization: detailed spend attribution, best practices benchmarking, cost optimization, simplified invoicing.

    “We have a vision to guide and support organizations worldwide to confidently embrace and leverage the transformative power of cloud computing, and to do good for themselves, their teams, their customers, and their stakeholders,” said Simon Anderson, CEO, Mission. “The next twenty years of global development will require rapid innovation, deep insights, and flexible, cost-effective cloud platforms that deliver rapid, tangible value to all. Mission will play a leading role in partnering with your company to design your future value, and to achieve your goals.”

    Customers can connect with Mission and explore its offerings – including free on-demand consultations with AWS-certified solutions architects – at missioncloud.com

    About Mission

    Mission is a trusted managed services provider and consulting partner for public cloud platforms including Amazon Web Services (AWS) and Microsoft Azure. Through its dedicated team of expert cloud operations professionals and solutions architects, Mission delivers a unique breadth and depth of AWS- and Azure-recognized technical and strategic proficiencies. Mission combines this know-how with an anything-is-possible belief in the power of cloud transformation, and a dedication to understanding and solving customers’ individual goals and challenges – enabling their development of new and powerful applications running on the cloud.

  • Perforce Acquires Perfecto Mobile to Drive DevOps Consolidation

    Perforce Acquires Perfecto Mobile to Drive DevOps Consolidation

    Perforce this week announced it plans to acquire Perfecto Mobile, a provider of automated application development tools, in a move that signals a potential wave of consolidation across the DevOps sector. Perfecto Mobile is the fifth acquisition Perforce has made in the last two years, and company CEO Mark Ties said there will be more to come.

    Schedule to close later this year, the acquisition is estimated to be about $200 million.

    The primary driver of this wave of consolidation is access to inexpensive capital coupled with mainstream adoption of DevOps processes that is requiring many startup companies to scale beyond their means, Ties said.

    As a provider of a cloud-based set of tools for automating the testing of web and mobile applications using a variety of open source frameworks, Perfecto Mobile will complement a portfolio of application testing tools based mainly on the technologies Perforce gained when it acquired PRKA earlier this year. Perfecto Mobile currently has more than 3,000 customers.

    Application testing, along with application development and deployment, increasingly is shifting to the left as developers assume more responsibility for the overall application environment. Instead of relying mainly on a dedicated team to test applications after they have been developed, companies now are continually testing modules as they are developed. Sometimes that’s done by the developers themselves, while other organizations prefer to maintain testing teams made up of individuals who did not write the code being tested. Proponents of the latter approach contend that approach leads to higher-quality code because the individuals testing the code are not as invested in how the code was written. Of course, in an ideal world, an organization would be able to embrace both approaches.

    Regardless of the approach taken, the one thing that is clear is that the rate of at which applications are being developed requires more reliance on automated testing than ever. Not only are there more applications being developed, but increasingly each one is made up of microservices. There often are multiple versions of those microservices that are subject to frequent change. To make matters even more challenging, the number of dependencies between microservices that make up an application are increasing exponentially. That means the days when organizations could rely mainly on manual testing are coming to an end.

    There may come a day when machine learning algorithms are able to play a bigger role in automating application testing and DevOps. But for now, that day is still far off. In the meantime, most organizations are still incorporating multiple approaches to automated testing into their application development processes. The issue is no longer so much about whether to automate testing as much as it is to what degree.

    In the meantime, the more acquisitions that occur across the DevOps landscape, the greater the validation of DevOps becomes as vendors scramble to extend portfolios that, in many cases, are still optimized for legacy approaches to building and deploying applications that increasingly are falling by the wayside.

    — Mike Vizard

  • Electric Cloud Named a Finalist in Leading DevOps Vendor Category for the 2018 DevOps Industry Awards

    Finalists announced as the DevOps Industry awards celebrate companies and individuals who have accomplished significant achievements when incorporating and adopting DevOps practices

    SAN JOSE, Calif., October 9, 2018 — Electric Cloud (http://electric-cloud.com/), the leader in Adaptive Release Orchestration and Continuous Delivery, today announced it was named a ‘Leading DevOps Vendor’ finalist in the 2018 DevOps Industry Awards (http://devopsindustryawards.com/finalists/). This award, hosted by 31 Media, recognizes vendor organizations who received top marks for their product suite and overall customer service. Electric Cloud’s ElectricFlow Application Release Orchestration platform is recognized as the de facto standard for helping companies release software on business demand with centralized control over DevOps environments, processes and tooling.

    Discover how ElectricFlow can help increase IT efficiency, uncover detailed insights on releases and safely adapt more quickly to business changes – at scale: (https://electric-cloud.com/products/electricflow/).

    The DevOps Industry Awards recognize the tremendous efforts of individuals and teams when undergoing digital transformation projects – whether they are small and bespoke, or large complex initiatives. As part of this program, ‘Leading DevOps Vendors’ show:

    • Evidence of a commitment to high quality and standards to customers
    • Commitment to customer satisfaction
    • Evidence of value for money
    • Demonstration of DevOps thought leadership and contributing to the wider IT community

    “It’s becoming obvious to organizations of all types that the pace of software innovation equates to market success these days. Therefore, releasing high quality software, securely and efficiently, is a critical need for everyone across any geography or industry,” said Carmine (CJ) Napolitano, CEO at Electric Cloud. “Electric Cloud ElectricFlow is designed to meet organizations where they are – from Waterfall to Agile, from On-Premises to the Cloud, and more – to simplify and accelerate their DevOps transformation and transform their software release from a chore, to a competitive advantage.”

    Industry-leading organizations like TIAA, Intel, Lockheed Martin, Phillip Morris, Terradyne, Cisco, GM, and E*Trade choose ElectricFlow because it uniquely provides:

    • A way to implement and share secure, repeatable and adaptable pipelines that deliver mainframe, monolithic and microservices applications
    • Unprecedented, actionable insight into the health and status of enterprise releases, without requiring manual data collection and analysis
    • A solution that will reliably scale as they roll out DevOps processes across their entire organization

    Share This: Electric Cloud named a finalist for the @DevopsOnline 2018 #DevOps Industry Awards https://electric-cloud.com/blog/2018/10/electric-cloud-named-a-leading-devops-vendor-for-the-2018-devops-industry-awards #ContinuousDelivery #DevOpsIndustryAwards

     About Electric Cloud, Inc.
    Electric Cloud’s Adaptive Release Orchestration platform helps organizations like E*TRADE, HPE, Intel and Lockheed Martin confidently release new applications and adapt to change at any speed demanded by the business, with the analytics and insight to measure, track, and improve their results.

  • Software AG Acquires Built.io to Advance Integration Strategy

    Software AG Acquires Built.io to Advance Integration Strategy

    Software AG has acquired Built.io as part of an effort to provide a multitier approach to application integration designed for different classes of developers.

    Subhash Ramachadran, senior vice president for product management at Software AG, said Built.io adds a low-code approach to integration in the form of a platform-as-a-service (iPaaS) environment developed using Node.js to a portfolio of technologies that include the webMethods platform.

    Ramachadran said the low-code approach will appeal more to so-called citizen integrators who are trying to integrate business processes with minimal intervention on the part of an IT team. Many of those capabilities are now expected to be delivered in a software-as-a-service (SaaS) model that citizen developers can invoke on demand. Built.io, for example, already provides built-in support for more than 300 applications and services. Those tools, however, don’t replace the need for a set of integration frameworks aimed at more complex tasks that require professional developers, Ramachadran said.

    Increasingly, there are large numbers of use cases for integration that simply don’t require a professional developer to accomplish, he noted. In fact, the number of use cases that can be addressed by tools such as Built.io might be substantially larger than the use cases requiring a platform the size and scale of webMethods.

    Software AG’s goal is to create a single platform to provide organizations with multiple classes of integration frameworks that can be applied to different personas within an organization, Ramachadran said. A common platform eventually would make it possible for integrations of varying skill levels to collaborate more easily.

    Those frameworks could then be plugged into any continuous integration/continuous development (CI/CD) platform to enable various Software AG integration platforms to be natural extensions of a DevOps environment, he added. The webMethods integration platform already supports Kubernetes clusters and Docker containers as a runtime environment.

    As DevOps processes continue to evolve, Ramachadran said Software AG is betting that organizations will want to make it easier for different classes of developers working with multiple types of tools to collaborate.

    To facilitate that transition, Software AG now enables everything from sharing code via GitHub to deploying micro gateways for managing application programming interfaces (APIs) within the context of a set of microservices, he noted, adding those capabilities will only become more important as organizations begin to build highly distributed internet of things (IoT) applications running on a wide variety of platforms.

    Microservices, however, create something of a paradox when it comes to integration. On the one hand, frameworks such as Built.io will make it simpler for more organizations to integrate multiple microservices and legacy monolithic applications. On the other hand, microservices are making integration more challenging for many professional developers as they continue to expand across the enterprise.

    The challenge facing most organizations will be striking the right balance between microservices and existing monolithic applications, many of which don’t naturally lend themselves to being re-engineered into a series of microservices. In fact, in many cases it may be difficult to distinguish from an integration standpoint what constitutes a microservice versus a monolithic application, so long as both can be invoked using a simple API.

    — Mike Vizard

  • DevOps Dozen 2018: Nominations Deadline Approaching

    DevOps Dozen 2018: Nominations Deadline Approaching

    The last day to submit your nominations for the DevOps Dozen 2018 awards is Oct 10. Click here to vote.

    This year’s awards will include 12 categories, with a winner chosen from each. The top four to six nominees in each category will become finalists, who will be selected based upon the number of nominations they received. You can nominate up to two entrants in each category; however, you can make only one nomination per person. In addition, everyone nominating will be required to provide their name and email address; while that won’t thwart any ballot-stuffing, we hope people will be trustworthy during the nomination process. The winners will be selected by our panel of judges.

    Who are the judges? This was tough. We couldn’t have anyone who might be eligible for an award. That disqualifies vendors, practitioners and many others. However, I think we have four great judges:

    1. Alan Shimel, founder and editor in chief, devopsy.kinsta.cloud
    2. George Hulme, longtime tech journalist and editor at devopsy.kinsta.cloud and Security Boulevard
    3. Jayne Groll, CEO and co-founder of the DevOps Institute
    4. Helen Beal, DevOpsologist at Ranger4.

    So what are the dozen categories for the DevOps Dozen this year? That you can get on the site itself, but here they are as well:

    [su_custom_gallery source=”media: 125437,125438,125439,125440,125441,125442,125443,125444,125445,125446,125447,125448,” link=”custom” target=”blank” width=”400″ height=”200″]

    Thank you again for your enthusiastic response to last year’s awards. The full list of 2017 finalists and winners are available to view here.

    There are so many great companies and people involved in DevOps that it’s always difficult to pick the winners. We know some worthy choices will not be voted tops in their category; however, acknowledging them in our awards process helps show how important they are in the DevOps space.

    As stated earlier, the top four to six nominees in each category will be designated as finalists, who then can submit a presentation on why they deserve the award to judges@devops.com. Finalists will be announced the second week of November and the winners, who will be chosen by our panel of judges, will be announced in December.

    If you have questions, send them to DD@devops.com. Voting for finalist nominees is open for three weeks, so don’t waste any time—nominate your favorites today. Good luck to everyone vying to be one of the DevOps Dozen 2018!

    — Alan Shimel

  • Splunk Aims to Trigger DevOps Processes

    Splunk Aims to Trigger DevOps Processes

    Splunk this week at its .conf18 conference continued a campaign to extend the reach of its operational analytics platform into the realm of DevOps through a partnership with Puppet.

    Spunk also announced the 4.0 release of Splunk IT Service Intelligence (ITSI), which extends a platform for managing IT using machine learning algorithms by integrating it with incident management software Splunk gained via its acquisition of VictorOps. Other new capabilities include support for a set of key performance indicators (KPIs) for tracking metrics such as application workloads and the ability to do root cause analysis on any event the machine learning algorithms predict.

    Andi Mann, chief technology advocate for Splunk, said the alliance with Puppet furthers Splunk’s ambitions to be a primary source of data used to inform automation frameworks that are at the heart of any set of DevOps processes. Over time, Splunk will continue to expand its DevOps partnerships with an eye toward being the analytics platform used to trigger automated processes using frameworks developed by Puppet and others, he said.

    At the same time, Splunk continues to develop orchestration capabilities of its own based on technologies it gained via its acquisition of Phantom. While that orchestration software primarily is used today in a security management application, Mann said Splunk is now looking at applying that software more broadly, as it encouraged developers to build applications using a Splunk Developer Cloud now in beta.

    Mann said that when it comes to machine learning in IT operations, otherwise known as AIOps, the most challenging task ahead is establishing trust. IT professionals are not going to sanction a “black box” approach that doesn’t enable them to see how a machine learning framework is determining what to automate. Because of that issue, Mann said, providing a root cause analysis capability in ITSI is critical.

    The next big issue facing organizations, he noted, is improving the quality of the data being used to inform a machine learning framework. One of the benefits of the DevOps movement is that, as developers take responsibility for both building and running applications, more of them are paying attention to how log data is being created. Mann said the notes developers leave within an application on how to resolve issues are becoming more detailed, a process that Splunk refers to as “semantic logging.”

    Mann noted the goal is to create a closed-loop system where every IT issue eventually creates a ticket in a DevOps system for developers to address. The bridge between those processes will be the chat capabilities provided by the VictorOps incident management platform. In fact, Mann said Splunk is moving from being a provider of log analytics software to being a provider of a continuous monitoring solution that analyzes data both stored in logs and in near real-time using a Splunk Data Stream Processor, which is currently in beta.

    It may take a while for that loop to be completely closed. But it’s clear that many of the tools that IT operations teams rely on today are becoming increasingly DevOps-friendly.

    — Mike Vizard

  • SAP Extends Effort to Modernize App Development

    SAP Extends Effort to Modernize App Development

    SAP this week expanded the scope of the SAP Cloud Platform to include support for the ABAP programming language and made available a beta version of a Kubernetes-as-a-service offering, in effort to update its app development portfolio.

    Announced at the SAP TechEd 2018 conference, these two offerings serve as bookends for an evolving SAP strategy that seeks to include organizations that have heavily invested in ABAP over the last 20 years as well as organizations that are shifting toward employing containers to build applications based on a microservices architecture.

    Dan Lahl, vice president of product marketing for SAP, said ABAP has been widely employed by more than thousands of SAP customers to build applications using the same language that SAP employed to build its on-premises IT environment. Those applications now can be built or enhanced using an SAP Cloud platform based on a distribution of the open source Cloud Foundry platform-as-as-service (PaaS) environment.

    At the same time, Lahl said SAP is working toward hosting its distribution of Cloud Foundry on Kubernetes in addition to making available a Kubernetes-based platform alongside Cloud Foundry. SAP is also leveraging container-based technologies such as Knative and Kubeless to provide access to a serverless computing framework based on Kubernetes. That capability is also in beta.

    The SAP Cloud Platform Backend Service for generating application programming interfaces (APIs) is now available in beta, while the SAP Cloud Platform Enterprise Messaging Service—based on technology developed by Solace—is now generally available.

    Finally, SAP is making available Cloud Application Programming Model for SAP Cloud Platform, a set of framework, tools, languages and libraries based on best practices defined by SAP. Lahl noted that many of those best practices are based on DevOps methodologies that SAP is helping customers embrace as part of an effort to accelerate application development projects.

    Lahl said SAP is, for the moment, focused on modernizing the application development processes of its core developer community. ABAP support, for example, makes it possible to use a venerable programming language that most SAP customers know on a managed instance of the Cloud Foundry PaaS. But the goal is to make SAP Cloud a platform that organizations will use to build applications using multiple programming languages regardless of how many SAP applications they might have running. According to SAP, today there are more than 10,000 customers using SAP Cloud Platform.

    It’s not clear to what degree Kubernetes might supplant Cloud Foundry as a major platform for building applications in the enterprise. Lahl contended that by putting Cloud Foundry on top of Kubernetes, SAP now provides one of the richest application development tools on a platform that is rapidly becoming a de facto standard for orchestrating containers.

    It may take a while before SAP becomes a dominant provider of a platform for building custom applications. But the one thing that is clear is that SAP these days is focused on a lot more than delivering a set of packaged applications that eliminate the need to build a custom application in the first place.

    — Mike Vizard

  • Pivotal Software Extends Development Platform Reach

    Pivotal Software Extends Development Platform Reach

    Pivotal Software announced an expansion of its implementation of the Cloud Foundry platform-as-a-service (PaaS) environment in addition to extending its support for Kubernetes to the Amazon Web Services (AWS) public cloud.

    At its SpringOne Platform 2018 conference, Pivotal revealed that Pivotal Cloud Foundry (PCF) can now extend a single instance of its distribution of the open source PaaS across multiple data centers. In addition, Pivotal is making it possible to automatically update the operating systems on which its PaaS is hosted, and added a more extensible user interface to its PCF Healthwatch monitoring tool.

    What’s more, Pivotal announced that Pivotal Container Service (PKS), its implementation of Kubernetes, now can be deployed on EC2 instances of the Amazon Web Services (AWS) public cloud. PKS is currently based on version 1.11 of Kubernetes that has been packaged with a software-defined runtime for spinning up clusters known as Kubo, developed under the auspices of the Cloud Computing Foundation (CFF), which also oversees Cloud Foundry. PKS was developed in collaboration with VMware, which is a sister company of Pivotal operating under the same Dell Technologies umbrella, and the latest version adds the ability to configure a namespace or cluster to emit logs to a specific destination, such as VMware vRealize Log Insight, without operator intervention.

    Richard Seroter, senior director of product for Pivotal, said Pivotal and VMware are collaborating to make Kubernetes clusters more accessible to enterprise IT organizations that typically don’t have engineers available to manage IT operations. By combining automation frameworks from VMware and Pivotal, the expectation is that PKS will gain more traction as IT organizations evaluate which flavor of Kubernetes to deploy in a production environment, he added. A recent research report published by the Cloud Native Computing Foundation (CNCF) would suggest that strategy is starting to gain traction.

    Pivotal apparently is pursuing a dual application development strategy. The first is based on a PCF framework that is highly prescriptive in terms of how applications should be built and deployed. The second is a more flexible container-as-a-service (CaaS) platform based on Kubernetes.

    In general, organizations that have invested in Cloud Foundry to deploy a PaaS are not likely abandon it in favor of a container platform overnight. But Pivotal and the CFF are under some pressure to be more aggressive in unifying Cloud Foundry and Kubernetes: There already are several instances of Cloud Foundry that run on top of Kubernetes, and Pivotal Software revealed earlier this month that it missed Wall Street’s expectations for billing revenue in its most recent quarter by 25 percent.

    It may take a while for the relationship between Cloud Foundry and Kubernetes to become more firmly established in the minds of IT professionals. But there are certainly no shortage of options when it comes to developing modern applications—there will be more than a few organizations employing multiple frameworks for building these applications for many years to come. The real issue may lie in deriving value from those investments.

    Survey findings published this week by Pivotal revealed that only 39 percent of global organizations are deploying code on a continuous, hourly or daily basis and only 40 percent deploy code on a monthly, quarterly or annual basis. The survey also found that only 35 percent of developers’ time is spent writing code for new products or features to deliver value, as opposed to maintenance or fixing old code. Also, one-third of U.S. respondents (33 percent) reported delaying application releases more than 11 times due to security concerns, compared to 21 percent globally. Clearly, there is much more DevOps work to be done.

    — Mike Vizard

  • GitLab Joins Unicorn Club With $100m Raise

    GitLab Joins Unicorn Club With $100m Raise

    GitLabGitLab has become the latest member of the Unicorn club after announcing a $100m round of funding led by ICONIQ Capital.  This latest round, a series D brings the total capital raise for GitLab to $145m over 3 years. According to the company it also raised their market valuation to over the magical $1B mark.

    Some of GitLab’s success in raising this latest round of capital can be attributed  to a raising tide lifting all boats. Microsoft’s acquisition of GitHub for $7.5B continues to make ripples in the software developer tools space. But while they share Git in their name, GitLab is not just another Git or GitHub imitator. No, GitLab has a far more ambitious mission. They actually want to be a one stop shop for a complete end to end DevOps solution. Using GitLab you can replace 6 to 9 different DevOps related tools. Or at least that is the vision.

    I have always thought this was a tall order that would require a different way of building software to succeed. GitLab’s CEO Sid Sijbrandij thinks he has found this new method. Using open source, GitLab has an army of software contributors that donate their software to GitLab everyday. With monthly releases you can see the results of this philosophy with constant progress on all fronts at once.

    While Sid realizes that every component or area of GitLab may not be best of breed today, it is his vision that it will be. So what does $100m buy you today to recognize this vision? Well you can hear it right from the horse’s unicorn’s mouth. I sat down with Sid to discuss the raise, the future of GitLab and the market in general.

    I have had the pleasure of interviewing Sid before. He has some very good ideas on where the market is and where it is heading. Below is our conversation, enjoy!

    [wpvideo lvF0Ey0B]

    — Alan Shimel

  • CloudBees Extends CI/CD Scope, Reach

    CloudBees Extends CI/CD Scope, Reach

    CloudBees, at its DevOps World | Jenkins World 2018 conference this week, unveiled a broad strategy to extend the reach and scope of continuous integration/continuous deployment (CI/CD) platforms based on the open source Jenkins software.

    Company CEO Sascha Labourey said CloudBees Suite will provide the equivalent of a customer relationship management (CRM) application for software delivery. That approach will not only accelerate application development processes, but also provide application stakeholders across the enterprise with more visibility into DevOps processes. For example, business executives are demanding more visibility into DevOps processes as the organization begins to appreciate how dependent it is on the timely delivery of software, Labourey said.

    Rather than buying isolated components of a CI/CD platform, the CloudBees suite provides a single pane of glass through which all the elements of the platform can be managed. That capability is critical because it enables an organization to start with one element of a CI/CD platform that, over time, can be expanded frictionlessly as the organization becomes more comfortable with DevOps processes.

    Labourey said it’s clear the CI/CD platform is the hub around which those DevOps process revolve. The CloudBees Suite includes CloudBees Core to unify the management and governance of pipelines, which includes limited availability of the Kube CD for extending the CloudBees platform to Kubernetes clusters. In fact, Labourey noted that Kubernetes is rapidly emerging as the foundational element of a federated approach to CI/CD in the age of microservices.

    CloudBees also announced an alliance through which Lenovo will provide IT organizations a turnkey set of servers running instances of CloudBees Core on the Red Hat OpenShift application development platform. As DevOps continues to evolve, Labourey said, organizations want to reduce the amount of time it takes their IT teams to deploy the infrastructure required for a modern application development platform.

    Another core element of CloudBees Suite is CloudBees DevOptics, a software-as-a-service (SaaS) application that provides visibility and insights into value streams and operations as well as continuous reports on the four key DevOps metrics. CloudBees DevOptics will provide the raw data the company will rely on to apply artificial intelligence (AI) in the form of machine and deep learning algorithms to the CloudBees CI/CD platform, Labourey said.

    The two remaining core modules of CloudBees Suite are CloudBees CodeShip, which enables organizations to jump start projects using a CI/CD as a Service offering, and CloudBees Jenkins Support, which provides users of the open source Jenkins platform full support. CloudBees is also making support for instances of Jenkins available as a standalone subscription service.

    It’s clear that CloudBees is trying to extend the reach of its widely employed CI/CD environment not only to new platforms, but also to new users. As digital business processes continue to proliferate across the enterprise, there is now a lot more at stake whenever an application development project is delayed. While such delays may be inevitable, the degree to which organizations might be surprised by those delays can be reduced sharply when everyone in the organization is operating on the same DevOps page.

    — Mike Vizard