HN user

keithpitt

161 karma

Buildkite CEO

[ my public key: https://keybase.io/keithpitt; my proof: https://keybase.io/keithpitt/sigs/HXdEBbaUkxhCrnLPmvRUNT_WIUoGO4iGG-7Ee-U5cRk ]

Posts37
Comments26
View on HN
buildkite.com 4y ago

Show HN: Buildkite Test Analytics: observability for your test suite

keithpitt
4pts0
buildkite.com 4y ago

Speed up your builds with Buildkite’s new free plan

keithpitt
1pts0
buildkite.com 4y ago

Buildkite Test Analytics, a new way to identify, track and fix problematic tests

keithpitt
10pts4
buildkite.com 5y ago

Buildkite’s Managed macOS CI

keithpitt
2pts0
building.buildkite.com 8y ago

5 ways we’ve improved flakey test debugging

keithpitt
1pts0
building.buildkite.com 8y ago

The rocky road to Emoji 4.0 support

keithpitt
1pts0
building.buildkite.com 9y ago

New in Buildkite: My Builds

keithpitt
1pts0
building.buildkite.com 10y ago

Introducing a new continuous integration stack for AWS: the Elastic CI Stack

keithpitt
12pts0
silarsis.blogspot.com 10y ago

Hubot and Slack and AWS and Buildkite = Social Ops

keithpitt
1pts0
buildkite.com 10y ago

Announcing Buildkite Agent 2.0

keithpitt
1pts0
stackshare.io 11y ago

How the World's Largest Design Marketplace Builds and Ships Code – StackShare

keithpitt
3pts0
buildbox.io 11y ago

CI and build automation for GitLab

keithpitt
2pts0
buildbox.io 11y ago

Buildbox: Bash vulnerability CVE-2014-6271

keithpitt
4pts0
buildbox.io 12y ago

Buildbox Agent 0.2 Release: Now with Artifact Downloading and Build Metadata

keithpitt
1pts0
buildbox.io 12y ago

Show HN: Buildbox Continuous Delivery Pipelines

keithpitt
1pts0
buildbox.io 12y ago

Rewriting the Buildbox Agent in Go

keithpitt
43pts6
speakerdeck.com 12y ago

Keith and Mario's Guide to Continuous Deployment

keithpitt
9pts3
buildbox.io 12y ago

Buildbox: Multiple Project Summary Reporting Standard (cc.xml)

keithpitt
1pts0
buildbox.io 12y ago

Buildbox now supports build artifacts

keithpitt
1pts0
buildbox.io 12y ago

Buildbox comes out of Beta

keithpitt
2pts0
buildbox.io 12y ago

Buildbox: A Hosted CI service that uses your own infrastructure to run builds

keithpitt
41pts30
speakerdeck.com 13y ago

Keith and Mario's Guide to Fast Websites

keithpitt
4pts0
foodti.me 13y ago

Foodtime - A food discovery service built in 48 hours for Rails Rumble

keithpitt
1pts0
www.greenlemon.com.au 14y ago

The story of trainerlisting.com.au

keithpitt
1pts0
lifehacker.com 14y ago

Desktoppr Is an Awesome Wallpaper Search Engine

keithpitt
1pts0
www.desktoppr.co 14y ago

Show HN: Desktoppr - Dropbox Wallpaper Syncing

keithpitt
20pts11
desktoppr.co 14y ago

Show HN: Desktoppr.co - Wallpaper sharing and syncing.

keithpitt
3pts0
github.com 14y ago

Ember-rails

keithpitt
2pts0
vendorkit.com 14y ago

VendorKit – an iOS library management system

keithpitt
47pts8
vendorforge.org 14y ago

Vendorforge

keithpitt
4pts0

Hi I’m Keith, Buildkite CEO.

You caught us! Well spotted.

We had such little success with the $9 plan. When people upgraded, they generally chose the more expensive option. Knowing this, we removed it to see what happens to upgrade rates. We might even increase the free offering to balance it out, not sure yet.

Pricing is dark art of science, economics, research and “making shit up”. I dunno if this iteration is any better, but we’ll see!

As someone who has either written, or reviewed every single line of code in Buildkite, I can tell you that there is no backdoor. If anything, we are constantly asking ourselves “how can we protect the customer from us in the unlikely event we were compromised”. Also, with how modern software delivery works, it’s impossible for an employee to make a change without someone noticing.

GitLab 7.8 release 11 years ago

Hey! buildkite.com have supported GitLab CI for a while, and you bring your own build agents, so you can keep your source code safe :)

Hi peter,

Thanks for taking the time to give us some feedback!

Jenknis has been around forever, and probably will be. It's one of those pieces of software that just keeps on going. Like the movie Grease - sure it's rough around the edges, but it's still pretty damn good - and future generations will still watch it.

People will still write these tools in a weekend - and that's totally cool! They don't have to use Buildbox if they don't want to.

There are varying skill levels out there. Some devs are really happy to install Ruby on Ubuntu, but often have gripes installing Jenkins, managing permissions, etc. And for those "young coders" - Jenkins looks very dated. It's very difficult to navigate, and managing plugins is usually a pain.

Buildbox is a middle-ground between managing Jenkins, and having your CI run entirely for you in the cloud by other services.

Cheers,

Keith from Buildbox

Hi krohling,

Yup, you're right! Your tests run on your own infrastructure, in your own office, under your desk, in your data centre, where ever it may be.

When doing risk assessment on secure systems (think banking, billing, etc), some people will see uploading source code to services like Circle as a security risk.

Have you ever committed a password accidentally to a repo? I think everyone has at some point. If your code runs on any server thats out of your control, you're now at risk. Because your password is now on some random machine in the cloud. Sure - probably a low risk of actually being compromised - but for some companies - this is very important.

Cheers,

Keith from Buildbox

Hi ssw1n!

Travis has chosen a very tight integration with GitHub and you run builds on their servers.

Jenkins is usually a hard thing for most people to setup. It's very old software and the UI hasn't changed in years.

I'm trying to find a middle ground between the two services. I can easily install ruby on a build slave, but trying to manage the build master is always a pain.

Yeah, I think we need to think about that some more. The duplicate wallpapers are a bug that we don't know how to fix. They have different dimensions, so its hard for us to figure out if its already in our database.

I see what you guys mean. Hopefully when we can add features agin we'll able to implement these things. We had FB connect, but took it out because we didnt have time to test it enough. We also took out username/password auth because we felt it would complicate things - perhaps not?