Personal blog of Yzmir Ramirez

Buildkite’s founding team — Lachlan Donald, Keith Pitt and Tim Lucas — working remotely

Buildkite, a Melbourne-based company that provides a hybrid continuous integration and continuous delivery (CI/CD) platform for software developers, announced today that it has raised AUD $28 million (about USD $20.2 million) in Series A funding, bringing its valuation to more than AUD $200 million (about USD $145 million).

The funding was led by OpenView, an investment firm that focuses on growth-stage enterprise software companies, with participation from General Catalyst.

This round is the company’s first since Buildkite raised about AUD $200,000 in seed funding when it was founded in 2013.

Co-founder and chief executive officer Lachlan Donald told TechCrunch that Buildkite didn’t seek more funding earlier because it was growing profitably. In fact, the company turned away interested investors “because we wanted to focus on sustainable growth and maintain control of our destiny.”

But Donald said they were open to investment from OpenView and General Catalyst because they see the two investors as “true partners as we enter and define this next generation of CI/CD.”

Buildkite’s team is small, with just 26 employees. “We’re a lean, focused team, so their expert advice and guidance will help more software teams around the world discover Buildkite,” Donald said. He added that part of the funding round will be used to give 42X returns to early investors and shareholders, and the rest will be used on product development.

In a statement about the funding, OpenView partner Mackey Craven said, “The global pandemic and the resulting economic uncertainty underlines the importance for companies to maximize efficiencies and build for growth. As the world continues to build digital-first applications, we believe Buildkite’s unique approach will be the new enterprise standard of CI/CD and we’re excited to be supporting them in realizing this ambition.”

Continuous integration gives software teams an automated way to develop and test applications, making collaboration more efficient, while continuous delivery refers to the process of pushing code to environments for further testing by other teams, or deploying it to customers. CI/CD platforms make it easier for fast-growing tech companies to test and deliver software. Buildkite says it now has more than 1,000 customers, including Shopify, Pinterest and Wayfair.

As part of the round, Jean-Michel Lemieux, Shopify’s chief technology officer, and Ashley Smith, chief revenue officer at Gatsby and OpenView venture partner, will join Buildkite’s board.

The increased use of online applications caused by the COVID-19 pandemic means there is more demand for CI/CD platform, since engineering teams need to work more quickly.

“A good example is Shopify, one of our longstanding partners. They came to us after they outgrew their previous hosted CI provider,” Donald said. “Their challenge is one we see across all of customers — they needed to reduce build time and scale their team across multiple time zones. Once they wrapped Buildkite into their development flow, they saw a 75% reduction in build wait times. They grew their team by 300% and have still been able to keep build time under 10 minutes.”

Other CI platforms available include Jenkins, CircleCI, Travis, Codeship and GitLab. Co-founder and chief technology officer Keith Pitt said one of the ways that BuildKite differentiates from its rivals is its focus on security, which prompted his interest in building the platform in the first place.

“Back in 2013, my then-employer asked that I stop using a cloud-based CI/CD platform due to security concerns, but I found the self-hosted alternatives to be incredibly outdated,” Pitt said. “I realized a hybrid approach was the solution for testing and deploying software at scale without compromising security or performance, but was surprised to find a hybrid CI/CD tool didn’t exist yet. I decided to create it myself, and Buildkite was born.”

Harness has made a name for itself creating tools like continuous delivery (CD) for software engineers to give them the kind of power that has been traditionally reserved for companies with large engineering teams like Google, Facebook and Netflix. Today, the company announced it has acquired Drone.io, an open-source continuous integration (CI) company, marking the company’s first steps into open source, as well as its first acquisition.

The companies did not share the purchase price.

“Drone is a continuous integration software. It helps developers to continuously build, test and deploy their code. The project was started in 2012, and it was the first cloud-native, container-native continuous integration solution on the market, and we open sourced it,” company co-founder Brad Rydzewski told TechCrunch.

Drone delivers pipeline configuration information as code in a Docker container. Image: Drone.io

While Harness had previously lacked a CI tool to go with its continuous delivery tooling, founder and CEO Jyoti Bansal said this was less about filling in a hole than expanding the current platform.

