[riot-devel] RIOT's CI system
thomas at riot-os.org
Mon Mar 20 19:17:07 CET 2017
thank you for sharing the results and thanks a lot to everyone involved
for their contributions to finally reduce the increasingly confusing
"Checks" section in github PRs.
Reading the document provided it seems to me that Jenkins actually
got a better score than Murdock 2. (Please tell me if I am mistaken
and misinterpret the table.)
Because of this I'd very much appreciate a little bit more of
on why this group came to the conclusion Murdock 2 is still better
fitting RIOT than Jenkins.
I do not intend to bash the task force results just try to better
understand the reasoning.
On 20 Mar 2017, at 10:13 PDT(-0700), Oleg Hahm wrote:
> Dear robust IOTlers,
> as you probably know we're currently running three CI systems in
> Murdock, Jenkins and Murdock 2, where the first one is the
> authoritative CI
> system and the other two are under test. Since these two last systems
> distributed deployment - a must-have feature for us - we need to
> Murdock with one of it.
> In order to decide whether we should use Jenkins or Murdock 2, a task
> was formed to deploy and thoroughly evaluate both systems. This task
> finally defined 34 criteria categorized into Web UI, GitHub Interface,
> Performance, Operation, Maintenance, Security, and Extensibility for
> evaluation. The outcome was that both tools seem to fulfill the
> satisfactorily well. You can find the result of the evaluation at .
> Hence, it was a close call, but eventually, we (the members of the
> task force)
> agreed that we want to switch to Murdock 2 as the default CI system.
> Murdock 2
> is currently developed by Kaspar particular for the needs of RIOT and
> therefore simplifies configuration. It is also seems to scale better
> outperform Jenkins.
> Please let us know if you disagree with our assessment and object
> switching to
> Murdock 2 as the authoritative CI.
> printk("ip6t_hook: happy cracking.\n");
> devel mailing list
> devel at riot-os.org
More information about the devel