From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Fri, 8 Aug 2014 14:19:34 -0700 Subject: [U-Boot] [PATCH v4 13/13] RFC: Deprecate MAKEALL In-Reply-To: <20140808211204.GF19374@bill-the-cat> References: <1407250023-9501-14-git-send-email-sjg@chromium.org> <53E1099E.6080905@freescale.com> <53E126FF.3040503@freescale.com> <53E12899.4050107@freescale.com> <53E12A0D.9030702@freescale.com> <20140805191026.GD19374@bill-the-cat> <53E1557F.2060101@freescale.com> <20140808211204.GF19374@bill-the-cat> Message-ID: <53E53EE6.1000302@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 08/08/2014 02:12 PM, Tom Rini wrote: > On Tue, Aug 05, 2014 at 03:06:55PM -0700, York Sun wrote: >> 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 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. > > Oh I'm sure, but maybe we can help get everyone a better script. For > example, you've said the way your job goes currently is every commit > gets a test. But.. that's not what you need exactly it sounds like. It > sounds like you need a given gerrit issue, which can have a few commits > to it, to be bisectable and compile tested. buildman will handle this > part for you, if you let it. > Tom, I agree buildman has improvements comparing with MAKEALL. I spent time to make Gerrit, Jenkins and MAKEALL work together. It is not easy as one would expect. For now, if I can make builmand to build the last commit, I can replace MAKEALL with buildman. But that seems not working. York