Show HN: No-Code CI for Android | Hacker News Reader

Show HN: No-Code CI for Android

turingci.com

36 pointsshipit18 comments

This 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.

Thank you! And you are correct -- I am indeed ESL :) tbh writing the copy for landing site has taken me longer than some of the code :p

I shall revisit with fresh eyes and get it sorted out. Thank you! Please keep us in mind whenever you do need CI.

No problem! Congratulations one the launch.

> 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 :)

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.

Yeah, if there's no space for an extended period of time the service will be useless, with an endless backlog of jobs.

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.

Just curious- is it built on Tekton? :) Have been tempted to play around with it.

ah no - just plain old Vue, Go, and k8s :)

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?

its a `2 vCPU, 7.5GB RAM` -- so far tested with open source projects including NDK and it stood up pretty well. Build times post close to what it would take on the local dev machine. Overall experience is that once you push your commit in about `2 mins + (local build time) mins` you'll get an email with the CI result.

Product wise we don't want the user to worry about machine resources as long as CI executes within reasonable time.

We can rent CPU/RAM in the cloud by the minute, but we can’t do that with the computer we’re developing on locally. I think this should naturally leads to faster builds being done in CI, more cost effectively, rather than CI being the slower builds.

Out of interest, have you modelled spot instance restarts into your costs? How about spot instance pricing going up?

The logo on their website doesn't load properly for me. My machine doesn't have the font "LucidaGrande" and if they read this, make sure you outline your text before exporting!

Is there something similar for iOS?

we're working on it as we speak! we'll keep you informed or just drop us an email listed on the site

Reply on news.ycombinator.com