From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2016.09-rc2 released
Date: Thu, 25 Aug 2016 06:28:21 +0200 [thread overview]
Message-ID: <57BE73E5.9060304@denx.de> (raw)
In-Reply-To: <20160824090107.15fee279@jawa>
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
next prev parent reply other threads:[~2016-08-25 4:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 0:38 [U-Boot] [ANN] U-Boot v2016.09-rc2 released Tom Rini
2016-08-24 7:01 ` Lukasz Majewski
2016-08-24 16:04 ` Tom Rini
2016-08-25 4:28 ` Heiko Schocher [this message]
2016-08-26 7:23 ` Andreas Bießmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57BE73E5.9060304@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox