From mboxrd@z Thu Jan  1 00:00:00 1970
From: Heiko Schocher <hs@denx.de>
Date: Thu, 25 Aug 2016 06:28:21 +0200
Subject: [U-Boot] [ANN] U-Boot v2016.09-rc2 released
In-Reply-To: <20160824090107.15fee279@jawa>
References: <20160823003842.GM5342@bill-the-cat> <20160824090107.15fee279@jawa>
Message-ID: <57BE73E5.9060304@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hello Lukasz,

Am 24.08.2016 um 09:01 schrieb Lukasz Majewski:
> Hi Tom,
>
>> A non-code change is that now I have Jenkins setup to automatically
>
> Jenkins - brrr.... I've had a really hard time with this "peculiar"
> piece of SW.
>
> Run away from it if you still can....

I have no experience with jenkins, but plan a tbot integration
for it ... Uh... why is it so bad?

> I've switched to buildbot a few months ago and that was _REALLY_ good
> decision.

I use buildbot too on my raspberry pi in conjunction with tbot.
See for an example [1] (currently some boards not really working, I have
to look at it ...)

I failed to integrate for example some images tbot creates at the end,
also results from test/py into buildbot ... so I created a tbot event
backend, which writes some results into a mySQL database and made a
really simple php script ... see [2]

> A few pros:
> - It is written in python, so if I need to extend it, then I write code
>    (not write in groovy) and use SCM to store the changes
> - It's web interface is far more readable than Jenkins (this is what
>    non-tech people say)
> - It is smaller project, with things which are really needed.

Ah, yes ... and at the end buildbot was the reason why I started
with tbot (and writting it in python).

bye,
Heiko
[1] http://xeidos.ddns.net/buildbot/tgrid
[2] http://xeidos.ddns.net/tests/test_db_auslesen.php
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany