You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this great action. The only problem is that the action doesn't fail in case if anything doesn't work in the process of interacting with Gitlab. I'm running the action with the standard parameters written in Readme, including using the master version of the code:
When everything is configured correctly on Gitlab the action works great. But when something expires the action still pretends everything works with a success status. Here are logs from 2 of such cases:
A Gitlab access token expires:
Switched to a new branch 'my-branch'
Branch 'my-branch'set up to track remote branch 'my-branch' from 'origin'.
pushing to my-branch branch at <my gitlab repo>
remote: HTTP Basic: Access denied
fatal: Authentication failed for'<my gitlab repo>'
Triggered CI for branch my-branch
Working with pipeline id #null
Poll timeout set to 10
Current pipeline status: null
Pipeline finished with status null
Fetching all GitLab pipeline jobs involved
jq: error (at <stdin>:0): Cannot index string with string "id"
Posting output from all GitLab pipeline jobs
Debug problems by unfolding stages/jobs above
Push to Gitlab fails because the given access token doesn't have a permission to push to a protected branch:
Switched to a new branch 'master'
Branch 'master'set up to track remote branch 'master' from 'origin'.
pushing to master branch at <my gitlab repo>
warning: redirecting to <my gitlab repo>
remote: GitLab: You are not allowed to push code to protected branches on this project.
To <my gitlab repo>! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '<my gitlab repo>'
Triggered CI for branch master
Working with pipeline id #167976
Poll timeout set to 10
Current pipeline status: success
Pipeline finished with status success
Fetching all GitLab pipeline jobs involved
Posting output from all GitLab pipeline jobs
Stage test / Job my_integration_job
Debug problems by unfolding stages/jobs above
{
"message": "Resource not accessible by integration",
"documentation_url": "https://docs.github.com/rest/reference/repos#create-a-commit-status"
}
(Note: in the above logs I just masked the actual gitlab repo link as it is not important for debugging.)
Hi @SvanBoxel,
Thanks for this great action. The only problem is that the action doesn't fail in case if anything doesn't work in the process of interacting with Gitlab. I'm running the action with the standard parameters written in Readme, including using the
master
version of the code:When everything is configured correctly on Gitlab the action works great. But when something expires the action still pretends everything works with a success status. Here are logs from
2
of such cases:(Note: in the above logs I just masked the actual gitlab repo link as it is not important for debugging.)
This is probably very related to #10
The text was updated successfully, but these errors were encountered: