The worst thing about Jenkins is that it works

Re:The worst thing about Jenkins is that it works by JeremyNT on Monday December 04, 2023 @08:32AM (#38516963)

This is definitely possible. We've been building an image in one phase and then running it in subsequent phases for years with gitlab.

I think you are going about this wrong. Are you generating an image tag dynamically? When you are tagging the image, make sure that you generate the tag deterministically based on information that is available to gitlab when the pipeline is created.

So for example, you could use the tag foo:$PIPELINE_ID instead of foo:$random

[ Parent | on HN ]

Re:The worst thing about Jenkins is that it works by codethief on Tuesday December 05, 2023 @01:20AM (#38527692)

My apologies, I misspoke: I wanted the image tag not to be $CI_COMMIT_SHA but to be a hash dynamically generated from certain files in the repo. The issue is that IMAGE won't accept a dynamically generated environment variable (passed from job to job via a dotenv artifact).

[ Parent | on HN ]

Re:The worst thing about Jenkins is that it works by nijave on Thursday December 07, 2023 @05:15PM (#38562570)

I think you could just jam anything you need in pipeline yaml from the dotenv file into outputs/variables then do something like this https://stackoverflow.com/a/71575683/2751619

[ Parent | on HN ]

Re:The worst thing about Jenkins is that it works by codethief on Friday December 08, 2023 @06:21AM (#38567697)

No, this doesn't work. Also note that the StackOverflow link is about Github Actions, not Gitlab CI.

[ Parent | on HN ]