Google has recently announced that Google Cloud Workflows, the service to orchestrate Google Cloud and HTTP-based API services with serverless workflows, is now generally available. Workflows Connectors are now in public preview.

Google Cloud Workflows requires no infrastructure management and scales on demand, including scaling down to zero if no requests are processed, It can be used to develop complex serverless applications, building on workflows that connect series of serverless tasks together in a predetermined order and work with other managed services like Google Cloud’s APIs, Cloud Functions or Cloud Run.

Among the features of the new service, an error handling with configurable retry policies, a reliable workflow execution targeted to enterprise and line-of-business applications and the ability to pass information between steps using JSON parsing and expression-based variable manipulations. Workflows publishes connectors to make it easier to access other Google Cloud APIs within a workflow.

Among the use cases that can benefit from workflows, inventory management processes, e-commerce transactions and other services that require an orchestration layer. Filip Knapik, product manager at GCP, wrote an article before the GA that covers examples for Workflows such as processing files uploaded to a storage bucket, tagging the files based on the extension. He explains:
GCP is not the only cloud provider offering managed workflows. Microsoft has Azure Logic Apps and Amazon introduced AWS Step Function over four years ago. Tim Bray, formerly VP/distinguished engineer at AWS, wrote a detailed comparison between the AWS and GCP services. But regardless of which features they offer and the maturity of the different services, he concludes that choosing the workflow service is a platform choice:

Google Cloud Workflows has a pay-per-use pricing model based on the number of steps and the number of external HTTP calls, with the first 5000 steps and 2000 HTTP calls free every month.

CloudBees Ships a Stable Jenkins X Distribution for Enterprise Teams

CloudBees announced the general availability of the CloudBees Jenkins X Distribution, a curated, enterprise-focused packaging of the open source Jenkins X CI/CD platform designed to run on Kubernetes. The company committed to releasing updates on a 30-day cadence, prioritizing stability over bleeding-edge feature velocity.

According to Ethan Jones, Director of Product Management at CloudBees, the decision was driven directly by enterprise customer feedback. Large IT organizations reported they could not keep pace with the rapid innovation cycle of the upstream Jenkins X open source project. A curated distribution gives teams a validated, stable baseline without requiring them to track every upstream commit.

What Is Jenkins X?

Jenkins X is an open source CI/CD platform built specifically for cloud-native application development on Kubernetes. It is not simply Jenkins ported to containers — it was designed from scratch to address the operational realities of building and deploying microservices in a Kubernetes environment.

Key differentiators of Jenkins X include:

• Native Tekton pipeline support: Jenkins X can build and manage Tekton pipelines that run directly on Kubernetes, without requiring a separate orchestration layer.
• Advanced deployment patterns: Out-of-the-box support for rolling updates, blue/green deployments, canary releases, and GitOps workflows.
• Immutable image management: Teams can build and deploy immutable container images, reducing configuration drift.
• Infrastructure version control: Infrastructure definitions are versioned alongside application code, enabling reliable rollbacks.
• Automated Kubernetes cluster provisioning: Jenkins X can provision and configure a Kubernetes cluster as part of its own installation process, reducing the operational burden of cluster setup.
• The jx CLI: A command-line tool that allows Jenkins X to be installed into new or existing clusters and simplifies importing existing projects or bootstrapping new applications.

Why a Curated Distribution Matters for Enterprise Adoption

Open source projects like Jenkins X move fast by design. New features, API changes, and integrations land frequently, which is valuable for early adopters and contributors but creates a stability challenge for enterprise teams who need predictable release cycles, thorough testing, and clear upgrade paths.

By curating the distribution, CloudBees takes responsibility for validating which upstream capabilities are mature enough for production enterprise use, then packaging them into a release on a defined 30-day schedule. This mirrors the model used successfully with the original CloudBees CI (formerly CloudBees Jenkins Enterprise) for traditional Jenkins users.

The Continuous Delivery Foundation Context

The announcement came against the backdrop of the newly formed Continuous Delivery Foundation (CDF), a Linux Foundation project dedicated to establishing best practices for building and deploying cloud-native applications. CloudBees contributed both Jenkins and Jenkins X to the CDF at its formation.

Other notable CDF projects at the time of this announcement included Tekton Pipelines and Spinnaker, the open source continuous deployment system originally developed at Netflix. Charter members of the CDF included Google, IBM, Capital One, CircleCI, Huawei, JFrog, and Salesforce, among a total of approximately 26 participating vendor and end-user organizations.

