From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 21 Dec 2020 08:42:46 -0500 Subject: [PATCH] doc: Add basic information about running CI tests In-Reply-To: <20201221021739.GA340859@laputa> References: <20201218221456.14712-1-trini@konsulko.com> <3ae99d1d-bbc2-d044-81e7-0aa527614cdd@gmail.com> <20201219004442.GT22942@bill-the-cat> <20201221021739.GA340859@laputa> Message-ID: <20201221134246.GZ22942@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Dec 21, 2020 at 11:17:39AM +0900, AKASHI Takahiro wrote: > On Fri, Dec 18, 2020 at 07:44:42PM -0500, Tom Rini wrote: > > On Fri, Dec 18, 2020 at 06:34:10PM -0500, Sean Anderson wrote: > > > On 12/18/20 5:14 PM, Tom Rini wrote: > > > > Start out by documenting general expectations on when CI is run, how > > > > anyone can run Azure pipelines, and how GitLab CI pipelines can be run. > > > > > > Should travis be documented as well? > > > > Travis is being dropped as travis-ci.org is ending and travis-ci.com > > offers too small of a number of build minutes for free to be useful to > > us. > > It would make little sense to run the whole set of test cases on Travis, > but I have used Travis until recently in order to run a small set of test > scenario, for example, limiting the scope to > buildman catch-all AArch64 > test/py sandbox > test/py qemu-x86_64 > by modifying .travis.yml. > > Since going through the all test paths is a time-consuming task any way, > it always makes sense for me to run some critical tests first locally > (without revealing those activities in public). Yes, but you can do that for Azure/GitLab too. I'll expand on that in v2, along with your other feedback. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: