All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 13/13] RFC: Deprecate MAKEALL
Date: Tue, 5 Aug 2014 15:06:55 -0700	[thread overview]
Message-ID: <53E1557F.2060101@freescale.com> (raw)
In-Reply-To: <20140805191026.GD19374@bill-the-cat>

On 08/05/2014 12:10 PM, Tom Rini wrote:
> On Tue, Aug 05, 2014 at 12:01:33PM -0700, York Sun wrote:
>> On 08/05/2014 11:59 AM, Simon Glass wrote:
>>> Hi York,
>>>
>>> On 5 August 2014 12:55, York Sun <yorksun@freescale.com> wrote:
>>>> On 08/05/2014 11:52 AM, Simon Glass wrote:
>>>>>>>
>>>>>>> BTW where does this information get published?
>>>>>>>
>>>>>>
>>>>>> When we use gerrit and Jenkins, the build log is stored in Jenkins log, and
>>>>>> emails were sent with the failure log.
>>>>>
>>>>> OK, I don't think I've send such an email. Do I have to do anything to
>>>>> get them to come to me?
>>>>>
>>>> The emails were sent from Jenkins, by my script collecting information from .ERR
>>>> files.
>>>>
>>>> Maybe I didn't understand your question. What do you mean "where does this
>>>> information get published"?
>>>
>>> I just mean that I don't think I have received an email yet, and don't
>>> know about the service, so am wondering how to get an email.
>>>
>>
>> Simon,
>>
>> Sorry I misled you. The emails are sent by my scripts under Jenkins (A
>> tool, see http://jenkins-ci.org/). It is not within u-boot.
> 
> Would you be able to post your jobs / scripts somewhere?  I've toyed
> with a personal setup and I know Marek has run one before as well.
> Thanks!
> 
Tom,

My script is long and messy. This is the part sending emails.

if ls LOG/*.ERR &>/dev/null; then
  error_msg="'Build failed. Log was sent to $GERRIT_PATCHSET_UPLOADER_EMAIL.'"
  ssh gerrit.hostname.masked gerrit review --message $error_msg
$GERRIT_PATCHSET_REVISION
  /bin/mail -s "Build failed $GERRIT_CHANGE_URL" $GERRIT_PATCHSET_UPLOADER_EMAIL
-c $admin_email < build.result
  exit 1
else
  echo "Passed"
  exit 0
fi

York

  reply	other threads:[~2014-08-05 22:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 14:46 [U-Boot] [PATCH v4 0/13] Add some missing buildman features and deprecate MAKEALL Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 01/13] buildman: Fix a few typos Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 02/13] buildman: Add some notes about moving from MAKEALL Simon Glass
2014-08-05 22:34   ` York Sun
2014-08-05 23:07     ` Simon Glass
2014-08-05 23:21       ` York Sun
2014-08-06  2:15         ` Simon Glass
2014-08-06  2:53           ` York Sun
2014-08-06 14:20             ` Simon Glass
2014-08-06 15:06               ` Tom Rini
2014-08-07 12:12                 ` Simon Glass
2014-08-07 13:14                   ` Masahiro Yamada
2014-08-08 10:59                     ` Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 03/13] buildman: Allow building of current source tree Simon Glass
2014-08-05 18:54   ` Tom Rini
2014-08-05 18:58     ` Simon Glass
2014-08-05 19:01       ` Tom Rini
2014-08-05 14:46 ` [U-Boot] [PATCH v4 04/13] buildman: Move BuilderThread code to its own file Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 05/13] buildman: Sort command line options Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 06/13] buildman: Refactor output options Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 07/13] buildman: Add verbose option to display errors as they happen Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 08/13] buildman: Remove unused non-incremental build method code Simon Glass
2014-08-05 14:46 ` [U-Boot] [PATCH v4 09/13] buildman: Add an option to specify the buildman config file Simon Glass
2014-08-05 14:47 ` [U-Boot] [PATCH v4 10/13] buildman: Add a message indicating there are no errors Simon Glass
2014-08-05 14:47 ` [U-Boot] [PATCH v4 11/13] buildman: Search for *cc instead of *gcc for the compiler Simon Glass
2014-08-05 17:41   ` Jeroen Hofstee
2014-08-05 18:25     ` Simon Glass
2014-08-05 14:47 ` [U-Boot] [PATCH v4 12/13] buildman: Add a few more toolchain examples to the README Simon Glass
2014-08-05 14:47 ` [U-Boot] [PATCH v4 13/13] RFC: Deprecate MAKEALL Simon Glass
2014-08-05 16:43   ` York Sun
2014-08-05 18:41     ` Simon Glass
2014-08-05 18:48       ` York Sun
2014-08-05 18:52         ` Simon Glass
2014-08-05 18:55           ` York Sun
2014-08-05 18:59             ` Simon Glass
2014-08-05 19:01               ` York Sun
2014-08-05 19:10                 ` Tom Rini
2014-08-05 22:06                   ` York Sun [this message]
2014-08-08 21:12                     ` Tom Rini
2014-08-08 21:19                       ` York Sun
2014-08-08 21:30                         ` Tom Rini
2014-08-08 21:36                           ` York Sun

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=53E1557F.2060101@freescale.com \
    --to=yorksun@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.