From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [PATCH] doc: Add basic information about running CI tests
Date: Mon, 21 Dec 2020 11:17:39 +0900 [thread overview]
Message-ID: <20201221021739.GA340859@laputa> (raw)
In-Reply-To: <20201219004442.GT22942@bill-the-cat>
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).
-Takahiro Akashi
>
> --
> Tom
next prev parent reply other threads:[~2020-12-21 2:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 22:14 [PATCH] doc: Add basic information about running CI tests Tom Rini
2020-12-18 23:34 ` Sean Anderson
2020-12-19 0:44 ` Tom Rini
2020-12-21 2:17 ` AKASHI Takahiro [this message]
2020-12-21 13:42 ` Tom Rini
2020-12-21 2:02 ` AKASHI Takahiro
2021-07-27 17:00 ` [PATCHv2] " Tom Rini
2021-07-27 17:01 ` [PATCH] " Tom Rini
2021-08-05 1:19 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201221021739.GA340859@laputa \
--to=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.