Describe your question in as much detail as possible:
I have a very normal setup which is to activate my BUILD stage whenever there is a git tag. During my initial development, I tested with the git tag on the UI, it all went well until I started testing it with the “git tag” on the command line on a remote git repo. Whenever this tags are pushed to the gitlab repo, the pipeline will be triggered and 100% fails to run at very early stage when the section where “Featching changes…” happens. it will fail to access the repository with the given token( gitlab-ci-token… )
- What are you seeing, and how does that differ from what you expect to see?
I have not done this before but I expect it to work just like the UI will.
Consider including screenshots, error messages, and/or other helpful visuals
What version are you on? Are you using self-managed or GitLab.com?
- GitLab (Hint:
- GitLab (Hint:
- What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
I have tried to make sure a baseline test is done with the UI and all access are given proper check on the gitlab-runner agent and to the server. Everytime the git tag on UI tested = works ! 3 out of 3 =SUCCESS. but I git clone a repo to a separate machine, run git tag -a 3.1.2 -m “bla bla 3.1.2” , the pipeline will fail for sure ( as shown on the screenshot )
I have also changed the CI/CD to do git clone instead of git fetch on all new pipeline , but still fails
Thanks for taking the time to be thorough in your request, it really helps!