[U-Boot] [PATCH 1/2] travis-ci: set env vars to name jobs
Stephen Warren
swarren at wwwdotorg.org
Tue Oct 25 01:18:24 CEST 2016
On 10/24/2016 05:03 PM, Tom Rini wrote:
> On Mon, Oct 24, 2016 at 04:41:48PM -0600, Stephen Warren wrote:
>
>> From: Stephen Warren <swarren at nvidia.com>
>>
>> Travis CI names sub-jobs after the first environment variable that is set
>> for a script. This doesn't produce meaningful results for any of the non-
>> buildman jobs. Add a dummy variable to give the jobs meaningful names.
>>
>> Signed-off-by: Stephen Warren <swarren at nvidia.com>
>
> I'm not sure. This un-does in part killing off TEST_CMD as a hook. At
> the end of the day, imho, what is important from travis-ci are the
> emails it sends (which are starting and pass/fail/interrupted) and the
> other notifications.
I don't believe I've ever received emails from Travis, although I
haven't used it in a while so perhaps it's a new feature.
Either way, I do like to look at the web UI to watch/check status
sometimes, and certainly would after a failure to track down the
problem, and this change makes the job list there possible to interpret,
whereas it isn't without it:
https://travis-ci.org/swarren/u-boot/builds/170278972
More information about the U-Boot
mailing list