“I would call it an expansion of our vision and where we were going. As you and I have talked in the past, the mission of Harness is to be a next-generation software delivery platform for everyone,” he said. He added that buying Drone had a lot of upside.”It’s all of those things — the size of the open-source community, the simplicity of the product — and it [made sense], for Harness and Drone to come together and bring this integrated CI/CD to the market.”

While this is Harness’ first foray into open source, Bansal says it’s just the starting point and they want to embrace open source as a company moving forward. “We are committed to getting more and more involved in open source and actually making even more parts of Harness, our original products, open source over time as well,” he said.

For Drone community members who might be concerned about the acquisition, Bansal said he was “100% committed” to continuing to support the open-source Drone product. In fact, Rydzewski said he wanted to team with Harness because he felt he could do so much more with them than he could have done continuing as a standalone company.

“Drone was a growing community, a growing project and a growing business. It really came down to I think the timing being right and wanting to partner with a company like Harness to build the future. Drone laid a lot of the groundwork, but it’s a matter of taking it to the next level,” he said.

Bansal says that Harness intends to also offer on the Harness platform a commercial version of Drone with some enterprise features, even while continuing to support the open source side of it.

Drone was founded in 2012. The only money it raised was $28,000 when it participated in the Alchemist Accelerator in 2013, according to Crunchbase data. The deal has closed and Rydzewski has joined the Harness team.

CircleCI, an early adherent to the notion of continuous delivery when it launched in 2011, announced a $100 million Series E investment today. It comes on top of a $56 million round last July.

The round was led by IVP and Sapphire Ventures . Under the terms of the deal, Cack Wilhelm will be joining the CircleCI board. Jai Das from Sapphire will also be joining the board as an observer.

Today’s investment brings the total raised to $215 million, according to the company, with $156 million coming over the last 8 months. The company did not want to discuss its current valuation.

Circle CI CEO Jim Rose says with so much uncertainty because of COVID-19 he welcomes not only the money, but the quality of the firms and people involved in the investment.

“We’re really excited to get both IVP and Sapphire because they’ve seen all of it all the way through public and beyond. Given all of the nuttiness over the last few months obviously having cash on the balance sheet is extremely helpful, but the other part, too is that this a time when you want to have more brains around the table, not fewer. And so being able to get people to help out and just think about the problems that we’re encountering right now is really helpful,” Rose told TechCrunch .

Rose recognizes the huge challenge everyone is facing, but he sees this switch to remote workforces really driving the need for more automation, something his company is in a position to help DevOps teams with.

“What we’ve seen from a DevOps perspective is that this forced migration to remote-only for so many organizations has really driven the urgency for more automation in the DevOps pipeline,” he said.

He said this has led to a huge surge in usage on the platform in recent weeks, and today’s investment will at least partly go towards making sure there are enough resources in place to keep the platform stable whatever comes.

“When we think about money and we think about where we’re investing in the near term, we’re investing a lot in making sure that the platform is stable and available and supporting all of our customers as they go through this. You know this is a difficult time, a difficult transition and we’re trying to make sure that we’re doing everything we can to support our customers through that process,” Rose said.

Many companies at this stage of startup maturity begin to look ahead to an IPO, but Rose isn’t ready to discuss that, especially in the current economic climate. “We’re going to have to get folks to some kind of liquidity at some point, but I think right now our focus is on really investing in the platform and investing in our customers and then we’ll let the market clear out and figure out what the new normal looks like,” he said.

The company would consider making some acquisitions with its base of capital if the right opportunity came along. “We’re always evaluating and always looking around. One of the interesting things about our space is that it’s flooded with new and innovative approaches to point problems. There are a lot of companies that are interesting, so we’re definitely always looking around,” he said.

CloudBees, the enterprise continuous integration and delivery service (and the biggest contributor to the Jenkins open-source automation server), today announced that it has acquired Electric Cloud, a continuous delivery and automation platform that first launched all the way back in 2002.

The two companies did not disclose the price of the acquisition, but CloudBees has raised a total of $113.2 million while Electric Cloud raised $64.6 million from the likes of Rembrandt Venture Partners, U.S. Venture Partners, RRE Ventures and Next47.

CloudBees plans to integrate Electric Cloud’s application release automation platform into its offerings. Electric Flow’s 110 employees will join CloudBees.

