From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Sun Date: Tue, 5 Aug 2014 09:43:10 -0700 Subject: [U-Boot] [PATCH v4 13/13] RFC: Deprecate MAKEALL In-Reply-To: <1407250023-9501-14-git-send-email-sjg@chromium.org> References: <1407250023-9501-1-git-send-email-sjg@chromium.org> <1407250023-9501-14-git-send-email-sjg@chromium.org> Message-ID: <53E1099E.6080905@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/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. Regards, York