From: Tom Rini <trini@konsulko.com>
To: Andrejs Cainikovs <andrejs.cainikovs@gmail.com>
Cc: u-boot@lists.denx.de, Andrejs Cainikovs <andrejs.cainikovs@toradex.com>
Subject: Re: [PATCH v1] CI: Add jsonschema python module
Date: Tue, 29 Aug 2023 11:04:22 -0400 [thread overview]
Message-ID: <20230829150422.GD3953269@bill-the-cat> (raw)
In-Reply-To: <20230829143710.204875-1-andrejs.cainikovs@toradex.com>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
On Tue, Aug 29, 2023 at 04:37:10PM +0200, Andrejs Cainikovs wrote:
> Some TI boards utilizes `ti-board-config` via binman device
> tree node, which when built via binman, triggers schema validation
> for board specific yaml configuration files.
>
> This change adds jsonschema python module to CI Docker image, which
> allows these targets to be built by CI without errors.
>
> Signed-off-by: Andrejs Cainikovs <andrejs.cainikovs@toradex.com>
> ---
> tools/docker/Dockerfile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
> index 3d2b64a355f..2f3121ffcf6 100644
> --- a/tools/docker/Dockerfile
> +++ b/tools/docker/Dockerfile
> @@ -98,6 +98,7 @@ RUN apt-get update && apt-get install -y \
> python2.7 \
> python3 \
> python3-dev \
> + python3-jsonschema \
> python3-pip \
> python3-pyelftools \
> python3-sphinx \
Interesting. How exactly are you using these CI images? We have
tools/buildman/requirements.txt now to cover the newly-added modules in
CI, as we call pip on that. But, it's not being used in the prepopulate
the pip cache stage in the Dockerfile. And, I'm not immune to the idea
that we should instead be installing the distro package here.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-08-29 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 14:37 [PATCH v1] CI: Add jsonschema python module Andrejs Cainikovs
2023-08-29 15:04 ` Tom Rini [this message]
2023-08-29 15:37 ` Andrejs Cainikovs
2023-08-29 21:03 ` Andrejs Cainikovs
2023-09-09 23:20 ` 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=20230829150422.GD3953269@bill-the-cat \
--to=trini@konsulko.com \
--cc=andrejs.cainikovs@gmail.com \
--cc=andrejs.cainikovs@toradex.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox