All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin via lustre-devel <lustre-devel@lists.lustre.org>
To: Xinliang Liu <xinliang.liu@linaro.org>
Cc: Jian Yu <jiyu@whamcloud.com>, Li Xi <lixi@ddn.com>,
	"cloud-dev-request@op-lists.linaro.org"
	<cloud-dev-request@op-lists.linaro.org>,
	Xinliang Liu via lustre-devel <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] Lustre Arm stuff status and work plan
Date: Tue, 28 Dec 2021 01:58:51 +0000	[thread overview]
Message-ID: <023CD146-E2BA-4B03-9459-C480E51EBE7E@whamcloud.com> (raw)
In-Reply-To: <CAKoKPbxQymhN93F5oM_TxK6y0kk5_bv3p62FncUz6Ri_0jmABw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 838 bytes --]



On Dec 27, 2021, at 8:53 PM, Xinliang Liu <xinliang.liu@linaro.org<mailto:xinliang.liu@linaro.org>> wrote:

Maloo is just one place to link to to actually let people see the results, but you can link to external resources too
like e.g. gatekeeper janitor helper does or assuming the information is small enough it could be entirely contained
in the comment (like say for a build failure)

Ok, understand now. Is there any other reference external CI that posts results to Lustre gerrit now?

Currently there are:
- checkpatch and Misc code checks (smach) that post their results as 100% comment only. they share codebase pretty much
- the Janitor (also started with above codebase but got changed and extended a lot)

There was external interest in the past to post results to gerrit but it never materialized in the end

[-- Attachment #1.2: Type: text/html, Size: 1614 bytes --]

[-- Attachment #2: Type: text/plain, Size: 165 bytes --]

_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org

  reply	other threads:[~2021-12-28  1:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16  8:23 [lustre-devel] Lustre Arm stuff status and work plan Xinliang Liu via lustre-devel
2021-12-20  2:30 ` Xinliang Liu via lustre-devel
2021-12-23  7:43   ` Oleg Drokin via lustre-devel
2021-12-27  7:56     ` Xinliang Liu via lustre-devel
2021-12-27 15:23       ` Oleg Drokin via lustre-devel
2021-12-28  1:53         ` Xinliang Liu via lustre-devel
2021-12-28  1:58           ` Oleg Drokin via lustre-devel [this message]
2022-02-18  8:05             ` Kevin Zhao via lustre-devel
2022-02-28  5:36               ` Oleg Drokin via lustre-devel
2022-03-11  8:28                 ` Kevin Zhao via lustre-devel
2022-03-15 22:09                   ` [lustre-devel] [EXTERNAL] " Simmons, James via lustre-devel
2022-03-16  1:25                     ` Kevin Zhao via lustre-devel
2022-03-18 22:46                       ` Simmons, James via lustre-devel
2022-03-20 12:26                         ` Kevin Zhao via lustre-devel
2022-03-29  7:37                 ` [lustre-devel] " Kevin Zhao via lustre-devel
2022-03-29 12:51                   ` Peter Jones via lustre-devel

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=023CD146-E2BA-4B03-9459-C480E51EBE7E@whamcloud.com \
    --to=lustre-devel@lists.lustre.org \
    --cc=cloud-dev-request@op-lists.linaro.org \
    --cc=green@whamcloud.com \
    --cc=jiyu@whamcloud.com \
    --cc=lixi@ddn.com \
    --cc=xinliang.liu@linaro.org \
    /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.