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
Currently, the text provided after the Smee token in a request is appended to the path given in the -P/--path option. This is working fine for us so far to trigger a Git repository scan in Jenkins using GitLab webhooks. However, the Jenkins Git plugin is changing the rules as newer versions expect an access token to be passed in with the URL, as &token=theToken. This would require us to change ALL webhooks in ALL GitLab repositories that need to trigger a build in Jenkins when we update to a version of the Git plugin that requires the token and, of course, every time we change that token.
An easier way to handle this would be to simply add the token parameter to the URL forwarded to Jenkins by Smee, so here's the request:
Please add a new parameter to Smee client (maybe -s/--suffix) which allows to append additional text to the constructed URL.
The text was updated successfully, but these errors were encountered:
Currently, the text provided after the Smee token in a request is appended to the path given in the
-P/--path
option. This is working fine for us so far to trigger a Git repository scan in Jenkins using GitLab webhooks. However, the Jenkins Git plugin is changing the rules as newer versions expect an access token to be passed in with the URL, as&token=theToken
. This would require us to change ALL webhooks in ALL GitLab repositories that need to trigger a build in Jenkins when we update to a version of the Git plugin that requires the token and, of course, every time we change that token.An easier way to handle this would be to simply add the token parameter to the URL forwarded to Jenkins by Smee, so here's the request:
Please add a new parameter to Smee client (maybe
-s/--suffix
) which allows to append additional text to the constructed URL.The text was updated successfully, but these errors were encountered: