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!