What’s the point: CNCF signs off on 2019, CircleCI rolls out Orbs, Travis maintenance, Functions 3.0

What's the point

The Cloud Native Computing Foundation has drawn a line under the last year, with the publication of its CNCF Annual Report 2019. The wide ranging roundup declared the organisation “one of the most successful open source foundations ever”, starting 2019 with 345 members, and adding more that 173 over the course of the year. Its end user community grew 89 per cent to 131 companies and startups. On its to do list for 2020 are expanding its Kubernetes Forums and launched Kubernetes Community Days, and create an Automotive user group, alongside its Telco, Research, and Financial Services orgs.

CircleCI floats out deployment Orbs

CircleCI has expanded its constellation of Orbs, its connector format to more easily hook its CI/CD product into other services, to cover a range of deployment options. CircleCI describes Orbs as “shareable packages of configuration elements, including jobs, commands, and executors.” The vendor has split the suite of deployment Orbs into three categories. Under Cloud Services there are Orbs for AWS Code Deploy, AWS SAM Serverless and AWS ECS, and Google Cloud Run, as well as Heroku and Cloud Foundry. Kubernetes cloud deployment lineup gets 12 Orbs in total, with CircleCI’s own Kubernetes  tool set, as well as Google’s Kubernetes Engine, Red Hat OpenShift, Azure Kubernetes Service, and Amazon EKS, amongst others. There are also eight “deployment tools orbs” including a Salesforce SFDX CLI integration, Pulumi, and feature flagging service LaunchDarkly.

Travis warns it will be having a lie-down

Travis has warned users that its public services will be unavailable on Saturday February 1, as travis-ci.com will be down for planned database maintenance. During the two hour down tools, builds triggered via GitHub will be accepted, but any scheduled or running builds will be canceled and “re-enqueued to begin running after the maintenance window has concluded”.

Azure Functions 3.0 now GA

Microsoft has announced that Azure Functions 3.0 is now generally available, meaning functions built on the new runtime can be deployed into production. The latest rev brings support for .NET Core 3.1 and Node 12, but the vendor also said it is “highly backwards compatible, so most existing apps running on older language versions should be able to upgrade to the 3.0 version and run on it without any code changes.” Applications on older versions of the Azure Functions runtime will still be supported, and there are no plans to deprecate 1.0 or 2.0.