Fetching from https://gitlab-ci-token:{$CI_JOB_TOKEN}@gitlab.com/.../repo/-/raw/... over HTTPS using gitlab-ci-token stopped working
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
For the last few months, I've had a pipeline script that downloads a file from a different repo kind of like this: curl https://gitlab-ci-token:{$CI_JOB_TOKEN}@gitlab.com/.../repo/-/raw/.... As of two or three days ago, it stopped working, and I instead get redirected to my company's SSO login page. git clone https://gitlab-ci-token:{$CI_JOB_TOKEN}@gitlab.com/.../repo.git does still work.
As far as we can tell, no settings changed on our end. I suspect what I was doing was never supported and worked on accident, and some recent change broke my workflow. Can somebody confirm that? I know that CI_JOB_TOKEN doesn't have files API access, so I was happy to have had this workaround until recently. If basic auth with gitlab-ci-token:{$CI_JOB_TOKEN} is meant to only work with the git smart http protocol, is there an efficient way with the git protocol to fetch the contents of just one file, or do I need to clone the whole thing?