Show HN: No-Code CI for Android
turingci.com
Show HN: No-Code CI for Android
1–10 of 19 posts
Re: Show HN: No-Code CI for Android
#2> Unlimited build minutes. No hidden costs. $7 per month per CI pipeline.
wow. how is this viable for them :
Re: Show HN: No-Code CI for Android
#3> Unlimited build minutes. No hidden costs. $7 per month per CI pipeline. wow. how is this viable for them :
author here - we are using spot instances on GCP for executing the pipeline which at 10 hrs/day usage makes us $1 in profit/month :)
Re: Show HN: No-Code CI for Android
#4> Unlimited build minutes. No hidden costs. $7 per month per CI pipeline. wow. how is this viable for them :
author here - we are using spot instances on GCP for executing the pipeline which at 10 hrs/day usage makes us $1 in profit/month :)
might I recommend figuring something else out because... that sucks :)
Re: Show HN: No-Code CI for Android
#5Earlier quoted context omitted.
author here - we are using spot instances on GCP for executing the pipeline which at 10 hrs/day usage makes us $1 in profit/month :)
might I recommend figuring something else out because... that sucks :)
hehe - actually I am an Android dev primarily and I thought that starting a project without CI sucks way more. So I built this for myself and was happy paying $7/mo for not having to spend weeks+$$$ on setting one up with current solutions.
Spot instances do take upto ~2 mins to come up so probably a turbo add-on that devs will feel happy paying for or please feel free to suggest.
Re: Show HN: No-Code CI for Android
#6> Unlimited build minutes. No hidden costs. $7 per month per CI pipeline. wow. how is this viable for them :
author here - we are using spot instances on GCP for executing the pipeline which at 10 hrs/day usage makes us $1 in profit/month :)
How does Turing handle the instances being terminated? Does it just start again from the beginning?
Re: Show HN: No-Code CI for Android
#7Earlier quoted context omitted.
author here - we are using spot instances on GCP for executing the pipeline which at 10 hrs/day usage makes us $1 in profit/month :)
How does Turing handle the instances being terminated? Does it just start again from the beginning?
We deploy the pipeline as a kubernetes job, once the build completes and posts logs/artifacts (apk) -- the job is archived and pods are evicted. So yes, starts from the beginning.
Re: Show HN: No-Code CI for Android
#8Earlier quoted context omitted.
author here - we are using spot instances on GCP for executing the pipeline which at 10 hrs/day usage makes us $1 in profit/month :)
might I recommend figuring something else out because... that sucks :)
Yeah, if there's no space for an extended period of time the service will be useless, with an endless backlog of jobs.
Re: Show HN: No-Code CI for Android
#9This looks really cool. I don't have a need for it now, but if I did this seems like a strong contender.
I'd have someone copyedit it, though. For example you have "pre" instead of "per". Also the sentence "Team needs to staff dedicated release engineer to handle the task with their already limited resources." is grammatically incorrect and gives off the impression that this was built by someone who's ESL. May be true, may not be true, has no connection to how good a tool it is but some people might misinterpret it that way.
Idiomatic ways to write that would include "Teams need dedicated release engineers", "Teams need a dedicated release engineer", and others.
Re: Show HN: No-Code CI for Android
#10> Unlimited build minutes. No hidden costs. $7 per month per CI pipeline. wow. how is this viable for them :
author here - we are using spot instances on GCP for executing the pipeline which at 10 hrs/day usage makes us $1 in profit/month :)
I’d guess that’s for a fairly slow machine, or else the prices would be pretty high?
What sort of spec machine (or kubernetes pod) are you providing for that?