All of lore.kernel.org
 help / color / mirror / Atom feed
From: <kazuhiro3.hayashi@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>, <Chris.Paterson2@renesas.com>
Cc: <tho1.nguyendat@toshiba.co.jp>
Subject: RE: Create a shared project to manage LAVA scripts
Date: Wed, 27 Jul 2022 07:56:12 +0000	[thread overview]
Message-ID: <OS3PR01MB1013617091019ACBDDCBD12A5E1979@OS3PR01MB10136.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <16E960C50D86F043.14553@lists.cip-project.org>

Hello Chris,

(Rebooted an old topic...)
I have created a project for this topic in cip-playground:
https://gitlab.com/cip-playground/cip-lava-job-submitter
We'll let you know after the minimum functions to submit LAVA jobs have been implemented.

> Examples:
> https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/blob/master/submit_tests.sh
> https://gitlab.com/cip-project/cip-core/deby/-/tree/cip-core-buster/lava

Please let me know if you have any other projects that should use the functions above.

Best regards,
Kazu

> 
> Hello Chris,
> 
> As I created the issue in deby[0], there are duplicated several scripts / data
> to handle LAVA jobs in multiple CIP projects.
> 
> Examples:
> https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/blob/master/submit_tests.sh
> https://gitlab.com/cip-project/cip-core/deby/-/tree/cip-core-buster/lava
> 
> We are plannning to create a new CIP project that includes common scripts
> to handle such LAVA jobs.
> The new project can be registered as a git submodule in other projects
> (like linux-cip-ci, deby) that depend on the common scripts.
> 
> Do you think this change is reasonable / feasible?
> If you have any other opinions or concerns, please let me konw.
> 
> [0] https://gitlab.com/cip-project/cip-core/deby/-/issues/16
> 
> Best regards,
> Kazu




       reply	other threads:[~2022-07-27  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16E960C50D86F043.14553@lists.cip-project.org>
2022-07-27  7:56 ` kazuhiro3.hayashi [this message]
2022-04-26  7:12 Create a shared project to manage LAVA scripts kazuhiro3.hayashi

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=OS3PR01MB1013617091019ACBDDCBD12A5E1979@OS3PR01MB10136.jpnprd01.prod.outlook.com \
    --to=kazuhiro3.hayashi@toshiba.co.jp \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=tho1.nguyendat@toshiba.co.jp \
    /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.