This gives my current team two months to find a new solution. Buddybuild, aside from the odd issue from time to time, had been a great solution for us. Now we're suddenly wondering where to go next. Not to mention, we now face the question of whether to move our iOS apps off buddybuild as well.
I'm sure your team had an incredibly productive December and are ready to get migrating on the double! Oh, wait, you're probably catching up from a month full of time-off and holidays and were planning on hitting it hard on new features in Jan..
Same boat here, we'd JUST started using BuddyBuild a month or two ago.
>I'm sure your team had an incredibly productive December and are ready to get migrating on the double! Oh, wait, you're probably catching up from a month full of time-off and holidays and were planning on hitting it hard on new features in Jan..
You nailed it. The last thing we want to be doing right now is have to tinker with finding a new CI system. There's too much real work that we have to do. It always takes time to set these things up properly, and reliably. We've used buddybuild for more than a year, and we've long had it to the point where it just worked, and worked reliably.
why not just deploy .... the only thing a CI system does is run a bunch of scripts ... build a bash script and deploy by hand.
Theres an 80/20 rule here, you can get 80% of CI features in 20% of the script you create
Also if you turn down your deployment cycle (once a day, twice a week , etc) you will lessen the problem of lack of a tool , until you find one
CI for me has always been about deployment organization and automation. Its ok to have a bug be fixed by end of day, it doesnt have to be deployed in 15 mins.
Have a look at App Center as well! https://appcenter.ms/ It is easy to setup and supports Android and iOS apps, as well as cross-platform ones. (Disclaimer: I am on that team)
