Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

news.ycombinator.com

Post reply on HN
Print view View original

41–50 of 60 posts

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#41

Post by dennispi »

thebloodrabbit wrote: post #36
joeblau wrote: post #35

I've been using Buddy Build and I really enjoy their environment. How does this compare to that?

Good question! The main differentiator might be that our platform is more open compared to Buddybuild's enclosed ecosystem approach. That means we allow much more customizability while having the same, fast initial project setup. Bitrise grows with the community, both by helping each other and developing extensions, like new steps/integrations and other tools. We feel that Buddybuild is great for smaller projects, bu…

As one of the Founders of buddybuild, I'd like to perhaps also provide another perspective on this specific thread.

We certainly don't think of buddybuild as a closed ecosystem.

In fact, our users are able to customize buddybuild infinitely to meet the needs of their workflow (details can be found here: https://www.buddybuild.com/blog/customizing-the-build-proces...)

Further, while buddybuild is favored by thousands of because it can can auto-provision iOS devices for you on the fly. Meaning, you never have to deal with provisioning profiles and UDIDs ever again.

We also care deeply about making sure that teams can involve and engage their end users as part of the development process. One of the reasons we built buddybuild is because of the frustration sending builds to our users... AND then never hearing back from them. Phones are great devices for "consuming content", but it became obvious that the physical form factor of the device tends to result in infrequent feedback which was often ambiguous.

So, we build an SDK that gives you high quality and actionable bug reports from beta users. With a simple screenshot, testers can file bug reports that include graphically annotated screenshots, feedback notes and their device metadata.

We also have a feature called "Instant Replay", which lets you watch a video of the exact steps required to reproduce a crash. Instant Replay works in conjunction with our Crash Reporting solution to offer you both the exact lines of code that caused a crash as well as the exact sequence of events that lead up to it (https://www.buddybuild.com/blog/introducing-instant-replay)

Thousands of teams with fairly complex needs use buddybuild every single day. They teams like Slack, Meetup, FireFox, Wordpress and others..

You can read why they made the choice to use buddybuild here: http://www.buddybuild.com/customers

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#43

Post by birmacher »

chrisstott wrote: post #40

I just wanted to extend congratulations from the team at buddybuild! It's awesome to see the mobile developer tools ecosystem as a whole expanding. It wasn't too long ago that mobile teams had to use web CI products, awkwardly repurposed to build & deploy their iOS and Android apps - imposing on them a huge maintenance burden and slowing down the development of their apps. Great tools help build great products, and t…

Thanks Chris, that's very kind of you all!

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#44

Post by thebloodrabbit »

pavlakoos wrote: post #42

How does it compare to Jenkins?

- First and foremost, the biggest advantage is that it's hosted. You can forget about having and maintaining your own build machines. Every build you kick off will start from the same clean VM, thus never giving you a false positive/negative.

- No need to worry about tooling maintenance anymore. Best example is when a new Xcode version is released, usually lots of things break. We test these out quickly and release the new version in a way that won't give you headache.

- You have the same kind of control over your build environment, but an easier time with project setup with our scanner and reusable steps. This means, you can do scripting, but you don't have to.

- Team and organization management features

- You don't lose the advantages of open source

- You get awesome tech support along with a very helpful community

- You get a much more intuitive and nicer UI/UX

We hear from a lot of our users coming from Jenkins how it took up more time for them to maintain the build machines than it actaully saved, while not always delivering proper build results, lacking the always clean kickoff state.

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#45

Post by the_greyd »

A small nitpick with your website. In your front slideshow "as a service" is moving(forward or backward depending on the term) as new terms take place in front of it. It would look better if it didn't move (and the words expanded on the left for the space they needed).

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#46

Post by thebloodrabbit »

the_greyd wrote: post #45

A small nitpick with your website. In your front slideshow "as a service" is moving(forward or backward depending on the term) as new terms take place in front of it. It would look better if it didn't move (and the words expanded on the left for the space they needed).

Thanks for the feedback! Took a note to fix that ;)

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#48

Post by christop »

thebloodrabbit wrote: post #34
christop wrote: post #33

Do the Docker containers that builds run in still provide root access to the Docker socket, allowing people to break out of the container?

You have passwordless sudo access on the Docker containers, however when you kick off a new build we will create a new VM just for the build and start the docker container inside it, making sure that nobody can ramble around :)

Thanks. Is this setup with the per-build VM and Docker server access intended so that users could set up multiple linked containers for integration testing, etc.?

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#49

Post by birmacher »

christop wrote: post #48
thebloodrabbit wrote: post #34

Earlier quoted context omitted.

You have passwordless sudo access on the Docker containers, however when you kick off a new build we will create a new VM just for the build and start the docker container inside it, making sure that nobody can ramble around :)

Thanks. Is this setup with the per-build VM and Docker server access intended so that users could set up multiple linked containers for integration testing, etc.?

Yup, we wanted to give you full access during the build, to achieve whatever you would like to do.

Re: Launch HN: Bitrise (YC W17) – Continuous Integration and Delivery for Mobile Apps

#50

Post by jinthagerman »

Love bitrise!

Customer support is great. They get actively involved with the community to solve issues. Great example was a tweak to access control in sierra meant builds hung. Bitrise worked on a solution with the fastlane guys.

Platform is rock solid.

Post reply on HN