“As of today, we provide customers with best-of-breed CI/CD software from a single vendor, establishing CloudBees as a continuous delivery powerhouse,” said Sacha Labourey, the CEO and co-founder of CloudBees, in today’s announcement. “By combining the strength of CloudBees, Electric Cloud, Jenkins and Jenkins X, CloudBees offers the best CI/CD solution for any application, from classic to Kubernetes, on-premise to cloud, self-managed to self-service.”

Electric Cloud offers its users a number of tools for automating their release pipelines and managing the application life cycle afterward.

“We are looking forward to joining CloudBees and executing on our shared goal of helping customers build software that matters,” said Carmine Napolitano, CEO, Electric Cloud. “The combination of CloudBees’ industry-leading continuous integration and continuous delivery platform, along with Electric Cloud’s industry-leading application release orchestration solution, gives our customers the best foundation for releasing apps at any speed the business demands.”

As CloudBees CPO Christina Noren noted during her keynote at CloudBees’ developer conference today, the company’s customers are getting more sophisticated in their DevOps platforms, but they are starting to run into new problems now that they’ve reached this point.

“What we’re seeing is that these customers have disconnected and fragmented islands of information,” she said. “There’s the view that each development team has […] and there’s not a common language, there’s not a common data model, and there’s not an end-to-end process that unites from left to right, top to bottom.” This kind of integrated system is what CloudBees is building toward (and that competitors like GitLab would argue they already offer). Today’s announcement marks a first step into this direction toward building a full software delivery management platform, though others are likely to follow.

During his company’s developer conference, Labourey also today noted that CloudBees will profit from Electric Cloud’s longstanding expertise in continuous delivery and that the acquisition will turn CloudBees into a “DevOps powerhouse.”

Today’s announcement follows CloudBees’ acquisition of CI/CD tool CodeShip last year. As of now, CodeShip remains a standalone product in the company’s lineup. It’ll be interesting to see how CloudBees will integrate Electric Cloud’s products to build a more integrated system.

For the longest time, GitHub was all about storing source code and sharing it either with the rest of the world or your colleagues. Today, the company, which is in the process of being acquired by Microsoft, is taking a step in a different but related direction by launching GitHub Actions. Actions allow developers to not just host code on the platform but also run it. We’re not talking about a new cloud to rival AWS here, but instead about something more akin to a very flexible IFTTT for developers who want to automate their development workflows, whether that is sending notifications or building a full continuous integration and delivery pipeline.

This is a big deal for GitHub . Indeed, Sam Lambert, GitHub’s head of platform, described it to me as “the biggest shift we’ve had in the history of GitHub.” He likened it to shortcuts in iOS — just more flexible. “Imagine an infinitely more flexible version of shortcut, hosted on GitHub and designed to allow anyone to create an action inside a container to augment and connect their workflow.”

GitHub users can use Actions to build their continuous delivery pipelines, and the company expects that many will do so. And that’s pretty much the first thing most people will think about when they hear about this new project. GitHub’s own description of Actions in today’s announcement makes definitely fits that bill, too. “Easily build, package, release, update, and deploy your project in any language—on GitHub or any external system—without having to run code yourself,” the company writes. But it’s about more than that.

“I see CI/CD as one narrow use case of actions. It’s so, so much more,” Lambert stressed. “And I think it’s going to revolutionize DevOps because people are now going to build best in breed deployment workflows for specific applications and frameworks, and those become the de facto standard shared on GitHub. […] It’s going to do everything we did for open source again for the DevOps space and for all those different parts of that workflow ecosystem.”

That means you can use it to send a text message through Twilio every time someone uses the ‘urgent issue’ tag in your repository, for example. Or you can write a one-line command that searches your repository with a basic grep command. Or really run any other code you want to because all you have to do to turn any code in your repository into an Action is to write a Docker file for it so that GitHub can run it. “As long as there is a Docker file, we can build it, run in and connect it to your workflow,” Lambert explained. If you don’t want to write a Docker file, though, there’s also a visual editor you can use to build your workflow.

As Corey Wilkerson, GitHub’s head of product engineering also noted, many of these Actions already exist in repositories on GitHub today. And there are now over 96 million of those on GitHub, so that makes for a lot of potential actions that will be available from the start.

With Actions, which is now in limited public beta, developers can set up the workflow to build, package, release, update and deploy their code without having to run the code themselves.

