Food, drink and containers for all!

Our Unofficial DockerCon After Party co-hosted with Iron.io last week was a hit! The sold out event had plenty of drinks, food, t-shirts, and stickers for the many developers, customers and partners who decompressed after two DockerCon-filled days. CEOs Paul Biggar (CircleCI) and Chad Arimura (Iron.io) welcomed guests with refreshingly brief talks and encouraged discussions of Docker containers as “the future“. Special thanks to Heavybit for hosting us in their beautiful SOMA offices, and to Maddie, Sarah, and the rest … Continue reading

Joel Test for Continuous Delivery

There’s a bit of a cottage industry forming around updating the Joel Test or producing more purpose-specific variations of it. If you’re not familiar with the Joel test, it’s Joel Spolsky’s “irresponsibly quick” way of measuring the quality of a development team. I find these fascinating to read, and wanted to contribute one in the latter category— a Joel Test specifically for continuous delivery (the practice of delivering software in short cycles that can be released at any time). I … Continue reading

It really is the future

Last week I wrote It’s the Future, a piece that satirized the container ecosystem, lightly mocking Docker and Google and CoreOS and a bunch of other technologies. Lots of Docker enthusiasts enjoying being the butt of the joke, but it was also much loved and shared by lots of people yelling “I told you this was all bullshit”. It’s very easy to see why people might think the container ecosystem is bullshit, in exactly the way I satirized. After all, … Continue reading

It’s The Future

Hey, my boss said to talk to you – I hear you know a lot about web apps? -Yeah, I’m more of a distributed systems guy now. I’m just back from ContainerCamp and Gluecon and I’m going to Dockercon next week. Really excited about the way the industry is moving – making everything simpler and more reliable. It’s the future! Cool. I’m just building a simple web app at the moment – a normal CRUD app using Rails, going to … Continue reading

Continuous Iteration: The Process and Tools Behind our New Site Design

As we looked forward into our 3rd year as a company, with over 23 million builds to date and more than 25 employees worldwide, we knew it was time to give our brand an updated look and feel. We worked to create a solid design base and cohesive style sheet. Instead of a huge overhaul to our site, we tackled the redesign like we do most things at CircleCI: by making continual, iterative changes as we determined what worked best … Continue reading

Testing 3rd Party APIs and Microservices

There’s a lot of challenges in testing your code against 3rd party APIs, so I’m going to explain some best practices that we’ve come up with or seen customers use over time at CircleCI. [Photo credit to @manp] There are two kinds of 3rd party APIs: ones that you don’t control, and ones that you do control. Service you don’t control include products like Twilio, Mailgun, GitHub, Intercom, or any other product or company that your team relies on in … Continue reading

Container Wars

The container wars have started! Containers have a huge amount of hype and momentum, and there are many spoils for whoever becomes dominant in the container ecosystem. The two major startups innovating in this space–CoreOS and Docker–have waged war on each other as part of gaining that control. The Current Landscape On Monday, CoreOS announced Tectonic. Tectonic is a full solution for running containers, including CoreOS as the host OS, Docker or rkt as the container format, and Kubernetes for … Continue reading

Announcing Automatic Test Balancing

Tl;DR: Instead of naively splitting tests among build containers, CircleCI now divides tests intelligently based on execution time. Status quo on CircleCI For years, CircleCI has enabled fast execution of large test suites by splitting tests evenly across many build containers (LXC containers under the hood–the same kind of lightweight containerization as Docker uses). While we have always provided the option to set up parallel actions by manually specifying what should happen on each container, the simplest way to use … Continue reading

Announcing Detailed Test Failure Reporting

TL;DR: CircleCI now tells you exactly which tests failed in our web UI, email notifications, and chat integrations. CircleCI was founded on the promise of making testing less of a pain for developers, and today we’re announcing a big step forward in delivering on that promise. Most of us are used to learning of a failure on CI being the beginning of a little hunting session. We get an email or a chat message that says a build failed, and … Continue reading

Testing ClojureScript code with clojurescript.test and Karma

At CircleCI, we’ve got a lot of tests. We build a product that’s fundamental to the workflow of developers across the world, so we try hard to validate that what goes into production is well tested. Historically, we’ve tested our frontend entirely through Webdriver tests, but with our transition to using ClojureScript for our UI, we took some time to reevaluate how to best test our new code. As great as Webdriver is when it comes to automating browser interactions, … Continue reading

← Older posts