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
I've been debugging ominous 401 error when using gitlabCommitStatus in pipeline (despite the "test connection" being successful in the jenkins management page), which went away after upgrading jenkins version. It seems at some point gitlab plugin version got updated and it stopped working because the required jenkins version was greater than jenkins version being used. It would be nice if the plugin explicitly logged "your jenkins version is too old", since the 401 was rather misleading and made me think the issue is with access token configuration
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered:
What feature do you want to see added?
I've been debugging ominous 401 error when using
gitlabCommitStatus
in pipeline (despite the "test connection" being successful in the jenkins management page), which went away after upgrading jenkins version. It seems at some point gitlab plugin version got updated and it stopped working because the required jenkins version was greater than jenkins version being used. It would be nice if the plugin explicitly logged "your jenkins version is too old", since the 401 was rather misleading and made me think the issue is with access token configurationUpstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: