[U-Boot] [PATCH v4 13/13] RFC: Deprecate MAKEALL

York Sun
2014-08-05T18:48:31Z

On 08/05/2014 11:41 AM, Simon Glass wrote:
> Hi York,
>
> On 5 August 2014 10:43, York Sun <yorksun@freescale.com> wrote:
>> On 08/05/2014 07:47 AM, Simon Glass wrote:
>>> Since buildman now includes most of the features of MAKEALL it is probably
>>> time to talk about deprecating MAKEALL.
>>>
>>> Comments welcome.
>>>
>>
>> Simon,
>>
>> I know buildman has been out for a while. I just rely too much on MAKEALL
>> automation and am reluctant to try buildman.
>>
>> Reading buildman/README, it seems buildman always builds a branch and its
>> upstream commit. I am hoping you can help me to understand how to use buildman
>> in my environment with gerrit and Jenkins. For every patch (internal
>> development), we use gerrit to conduct review and Jenkins to test. If you are
>> not familiar with either, the simplest way to understand is a script will run on
>> every commit. In the script I use MAKEALL to build all concerned (hundreds)
>> targets for _this_ commit. The dependency is maintained by gerrit. The result is
>> fed back to gerrit to show the author (and reviewers) if a failure happens.
>>
>> If using buildman and the upstream commit is always built, a great amount of
>> time will be consumed with no benefit. If you see a better way to use buildman,
>> I can give it a try.
>
> With the v3 or v4 series you can omit the -b option and it will build
> the currently checked-out commit for the selected boards. It might be
> useful in that the problems are stored in files as well as displayed
> on the command line.

I use the .ERR file from MAKEALL. It would be nice to have similar log, in
individual files.

>
> So perhaps you could try that?

I would like to try that.

>
> 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.

York