From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] travis-ci: set env vars to name jobs
Date: Mon, 24 Oct 2016 20:20:55 -0400 [thread overview]
Message-ID: <20161025002055.GQ18591@bill-the-cat> (raw)
In-Reply-To: <e61e4084-2127-3740-65d6-2513a955f3dd@wwwdotorg.org>
On Mon, Oct 24, 2016 at 05:18:24PM -0600, Stephen Warren wrote:
> 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@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@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.
Ah, https://docs.travis-ci.com/user/notifications#Email-notifications
explains and it's setup by default to not spam uninterested parties.
Which I think in turn means it also doesn't email interested parties
easily, sadly.
> 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
Yeah, I spent a lot of time with the UI when I was doing the last
series. And since it is indeed harder to get email notifications than I
would like, this makes sense too.
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161024/c2c7fc46/attachment.sig>
next prev parent reply other threads:[~2016-10-25 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 22:41 [U-Boot] [PATCH 1/2] travis-ci: set env vars to name jobs Stephen Warren
2016-10-24 22:41 ` [U-Boot] [PATCH 2/2] travis-ci: remove duplicate build Stephen Warren
2016-10-24 23:04 ` Tom Rini
2016-10-29 17:41 ` [U-Boot] [U-Boot,2/2] " Tom Rini
2016-10-24 23:03 ` [U-Boot] [PATCH 1/2] travis-ci: set env vars to name jobs Tom Rini
2016-10-24 23:18 ` Stephen Warren
2016-10-25 0:20 ` Tom Rini [this message]
2016-10-29 17:40 ` [U-Boot] [U-Boot,1/2] " Tom Rini
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=20161025002055.GQ18591@bill-the-cat \
--to=trini@konsulko.com \
--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