Paul "TBBle" Hampson

Per [JENKINS-45514: Allow the ability to grant rights to the "Scan Multibranch Pipeline Now" link](https://issues.jenkins.io/browse/JENKINS-45514), that's already possible by giving users the `Job/Build` permission.

Ah, sorry, I misunderstood.

Looks like https://issues.jenkins.io/browse/JENKINS-64529 is the same problem.

It seems this was a known, deliberate change per https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/91#issuecomment-633235942. But the [1.5.2 release notes](https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.5.2) marked it as a fix, rather than a breaking-change new feature. It appears that the...

I'm not sure what #107 has to do with this? #107 is talking about per-user API tokens so that this plugin can take actions as a user (or users) on...

Yes, resaving each of your jobs should do it. The secret token we're talking about in this ticket is _not_ the Personal Access Token on this screen though. This issue...

@kuhnroyal I'd raise that as another bug report, so it's clearly visible _as_ a bug report. However, it's possible this was fixed by #105, which was _after_ the 1.5.3 release....

The "Secret Token" box in the config should _not_ be a Personal Access Token for a GitLab user. It should be a nice long random string, because it's the token...

For the error with invalid secret token, I expect that after changing the secret token in the config, you need to go through every Jenkins job using this plugin and...

I've just noticed, the log is coming from `GitLabSystemHookAction.java`, not `GitLabWebHookAction.java`. So it's the hook added to the GitLab system webhooks for detecting job deletion, not the hook attached to...