Open bolrock opened 6 months ago
I also tried removing the GITLAB_TOKEN from the project variable and adding
before_script: - export GITLAB_TOKEN="$CI_JOB_TOKEN" - export GITLAB_URL="$CI_SERVER_URL"
unfortunately, the CI_JOB_TOKEN
does not provide the ability to push code. see https://github.com/semantic-release/semantic-release/issues/1729 for more discussion about that situation
Without the @semantic-release/git module it is working fine. The tag is created and pushed to the master branch. But it seems the module cannot push the assets to the master branch.
you need to verify the permissions you've granted to your token. you need to use a token that provides the appropriate level of access. it appears that the one you are using does not provide the ability to push code to a protected branch
I have a protected master branch on my gitlab project
I'm using that Docker image
and I'm using that config
Without the @semantic-release/git module it is working fine. The tag is created and pushed to the master branch. But it seems the module cannot push the assets to the master branch.
Adding a printenv in the script I can see my GITLAB_TOKEN variable with my token.
But I don't understand if it's really possible to push to master with a personal access token ? I also tried removing the GITLAB_TOKEN from the project variable and adding
Now the printenv still show me the variable
But it is still not working (with another reason).
I don't want to unprotect my master branch. So what's the solution ?