Location of container files for CI purposes
Christophe Lyon
christophe.lyon@arm.com
Fri Dec 19 15:46:28 GMT 2025
On 12/19/25 13:56, Claudio Bantaloukas via Gcc wrote:
> Hi folks,
> as part of forge integration, Pietro is proposing that we add a workflow
> that checks autogenerated files are consistent with the autoconf
> versions the project uses.
> I've asked Pietro to add his containerfile under contrib/ci-container/
> essential/Containerfile so that this is documented and can be used to
> build the container image used to run the checks on the forgejo runner.
>
> Are there any objections on the use of contrib/ci-container/* for
> documenting such containers?
>
LGTM, it's probably good to have such a dedicated "name space".
> See also https://forge.sourceware.org/gcc/gcc-TEST/pulls/132
I think I've noticed a typo, but this containerfile contains the
packages I add in the current sanity-checks.yaml, so that's good.
I'll update the sanity checks workflow to use that image once built and
deployed.
Thanks,
Christophe
>
> Cheers,
> Claudio
>
>
More information about the Gcc
mailing list