Hi all, recently CI (bashing?) seems to be major topic here ;) And as a result, some people are working on bringing up a new (homegrown) CI environment for RIOT. However, from what I read in the wiki there was a (working?) Jenkins-CI setup for RIOT in the past, before using/switching to Travis - what happened?
I mean, currently we are talking about setting up a dedicated RIOT-CI - again. Why not revive or start using Jenkins, maybe someone can enlighten me?! However, I think Cenk has a point here: > @all: Do we need a CI-TaskForce? At least it should be defined what are the requirements on a _RIOT-CI_ - mandatory features - nice-to-have stuff - possible CI frameworks For the latter I would rather opt for some well-known implementation, that easily scales to multiple machines. Though Jenkins supports this and has plugins for virtually everything, it is a huge bulk of software and might not be the best fitting CI for RIOT. Briefly said: (IMHO) its no wonder that a free CIs such as Travis cannot handle RIOT with its ever growing community, highly active and dynamic development. Best Sebastian > Am 04.03.2016 um 10:43 schrieb Cenk Gündogan <cenk.guendo...@fu-berlin.de>: > > Hello Carsten, > > Thank you for the hint. > CircleCI looks nice, but its free plan includes only one (concurrent) build > at a time. > I think this won't help much in our case (: > Currently, we have about 11 jobs that need to be processed before one > pull request can be marked as "checked". And each job takes about 40 min > to complete on travis (worst case). > > We definitely have a lot of room for improvement, like grouping > common tests into one test binary, omitting similar boards for > certain tests,.. > > @all: Do we need a CI-TaskForce? > > Best, > Cenk > > On 03.03.2016 20:51, Carsten Bormann wrote: >> Have you looked at CircleCI? >> This seems to be the rage for IETF repos at this point. >> (ISTR I couldn't get it to work for my repos, but I probably just didn't >> try hard enough.) >> >> Grüße, Carsten >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel > > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
