This is a weird one. I run into it a few times now (repeatable).
Short version
I commit a new file, The CI job runs and produces artifacts, I got to the CI pipeline page in my Gitlab account, click the “Downloads artifacts button” and it downloads the previous pipelines artifacts instead of the expected new artifacts.
I am using the hosted version on gitlab.com I believe the version is
GitLab Enterprise Edition 15.3.0-pre 91fada02300
Steps to reproduce.
- Goto DI/DC => Pipeline page
- Download the latest Pipeline archives using the download artifacts button.
- I check the archives and see it is version AA (Good)
- Push a new commit to the git repo (Version BB), this will cause a new pipeline job and will produce new artifacts
- On the “Pipeline page” a new pipeline job will show up, and show as “passed”. The commit message will match the message (Version BB) I put in Step 4.
- Download the latest Pipeline archives using the download artifacts button.
- I check the archives and see it is version AA (BAD), When I was expecting version BB
See this image.
If I click the download button next to the BB pipeline it will download the artifacts for AA
Strange!!
I can reproduce this problem.
As a workaround, I click into the latest pipeline and then the job that produces the artifacts, and download the artifacts from the job page directly. This seems to work without issue.
What troubleshooting steps have you already taken?
- I have clicked “clear runners caches”
- I have checked with Chrome, and Microsoft Edge
- I have added logging messages to output the version number in the CI logs. Always shows the correct version
How do I resolve this issue?