Hey Martine, Hi all, > Am 04.03.2016 um 14:15 schrieb Martine Lenders <authmille...@gmail.com>: > > The reason why we stopped using Jenkins is exactly that. Additionally nobody > of us (at least then) was really fond of Java but good Java knowledge is > pretty much required to get the patchwork of Plug-ins running that were > needed just to build PRs from GitHub. This was at least how I, one of the > main maintainers for the CI server was experiencing it. Yeah, I perfectly understand ... I don't really _like_ Jenkins for its Java "dependencies", too ;-)
However, I helped some guys at my working group to setup a neat Jenkins environment for several C++ projects. The master and all workers are VMs, we add workers according to any requirement (specific OS, compiler versions etc.) on demand and delete old ones, if no longer needed. All in all it works like charm, they even use Github integration ... somehow ... but I know they have some trouble with that, too. IMHO a master-slave concept (as in Jenkins) with ability to add worker nodes on demand and thereby dynamically add/remove resources is very desirable for a _RIOT-CI_ as well and would enable future scale-out to cope with growth of RIOT. And for instance, before an Hack'n'Ack or the next major release one could add free resources (e.g., some servers from other projects or desktop PCs idling around) and crunch all the pull-request in advance, trigger additional tests and builds for verification as needed ... zzZzZZ ... Sweet dreams :) Yet again: Jenkins might not be the right choice for RIOT, especially if Github integration is not working properly -- but there are lots of other CI frameworks around. But as always, setup and maintenance of such a CI requires resources too, i.e., time and people. Cheers, Sebastian _______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
