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
the pipeline just passes along as if nothing happened
[Pipeline] stage
[Pipeline] { (notify SourceHub about pipeline start)
[Pipeline] updateGitlabCommitStatus ([hide](http://jenkins/job/nsi/job/ansible-inventories/job/master/3113/console#))
Failed to update GitLab commit status for project '/ansible-inventories': HTTP 403 Forbidden
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Clean workspace on the master branch)
[Pipeline] cleanWs
Anything else?
The reason for 403 is because the user we are using got blocked today by mistake and even if we use tokens the auth part does not work. So we know why, we just want the pipeline to fail if there was an error updating gitlab in any way
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered:
screwyy
added
the
bug
For changelog: Minor bug. Will be listed after features
label
Jan 18, 2024
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Docker official LTS image
Reproduction steps
use updateGitlabCommitStatus as a step and if you receive 403 the pipeline does not fail, it acts as if all is good
Expected Results
step/stage failed
Actual Results
the pipeline just passes along as if nothing happened
Anything else?
The reason for 403 is because the user we are using got blocked today by mistake and even if we use tokens the auth part does not work. So we know why, we just want the pipeline to fail if there was an error updating gitlab in any way
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: