I recently upgraded my GitLab instance to a newer version and noticed a change in behavior when using the updateGitlabCommitStatus step in Jenkins pipelines. Prior to the upgrade,...
Config right gitlab token to jenkins and test success Config webhook on gitlab and triggered jenkins job build successfully However, the post-build actions "Publish build status to GitLab" failed. My gitlab version is 13.10 The jenkins log shows: Failed to update Gitlab commit status for proj...
[ Accept = [application/json], PRIVATE-TOKEN = [***FILTERED***] ] Apr 12, 2019 11:53:16 AM FINEST com.dabsquared.gitlabjenkins.gitlab.api.impl.ResteasyGitLabClientBuilder Got response from GitLab: URL: https://git.todo42.de/api/v4/user Status: 200 OK ... Apr 12, 2019 11:53:...
Also included are commits to allow Node.js 14 to continue to build and pass tests on our Jenkins CI, including adding Python 3.10 to the list of allowable Python versions for building. Commits [7923c61a62] - build: pin build-docs workflow to Node.js 14 (Richard Lau) #40939 [da...
我认为您在“option”块中遗漏了一个“gitlabBuilds”命令，该命令声明了您在构建中将要执行的步骤。
Gitlab v17.3.6 Security (2 changes): [Fixed HTML injection in Global Search bug](https://gitlab.com/gitlab-org/security/gitlab/-/commit/96159ab6cd9af8fc0ceadaf7568c8aaf079a8542) ([merge request](https://gitlab.com/gitlab-org/security/gitlab/-/merge_requests/4506)) ...
Issue Failed to update Gitlab commit status for project. HTTP 401 Unauthorized Context Gitlab plugin version: 1.4.2 Gitlab version: GitLab Enterprise Edition 8.11.5-ee b7548a4 Jenkins version: 2.25 Logs & Traces Started by GitLab push by...
Context Gitlab plugin version: 1.5.11 Gitlab version: 11.7.0-rc4-ee Jenkins version: 2.157 Job type: Pipeline, Freestyle, Matrix, etc. Logs & Traces Failed to update Gitlab commit status for project '/': HTTP 403 Forbidden Finished: SUCC...
@user318@nick.thomasI am facing the same issue with my Gitlab CE deployment after updating from 12.3.1 to 12.5. Now build automations from Jenkins that try topushto gitlab are failing with the same error below. I tried the database update workaround but unfortunately, it didn't work for...