131–140 of 170 posts
There's always Jenkins with Fastlane as an alternative, then again Apple offered the guy that created Fastlane an internship. Maybe Google will put something together for the Android crowd?
And the guy that created it, @krausefx, now actually runs it as a Open Source community project - from within Google where the Fabric team landed after some time at Twitter.
Holy shit. Was looking at the pricing. > $1,037/mo > Billed monthly > 10 Concurrent builds That’s A LOT for 10 concurrent builds... I am sure the product is great, but that pricing is just a jaw drop. Probably a sign of “we are confident this price is worth it.” Anyway, congrat.
Wow, looks like a great opportunity to create a competing service that supports iOS / Android.
Earlier quoted context omitted.
The logic still applies. 1. Start with platform you're most comfortable with. 2. Iterate on product until you have a winning formula 3. Replicate on 2nd platform to double revenues Building is a lot easier than identifying what to build, better to speedily experiment on one platform.
In my opinion the new logic is build in React Native (unless your app fits in the 10% of use cases that won't work well with RN), then deploy to both at once. We have had excellent results.
Curious how those of you who knew about buddybuild heard about it? Seems I hear about companies for the first time when they are either acquired or shutdown.
It was one of the few CI providers that supported MacOS. Since iOS apps can only be legally built on apple hardware, if you were an iOS developer and didn't want to maintain your own mac minis, you knew about them and the few other providers.
Earlier quoted context omitted.
But would you really setup a CI process to automatically build that app? (and one that'll probably cost you at least a 100$ a month)
I would. Every time. I've been happy with bitrise if people are looking for mobile CI alternatives: https://www.bitrise.io/
I recently posted an „Ask HN“ asking for a flexible CI system. Most of the suggestions were proprietary hosted SaaS solutions. I was sceptical, and things like that keep me sceptical. Sure, setting up a CI system yourself is maybe a bit harder than using a hosted solution. But if the provider decides to change their offering, you are in big trouble. You‘ll need to spend a lot of time switching to a new sevice, migrat…
I've built several Jenkins-based CI systems at work. Once you know how to not shoot yourself in the foot, it's really easy. I have 2 cardinal rules: 1) Don't run any jobs on the master box – master is just a web server + master Jenkins app server 2) All build scripts should be part of the project, not configured CI #2 is the more important. Jenkins jobs at my work used to have tons of configuration and plugins, becau…
Earlier quoted context omitted.
I would. Every time. I've been happy with bitrise if people are looking for mobile CI alternatives: https://www.bitrise.io/
Bitrise looks very nice for mobile apps. And it is open source https://www.bitrise.io/cli Are people interested in if we ingrate https://github.com/bitrise-io/bitrise in GitLab Runner so it works with GitLab CI?