Thanks to everyone who responded and especially to Alexander. Alexander, your
patch fixed the problem and the test suite -- many thanks!
On 26 Jan 2024, at 13:28, Alexander Fedorov wrote:
> I *think* it should be enough to simply use an intermediate variable
> (say IMAGE) in the matrix and job
I *think* it should be enough to simply use an intermediate variable
(say IMAGE) in the matrix and job templates.
Please find a patch that *may* solve the problem attached.
Best regards,
Fedorov Alexander.
On Fri, 26 Jan 2024 at 19:43, Alexander Fedorov wrote:
>
> Hello,
>
> It seems that
Hello,
It seems that `image` is not a variable, but a "job keyword", and thus
cannot be directly set in the matrix.
https://docs.gitlab.com/ee/ci/yaml/?query=image
> Keyword type: Job keyword. You can use it only as part of a job or in the
> default section.
Best regards,
Fedorov Alexander.
Would it be that the images were created with the exact same
Dockerfile recipe in different environments? Docker could be doing the
caching wrong because it ignores the environment when caching. A
solution is to modify at least one byte in the Dockerfile—when I
generate Dockerfile's, I include a
I have created a new docker image for Allegro CL version 11.0
(express/free), and put it on DockerHub:
https://hub.docker.com/repository/docker/rpgoldman/allegro11express/general
I have tried to add regression and upgrade tests using this Docker Image
-- see [Regression
