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.
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.
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.
Thanks for your feedback! We actually had a page that did that, but we decided to take it down - mainly because we want to finish our product fully before starting to compare ourselves to other solutions :)
Yup! We 100% do iOS builds. If you have some spare Apple hardware about the place, you can hook Buildbox up to it, so you can start running your iOS and Mac builds right away!
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.
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!