GitLab Plugin Received Webhook Does not Scan

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

GitLab Plugin Received Webhook Does not Scan

Sverre Moe-2
GitLab Plugin API access no longer works:
It wirj
The Jenkins job is a Multibranch Pipeline.
The SCM is Git (not Git Project)

This has worked before.
Then we upgraded Jenkins LTS from 2.263 to 2.277
Along with many plugin updates.
Now it no longer works.
GitLab is able to send the notification, and Jenkins receive it, but does not run a scan.
I checked the Jenkins log, and it did receive the webhook, but nothing more was done

2021-03-22 18:11:52.669+0000 [id=67685] INFO    c.d.g.webhook.GitLabWebHook#getDynamic: WebHook called with url: /project/my-awesome-projct

Both these methods of adding Push notification have worked last week prior to the Jenkins upgrade.

GitLab > Group > Project > Settings > Integrations > Jenkins CI
Checked: Active
Trigger
Checked: Push
Jenkins URL: https://jenkins.company.com
Project name: my-awesome-project

Test settings > Connection succesful

GitLab > Group > Project > Settings > Webhook
URL: https://jenkins.company.com/project/my-awesome-project
Secret Token: *Empty*
Checked: Push events
Checked: Enable SSL verification

Test > Push events > Hook executed successfully: HTTP 200



Jenkins 2.277.1
  Git plugin 4.7.0
  GitLab Plugin 1.5.19
  Gitlab API Plugin 1.0.6
  GitLab Branch Source Plugin 1.5.4

GitLab Enterprise Edition 13.9.3

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5f0c3611-e355-41cb-930b-edc55617677cn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: GitLab Plugin Received Webhook Does not Scan

Sverre Moe-2
I even tried to uncheck the GitLab Configuration for authentication
`Enable authentication for '/project' end-point`

But alas, still not working.

mandag 22. mars 2021 kl. 19:17:12 UTC+1 skrev Sverre Moe:
GitLab Plugin API access no longer works:
It wirj
The Jenkins job is a Multibranch Pipeline.
The SCM is Git (not Git Project)

This has worked before.
Then we upgraded Jenkins LTS from 2.263 to 2.277
Along with many plugin updates.
Now it no longer works.
GitLab is able to send the notification, and Jenkins receive it, but does not run a scan.
I checked the Jenkins log, and it did receive the webhook, but nothing more was done

2021-03-22 18:11:52.669+0000 [id=67685] INFO    c.d.g.webhook.GitLabWebHook#getDynamic: WebHook called with url: /project/my-awesome-projct

Both these methods of adding Push notification have worked last week prior to the Jenkins upgrade.

GitLab > Group > Project > Settings > Integrations > Jenkins CI
Checked: Active
Trigger
Checked: Push
Project name: my-awesome-project

Test settings > Connection succesful

GitLab > Group > Project > Settings > Webhook
Secret Token: *Empty*
Checked: Push events
Checked: Enable SSL verification

Test > Push events > Hook executed successfully: HTTP 200



Jenkins 2.277.1
  Git plugin 4.7.0
  GitLab Plugin 1.5.19
  Gitlab API Plugin 1.0.6
  GitLab Branch Source Plugin 1.5.4

GitLab Enterprise Edition 13.9.3

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/65595efa-2fee-4fcd-bba6-eb0e08de01dcn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: GitLab Plugin Received Webhook Does not Scan

Sverre Moe-2
The old style we where using with Gitolite to notify Jenkins of git push seems to work still.
https://jenkins.company.com/git/notifyCommit?url=ssh://[hidden email]/group/my-awesome-project.git

A workaround at least until I can find out why the GitLab Plugin does not work.

mandag 22. mars 2021 kl. 19:30:56 UTC+1 skrev Sverre Moe:
I even tried to uncheck the GitLab Configuration for authentication
`Enable authentication for '/project' end-point`

But alas, still not working.

mandag 22. mars 2021 kl. 19:17:12 UTC+1 skrev Sverre Moe:
GitLab Plugin API access no longer works:
It wirj
The Jenkins job is a Multibranch Pipeline.
The SCM is Git (not Git Project)

This has worked before.
Then we upgraded Jenkins LTS from 2.263 to 2.277
Along with many plugin updates.
Now it no longer works.
GitLab is able to send the notification, and Jenkins receive it, but does not run a scan.
I checked the Jenkins log, and it did receive the webhook, but nothing more was done

2021-03-22 18:11:52.669+0000 [id=67685] INFO    c.d.g.webhook.GitLabWebHook#getDynamic: WebHook called with url: /project/my-awesome-projct

Both these methods of adding Push notification have worked last week prior to the Jenkins upgrade.

GitLab > Group > Project > Settings > Integrations > Jenkins CI
Checked: Active
Trigger
Checked: Push
Project name: my-awesome-project

Test settings > Connection succesful

GitLab > Group > Project > Settings > Webhook
Secret Token: *Empty*
Checked: Push events
Checked: Enable SSL verification

Test > Push events > Hook executed successfully: HTTP 200



Jenkins 2.277.1
  Git plugin 4.7.0
  GitLab Plugin 1.5.19
  Gitlab API Plugin 1.0.6
  GitLab Branch Source Plugin 1.5.4

GitLab Enterprise Edition 13.9.3

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/49857a5a-5aed-4cd2-ab39-bb89e21e891dn%40googlegroups.com.