<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px">> It seems that with Gitlab CI you can configure 'runners' on your own<br clear="none"><div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1480531180385_5966" style="display: block;"><div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1480531180385_5965"><div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1480531180385_5964"><div class="y_msg_container" id="yui_3_16_0_ym19_1_1480531180385_5963">hardware for the project(s) that use it, right? So you can install<br clear="none">dependencies and don't need to start with a clean slate for every<br clear="none">build? That has several pro's and cons as compared with Travis. More<br clear="none">DIY, but still with a standardized API.<br clear="none"><br clear="none"><div dir="ltr" id="yui_3_16_0_ym19_1_1480531180385_6097">One other feature-- you can have multiple runners for the same target. So <br></div><div dir="ltr">I could have rpi drones in each timezone running gitlab-runner, and if you <br></div><div dir="ltr">shoot one of them down gitlab ci will pick one of the other 23 for the next <br></div><div dir="ltr">build.</div><div dir="ltr"><br></div><div dir="ltr">It's completely and utter world domination, really.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1480531180385_6113"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1480531180385_6115">-Jonathan<br></div></div> </div> </div> </div></div></body></html>