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

Apple acquires Buddybuild

buddybuild.com

Post reply on HN
Print view View original

101–110 of 170 posts

Re: Apple acquires Buddybuild

#101

Post by Pharaoh2 »

sargun wrote: post #13
jakobegger wrote: post #8

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…

There is Buildkite, which a hybrid server side / client side solution. This has worked extraordinarily because one of the most frustrating parts of setting up a CI service is setting up a long-lived, reliable server.

Not a reasonable replacement as maintaining your own mac servers is non-trivial and all the major cloud providers don't have mac as hardware options.

Re: Apple acquires Buddybuild

#102

Post by Pharaoh2 »

favorited wrote: post #39
jakobegger wrote: post #8

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…

Not a reasonable replacement as maintaining your own mac servers is non-trivial and all the major cloud providers don't have mac as hardware options.

Re: Apple acquires Buddybuild

#103

Post by Pharaoh2 »

rectang wrote: post #33
jakobegger wrote: post #8

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…

This is where open source projects with open governance offer peace of mind over proprietary offerings. Community stakeholders get a say in how the project evolves -- decisions are not made solely on what offers the best value for the platform's investors.

Hard part in this case is not the actual build code or even the CI runners, its actually maintaining a mac server farm for your builds. None of the major cloud providers have mac hardware options.

Buddybuild and very few other CI systems have iOS and Android support.

Re: Apple acquires Buddybuild

#104

Post by LeoNatan25 »

skywhopper wrote: post #86
pm90 wrote: post #31

Earlier quoted context omitted.

Apple is notoriously bureaucratic. So its not surprising that innovation is stifled. I really hate this duality b/w innovation and stability... perhaps if more startups were focused on longer term survivability, it would be better for society overall?

Innovation and stability are tautologically in opposition to each other, alas.

No, they are perpendicular. An optimal path can be found so that both advance in the desired direction.

Re: Apple acquires Buddybuild

#105

Post by favorited »

Pharaoh2 wrote: post #102
favorited wrote: post #39

Earlier quoted context omitted.

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…

Not a reasonable replacement as maintaining your own mac servers is non-trivial and all the major cloud providers don't have mac as hardware options.

Except the parent comment wasn't asking about a cloud-based replacement. They specifically mentioned setting up a CI environment yourself.

Re: Apple acquires Buddybuild

#106

Post by vivekmgeorge »

Personally, I think this is the fairly useless move by Apple. Being able to build apps easier will not change this dead ecosystem. Easier ways to market apps, get them into the hands of users, and remind ppl to use the apps they downloaded is what's needed. Facebook, Google and Apple consume all free of users.

Re: Apple acquires Buddybuild

#107

Post by favorited »

peteretep wrote: post #68
favorited wrote: post #39

Earlier quoted context omitted.

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…

At that point, is there much point in using Jenkins? Aren't there much lighter weight alternatives?

If you know a good one, definitely let me know. Generally the only constraints are open source with a permissive license & on-premises installs.

One benefit is it can already integrate with whatever else is out there. When we switched from GitLab to GitHub Enterprise at work, our CI environment just needed to point somewhere else.

Re: Apple acquires Buddybuild

#108

Post by thisisit »

st3fan wrote: post #29

I'm happy for the founders, this is probably a good and profitable exit for them. But as a customer I am really sad and disappointed. Apple has a very bad reputation when it comes to taking over products like this. TestFlight is the prime example. TestFlight basically disappeared for a year until coming back as a more limited and slower Apple branded service. And by slow I mostly mean, it takes 6 months for bugs to b…

Sometimes I wonder - isn't that an opportunity in disguise for another shop to fill the gaps? Or I am missing something?

Re: Apple acquires Buddybuild

#109

Post by asdjasldkjkljd »

skywhopper wrote: post #86
pm90 wrote: post #31

Earlier quoted context omitted.

Apple is notoriously bureaucratic. So its not surprising that innovation is stifled. I really hate this duality b/w innovation and stability... perhaps if more startups were focused on longer term survivability, it would be better for society overall?

Innovation and stability are tautologically in opposition to each other, alas.

Right, if you innovate too quickly you end up with major security issues like root login with a blank password.

Re: Apple acquires Buddybuild

#110

Post by nathanvanfleet »

st3fan wrote: post #83
jagger27 wrote: post #78

Earlier quoted context omitted.

I wonder if Apple's satellite operations (like the Siri team in Ottawa, Canada, for example) might have some autonomy and self direction simply due to distance from the mothership. As for a shift in startup culture, what is more tempting than 5 to 10 years of hard work into billion dollar exits? Local governments could start offering tax incentives that build over time—or more aggressively, have steep disincentives o…

Siri team in Ottawa? I find that hard to believe. Why would such an important team not be on the main campus?

That explains why Siri doesn't understand beanie but knows the word "toque"
Post reply on HN