On Tue, Aug 29, 2023 at 05:37:35PM +0200, Andrejs Cainikovs wrote:
> On 29/08/2023 17:04, Tom Rini wrote:
> > 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 b
On 29/08/2023 17:37, Andrejs Cainikovs wrote:
> On 29/08/2023 17:04, Tom Rini wrote:
>> 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 prepopu
On 29/08/2023 17:04, Tom Rini wrote:
> 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,
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
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.
Si
5 matches
Mail list logo