The Kubernetes CI/CD Landscape in 2019

At the time of this announcement, Kubernetes-native CI/CD was still an emerging category. Multiple platforms were competing to define what a modern, cloud-native pipeline should look like. CloudBees held a strong position given its decades of stewardship over the Jenkins ecosystem and its large enterprise install base.

The broader takeaway for DevOps practitioners was already clear: as organizations move workloads to Kubernetes and adopt microservices architectures, CI/CD tooling must evolve in step. Traditional CI/CD systems designed for monolithic applications do not map cleanly to containerized, distributed workloads. Jenkins X — and the curated CloudBees distribution — represented an early attempt to bridge that gap with a commercially supported, enterprise-ready solution.

Summary

• CloudBees released the CloudBees Jenkins X Distribution with a 30-day update cadence targeting enterprise stability.
• Jenkins X is a Kubernetes-native CI/CD platform supporting Tekton pipelines, GitOps, advanced deployment patterns, and automated cluster provisioning.
• The distribution addresses enterprise demand for a validated, stable release track separate from the fast-moving upstream project.
• Both Jenkins and Jenkins X were donated to the Continuous Delivery Foundation (CDF) under the Linux Foundation.
• Kubernetes-native CI/CD was an emerging but critical category for teams building and deploying microservices at scale.

AWS RoboMaker Reaches Seven Global Regions

Amazon Web Services announced that AWS RoboMaker expanded into three additional regions: Frankfurt (EU), Singapore (Asia-Pacific), and Ohio (Eastern US). Combined with existing availability in Ireland, Northern Virginia, Oregon, and Tokyo, the service became accessible across seven AWS regions worldwide.

According to Amazon, the regional expansion was designed to give customers greater flexibility to build highly available robotic applications, run distributed simulations, and manage fleet deployments closer to where their robots operate. AWS RoboMaker had originally launched in November 2018, and pricing for the newly added regions was published alongside this announcement.

What Is AWS RoboMaker?

AWS RoboMaker is a managed cloud service designed to simplify the full lifecycle of intelligent robotics software: development, simulation, and deployment at scale. The service is built on top of the Robot Operating System (ROS), the most widely adopted open-source robotics middleware framework, and extends it with native connectivity to AWS cloud services.

The platform consists of three primary components:

• Development environment: A cloud-based IDE pre-configured with ROS, build tools, and AWS SDK integrations, so teams can write and iterate on robotics application code without managing local toolchains.
• Simulation service: A scalable simulation environment that lets developers run parallel simulation jobs to accelerate testing and validation of robot behaviours before deploying to physical hardware.
• Fleet management: A service for remotely deploying, updating, and managing robotics applications across a fleet of physical devices.

AWS RoboMaker Extends ROS to the Cloud

One of the core value propositions of AWS RoboMaker is bridging ROS-based development with managed AWS cloud services. Robotics applications built on RoboMaker can integrate capabilities such as:

• Machine learning: Integration with AWS ML services enables robots to perform tasks like object recognition and natural language understanding.
• Monitoring and analytics: Robots can stream operational telemetry to AWS for analysis and alerting.
• Navigation and communication: Cloud connectivity supports map storage, path planning data, and inter-device messaging.

Around the time of the regional expansion, Amazon also announced support for ROS Melodic Morenia within RoboMaker, keeping the platform aligned with the latest stable ROS release available at the time.

AWS RoboMaker operates in a competitive landscape that includes robotics development platforms from other vendors. Companies such as Qualcomm offered cloud-connected robotics development platforms, some also built on ROS, while third-party providers like Freedom Robotics announced interoperability with RoboMaker for fleet monitoring use cases.

Community Engagement and Getting Started

Ahead of the Robotics Summit & Expo, Amazon Web Services hosted a free, hands-on workshop as part of an AWS RoboMaker Immersion Day in Boston. The event gave developers practical experience with the platform before the broader industry conference, which was produced by The Robot Report.

At the Robotics Summit & Expo, Roger Barga, then General Manager of AWS Robotics and Autonomous Services, delivered a keynote discussing how ROS combined with cloud infrastructure is enabling a new generation of intelligent, connected robots.

Developers looking to get started with AWS RoboMaker can access documentation, tutorials, and a sample simulation job directly through the AWS RoboMaker product page and the RoboMaker console.

Summary: AWS RoboMaker Region Availability (as of July 2019)

Note: AWS regularly adds new region support. Check the official AWS RoboMaker page for the current list of supported regions.