Now developers could host those Actions themselves — they are just Docker containers, after all — but GitHub will also host and run the code for them. And that includes developers on the free open source plan.

Over time — and Lambert seemed to be in favor of this — GitHub could also allow developers to sell their workflows and Actions through the GitHub marketplace. For now, that’s not an option, but it it’s definitely that’s something the company has been thinking about. Lambert also noted that this could be a way for open source developers who don’t want to build an enterprise version of their tools (and the sales force that goes with that) to monetize their efforts.

While GitHub will make its own actions available to developers, this is an open platform and others in the GitHub community can contribute their own actions, too.

GitHub will slowly open Actions to developers, starting with daily batches for the time being. You can sign up for access here.

In addition to Actions, GitHub also announced a number of other new features on its platform. As the company stressed during today’s event, it’s mission is to make the life of developers easier — and most of the new features may be small but do indeed make it easier for developers to do their jobs.

So what else is new? GitHub Connect, which connects the silo of GitHub Enterprise with the open source repositories on its public site, is now generally available, for example. GitHub Connect enables new features like unified search, that can search through both the open source code on the site and internal code, as well as a new Unified Business Identity feature that brings together the multiple GitHub Business accounts that many businesses now manage (thanks, shadow IT) under a single umbrella to improve billing, licensing and permissions.

The company also today launched three new courses in its Learning Lab that make it easier for developers to get started with the service, as well as a business version of Learning Lab for larger organizations.

What’s maybe even more interesting for developers whose companies use GitHub Enterprise, though, is that the company will now allow admins to enable a new feature that will display those developers’ work as part of their public profile. Given that GitHub is now the de facto resume for many developers, that’s a big deal. Much of their work, after all, isn’t in open source or in building side projects, but in the day-to-day work at their companies.

The other new features the company announced today are pretty much all about security. The new GitHub Security Advisory API, for example, makes it easier for developers to find threads in their code through automatic vulnerability scans, while the new security vulnerability alerts for Java and .NET projects now extend GitHub’s existing alerts to these two languages. If your developers are prone to putting their security tokens into public code, then you can now rest easier since GitHub will now also start scanning all public repositories for known token formats. If it finds one, it’ll alert you and you can set off to create a new one.

Armory, a startup that has built a CI/CD platform on top the open source Spinnaker project, announced a $10 million Series A today led by Crosslink Capital. Other investors included Bain Capital Ventures, Javelin Venture Partners, Y Combinator and Robin Vasan.

Software development certainly has changed over the last several years, going from long cycles between updates to a continuous delivery model. The concept is actually called CI/CD or continuous integration/continuous delivery. Armory’s product is designed to eliminate some of the complexity associated with deploying this kind of solution.

When they started the company, the founders made a decision to hitch their wagon to Spinnaker, a project that had the backing of industry heavyweights like Google and Netflix. “Spinnaker would become an emerging standard for enabling truly multi-cloud deployments at scale. Instead of re-creating the wheel and building another in-house continuous delivery platform, we made a big bet on having Spinnaker at the core of Armory’s Platform,” company CEO and co-founder Daniel R. Odio wrote in a blog post announcing the funding.

The bet apparently paid off and the company’s version of Spinnaker is widely deployed enterprise solution (at least according to them). The startup’s ultimate goal is to help Fortune 2000 companies deploy software much faster — and accessing and understanding CI/CD is a big part of that.

As every company out there becomes a software company, they find themselves outside their comfort zones. While Google and Netflix and other hyper-scale organizations have learned to deploy software at startling speed using state of the art methodologies, it’s not so easy for most companies with much smaller engineering teams to pull off.

That’s where a company like Armory could come into play. It takes this open source project and it packages it in such a way that it simplifies (to an extent) the complex world that these larger companies operate in on a regular basis, putting Spinnaker and CI/CD concepts in reach of organizations whose core competency might not involve sophisticated software deployment.

All of this relates to multi-cloud and cloud-native approaches to software development, which lets you manage your applications and infrastructure wherever they live across any cloud vendor or even on-prem in consistent way. Being able to manage continuous deployment is part of that.

Armory launched in 2016 and is based in the Bay area. It has raised a total of $14 million with a $4 million seed round coming last year. They were also a member of the Y Combinator Winter 2017 class and count Y Combinator as an investor in this round.

