[JIRA] (JENKINS-35310) ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it

[jostein.gogs...@gmail.com (JIRA)]

Title: Message Title

Jostein Gogstad commented on JENKINS-35310   Re: ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it Authentication tokens doesn't work, as Jesse pointed out. The following endpoints works for triggering indexing and builds in multibranch projects: curl -isk -u gitlab:5d7b834xxxxxxxxxxxxxxx6c1e0c9f3 -X POST https://myjenkins.internal.com/job/my_multibranch_job/job/Branches/build HTTP/1.1 302 Found ... It gives 302, but it both indexes and trigger builds on branches with new commits. Since the authentication token doesn't work, you'll have to use an user level authentication token and use it as password in a BASIC authentication scheme, you'll find the user authentication token under https://myjenkins.internal.com/user/USERNAME/configure (press "Show token"). If your SCM-vendor doesn't support explicitly specifying BASIC credentials (gitlab has no configuration for this), you can embed it in the url. Our push hook in GitLab is https://gitlab:5d7b834xxxxxxxxxxxxxxx6c1e0c...@myjenkins.internal.com/job/my_multibranch_job/job/Branches/build Finally if you want to trigger build on specific branches in a multibranch pipeline, they can be triggered as such curl -isk -u gitlab:5d7b834xxxxxxxxxxxxxxx6c1e0c9f3 -X POST https://myjenkins.internal.com/job/my_multibranch_job/job/Branches/job/develop/build HTTP/1.1 201 Created Hope that helps Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.