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 test](https://gitlab.common-lisp.net/asdf/asdf/-/blame/allegro-resize-areas/gitlab...) and [Upgrade test](https://gitlab.common-lisp.net/asdf/asdf/-/blob/allegro-resize-areas/gitlab-...).
Unfortunately, these tests don't work! They print the right information at the head of [the job]():
Regression test: [allegro, rpgoldman/allegro11express, modern] :
But they pull the wrong docker image:
``` Using Docker executor with image containers.common-lisp.net/cl-docker-images/allegro:latest ... Authenticating with credentials from job payload (GitLab Registry) Pulling docker image containers.common-lisp.net/cl-docker-images/allegro:latest ... Using docker image sha256:d0fc75f61208fa39497f5ae2188d6d70d4b65ae513105dbdf80f85b41a45ffdc for containers.common-lisp.net/cl-docker-images/allegro:latest with digest containers.common-lisp.net/cl-docker-images/allegro@sha256:e16f3a55a2d829732a438c363dc6905754c46ca595e868377ed61faeeda44fdb ... ```
Does anyone on the list understand GitLab pipelines well enough to tell me why my `image` variable binding in "Regression test" and "Upgrade test" doesn't clobber the value from the template? Or, even more oddly, why it seems to half-way clobber it, giving the right info print, but pulling the wrong image?
Sorry to bother the list, but I'm at my wits end and the debugging tools and documentation are somewhere between horrible and non-existent.
Thanks for any advice,
R
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 sha256 of the environmental contents as a value to be printed while generating the image.
Then again, yours could be a completely different problem.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org “Once upon a time, there was a person whose life was so good there was no story to tell about it.” — Foer
On Fri, Jan 26, 2024 at 12:03 PM Robert Goldman rpgoldman@sift.net wrote:
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 test and Upgrade test.
Unfortunately, these tests don't work! They print the right information at the head of the job:
Regression test: [allegro, rpgoldman/allegro11express, modern] :
But they pull the wrong docker image:
Using Docker executor with image containers.common-lisp.net/cl-docker-images/allegro:latest ... Authenticating with credentials from job payload (GitLab Registry) Pulling docker image containers.common-lisp.net/cl-docker-images/allegro:latest ... Using docker image sha256:d0fc75f61208fa39497f5ae2188d6d70d4b65ae513105dbdf80f85b41a45ffdc for containers.common-lisp.net/cl-docker-images/allegro:latest with digest containers.common-lisp.net/cl-docker-images/allegro@sha256:e16f3a55a2d829732a438c363dc6905754c46ca595e868377ed61faeeda44fdb ...
Does anyone on the list understand GitLab pipelines well enough to tell me why my image variable binding in "Regression test" and "Upgrade test" doesn't clobber the value from the template? Or, even more oddly, why it seems to half-way clobber it, giving the right info print, but pulling the wrong image?
Sorry to bother the list, but I'm at my wits end and the debugging tools and documentation are somewhere between horrible and non-existent.
Thanks for any advice,
R
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.
On Fri, 26 Jan 2024 at 18:03, Robert Goldman rpgoldman@sift.net wrote:
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 test and Upgrade test.
Unfortunately, these tests don't work! They print the right information at the head of the job:
Regression test: [allegro, rpgoldman/allegro11express, modern] :
But they pull the wrong docker image:
Using Docker executor with image containers.common-lisp.net/cl-docker-images/allegro:latest ... Authenticating with credentials from job payload (GitLab Registry) Pulling docker image containers.common-lisp.net/cl-docker-images/allegro:latest ... Using docker image sha256:d0fc75f61208fa39497f5ae2188d6d70d4b65ae513105dbdf80f85b41a45ffdc for containers.common-lisp.net/cl-docker-images/allegro:latest with digest containers.common-lisp.net/cl-docker-images/allegro@sha256:e16f3a55a2d829732a438c363dc6905754c46ca595e868377ed61faeeda44fdb ...
Does anyone on the list understand GitLab pipelines well enough to tell me why my image variable binding in "Regression test" and "Upgrade test" doesn't clobber the value from the template? Or, even more oddly, why it seems to half-way clobber it, giving the right info print, but pulling the wrong image?
Sorry to bother the list, but I'm at my wits end and the debugging tools and documentation are somewhere between horrible and non-existent.
Thanks for any advice,
R
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 varedif.a.s@gmail.com wrote:
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.
On Fri, 26 Jan 2024 at 18:03, Robert Goldman rpgoldman@sift.net wrote:
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 test and Upgrade test.
Unfortunately, these tests don't work! They print the right information at the head of the job:
Regression test: [allegro, rpgoldman/allegro11express, modern] :
But they pull the wrong docker image:
Using Docker executor with image containers.common-lisp.net/cl-docker-images/allegro:latest ... Authenticating with credentials from job payload (GitLab Registry) Pulling docker image containers.common-lisp.net/cl-docker-images/allegro:latest ... Using docker image sha256:d0fc75f61208fa39497f5ae2188d6d70d4b65ae513105dbdf80f85b41a45ffdc for containers.common-lisp.net/cl-docker-images/allegro:latest with digest containers.common-lisp.net/cl-docker-images/allegro@sha256:e16f3a55a2d829732a438c363dc6905754c46ca595e868377ed61faeeda44fdb ...
Does anyone on the list understand GitLab pipelines well enough to tell me why my image variable binding in "Regression test" and "Upgrade test" doesn't clobber the value from the template? Or, even more oddly, why it seems to half-way clobber it, giving the right info print, but pulling the wrong image?
Sorry to bother the list, but I'm at my wits end and the debugging tools and documentation are somewhere between horrible and non-existent.
Thanks for any advice,
R
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 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 varedif.a.s@gmail.com wrote:
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.
On Fri, 26 Jan 2024 at 18:03, Robert Goldman rpgoldman@sift.net wrote:
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 test and Upgrade test.
Unfortunately, these tests don't work! They print the right information at the head of the job:
Regression test: [allegro, rpgoldman/allegro11express, modern] :
But they pull the wrong docker image:
Using Docker executor with image containers.common-lisp.net/cl-docker-images/allegro:latest ... Authenticating with credentials from job payload (GitLab Registry) Pulling docker image containers.common-lisp.net/cl-docker-images/allegro:latest ... Using docker image sha256:d0fc75f61208fa39497f5ae2188d6d70d4b65ae513105dbdf80f85b41a45ffdc for containers.common-lisp.net/cl-docker-images/allegro:latest with digest containers.common-lisp.net/cl-docker-images/allegro@sha256:e16f3a55a2d829732a438c363dc6905754c46ca595e868377ed61faeeda44fdb ...
Does anyone on the list understand GitLab pipelines well enough to tell me why my image variable binding in "Regression test" and "Upgrade test" doesn't clobber the value from the template? Or, even more oddly, why it seems to half-way clobber it, giving the right info print, but pulling the wrong image?
Sorry to bother the list, but I'm at my wits end and the debugging tools and documentation are somewhere between horrible and non-existent.
Thanks for any advice,
R
Robert P. Goldman Research Fellow Smart Information Flow Technologies (d/b/a SIFT, LLC)
319 N. First Ave., Suite 400 Minneapolis, MN 55401
Voice: (612) 326-3934 Email: rpgoldman@SIFT.net
-
Alexander Fedorov -
Faré -
Robert Goldman -
Robert Goldman