When Microsoft acquired GitHub for $7.5 billion smackeroos in June, it sent some shock waves through the developer community as it is a key code repository. Google certainly took notice, but the two companies continue to work closely together. Today at Google Next, they announced an expansion of their partnership around Google’s new CI/CD tool, Cloud Build, which was unveiled this week at the conference.

Politics aside, the purpose of the integration is to make life easier for developers by reducing the need to switch between tools. If GitHub recognizes a Docker file without a corresponding CI/CD tool, the developer will be prompted to grab one from the GitHub Marketplace with Google Cloud Build offered prominently as one of the suggested tools.

Photo: GitHub

Should the developer choose to install Cloud Build, that’s where the tight integration comes into play. Developers can run Cloud Build against their code directly from GitHub, and the results will appear directly in the GitHub interface. They won’t have to switch applications to make this work together, and that should go a long way toward saving developer time and effort.

Google Cloud Build. Photo: Google

This is part of GitHub’s new “Smart Recommendations,” which will be rolling out to users in the coming months.

Melody Meckfessel, VP of Engineering for Google Cloud says that the two companies have a history and a context and they have always worked extremely well together on an engineer-to-engineer level. “We have been working together from an engineering standpoint for so many years. We both believe in doing the right thing for developers. We believe that success as it relates to cloud adoption comes from collaborating in the ecosystem,” she said.

Given that close relationship, it had to be disappointing on some level when Microsoft acquired GitHub. In fact, Google Cloud head, Diane Greene expressed sadness about the deal in an interview with CNBC earlier this week, but GitHub’s SVP of Technology Jason Warner believes that Microsoft will be a good steward and that the relationship with Google will remain strong.

Warner says the company’s founding principles were about not getting locked in to any particularly platform and he doesn’t see that changing after the acquisition is finalized. “One of the things that was critical in any discussion about an acquisition was that GitHub shall remain an open platform,” Warner explained.

He indicated that today’s announcement is just a starting point, and the two companies intend to build on this integration moving forward. “We worked pretty closely on this together. This announcement is a nod to some of the future oriented partnerships that we will be announcing later in the year,” he said. And that partnership should continue unabated, even after the Microsoft acquisition is finalized later this year.

There are few open-source projects as complex as OpenStack, which essentially provides large companies with all the tools to run the equivalent of the core AWS services in their own data centers. To build OpenStack’s various systems the team also had to develop some of its own DevOps tools, and, in 2012, that meant developing Zuul, an open-source continuous integration and delivery (CI/CD) platform. Now, with the release of Zuul v3, the team decided to decouple Zuul from OpenStack and run it as an independent project. It’s not quite leaving the OpenStack ecosystem, though, as it will still be hosted by the OpenStack Foundation.

Now all of that may seem a bit complicated, but at this point, the OpenStack Foundation is simply the home of OpenStack and other related infrastructure projects. The first one of those was obviously OpenStack itself, followed by the Kata Containers project late last year. Zuul is simply the third of these projects.

The general concept behind Zuul is to provide developers with a system for automatically merging, building and testing new changes to a project. It’s extensible and supports a number of different development platforms, including GitHub and the Gerrit code review and project management tool.

Current contributors include BMW, GitHub, GoDaddy, Huawei, Red Hat and SUSE. “The wide adoption of CI/CD in our software projects is the foundation to deliver high-quality software in time by automating every integral part of the development cycle from simple commit checks to full release processes,” said BMW software engineer Tobias Henkel. “Our CI/CD development team at BMW is proud to be part of the Zuul community and will continue to be active contributors of the Zuul OSS project.”

The spin-off of Zuul comes at an interesting time in the CI/CD community, which is currently spoiled for choice. Spinnaker, Google and Netflix are betting on an open source CD platform that solves some of the same problems as Zuul, for example, while Jenkins and similar projects continue to go strong, too. The Zuul project notes that its focus is more strongly on multi-repo gating, which makes it ideal handling very large and complex projects. A number of representatives of all of these open-source projects are meeting at the OpenDev conference in Vancouver, Canada that’s running in parallel with the semi-annual OpenStack Summit there, and my guess is that we’ll hear quite a bit more about all of these projects in the coming days and weeks.