Gitlab CI automatic release
See original GitHub issueThe problem
I’m trying to set up gitlab ci to work with pythonn-semantic-release but when the code tries to push, I’m getting 403 Forbidden.
Expected behavior
python-semantic-release would realise it’s on gitlab ci and obtain the CI_JOB_TOKEN.
Additional context
Could it be connected to this: https://docs.gitlab.com/ee/user/project/new_ci_build_permissions_model.html
Are there any examples out there of .gitlab-ci.yml
for this use case?
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
How GitLab is automating release generation in .gitlab-ci.yml
Release Management, a group within the Release stage, is about unblocking users as they continuously deliver value to their customers. A part of ......
Read more >GitLab: Automatic releases with CI/CD Pipelines
After that, every time the scheduler is executed, a Tag will be created from the Master-Branch. This Tag will then be released automatically....
Read more >How To Automate Release Notes in GitLab - Medium
It is easy to find all the commits from the new release. $PREV_HASH is the last commit of the previous release.
Read more >Introduction - Release automation - Gitlab CI
go-semrel-gitlab is a set of commands you can use to compose your automated release workflow. ... Other features include. ... This project was...
Read more >Automate tagging and creating releases with GitLab CI
The basic workflow is straight forward. You commit a change to your default branch, it runs the pipeline defined in your .gitlab-ci.yml file...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
IIRC, pushing code with this
CI_JOB_TOKEN
is not possible and a personal access token is required for that.@nraw I’ve just been through the same thing, you need to create a personal access token and use that to set a CI/CD variable called GL_TOKEN.