Timeline for Continuous Integration recommendation for a single private repo Android project hosted on GitHub
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2016 at 4:06 | comment | added | Steve Barnes | @Creos - Jenkins is definitely a "Swiss army knife" but then again unless you are producing a single, highly specialised, custom solution that is to some extent inevitable. It has to be able to do anything. You could probably come up with a much simpler CI system for your specific usage, say a couple of python scripts that checked out multiple copies, did all the builds, ran the tests, etc., but the time spent on it would exceed the time learning & configuring Jenkins. | |
| Jul 21, 2016 at 3:38 | vote | accept | Creos | ||
| Jul 30, 2016 at 20:38 | |||||
| Jul 21, 2016 at 3:38 | comment | added | Creos | ok thanks, i'll look into it... i've used it in the past in a professional environment and my impression of jenkins was that's it's an unwieldy behemoth and kind of... for lack of a better word crappy. however, my impression was pretty superficial and it was some time ago so i'll definitely look into it. thx for the reply, since it's the only one i'll mark it as accepted | |
| Jul 19, 2016 at 7:29 | history | answered | Steve Barnes | CC BY-SA 3.0 |