Dear Dirk, I hope this email finds you well. I wanted to update you on the ongoing issues I've been facing with the GitLab webhook configuration and triggering builds in Jenkins.
Unfortunately, I'm still encountering problems despite several attempts to resolve them. Here are the errors I'm encountering: In GitLab: Hook executed successfully but returned HTTP 403 <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 403 Invalid access token</title> </head> <body><h2>HTTP ERROR 403 Invalid access token</h2> <table> <tr><th>URI:</th><td>/git/notifyCommit</td></tr> <tr><th>STATUS:</th><td>403</td></tr> <tr><th>MESSAGE:</th><td>Invalid access token</td></tr> <tr><th>SERVLET:</th><td>Stapler</td></tr> </table> <hr/><a href="https://eclipse.org/jetty";>Powered by Jetty:// 10.0.20</a><hr/> </body> </html> In Jenkins, when triggering a build: The recommended git tool is: NONE using credential jenkinsgitlabssh > git rev-parse --resolve-git-dir /var/jenkins_home/workspace/EasyFormerPipeline/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url git@192.168.0.24:Berechit/easyformer.git # timeout=10 Fetching upstream changes from git@192.168.0.24:Berechit/easyformer.git > git --version # timeout=10 > git --version # 'git version 2.39.2' using GIT_SSH to set credentials Test EasyFormer23042024 Verifying host key using known hosts file, will automatically accept unseen keys > git fetch --tags --force --progress -- git@192.168.0.24:Berechit/easyformer.git +refs/heads/*:refs/remotes/origin/* # timeout=10 ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from git@192.168.0.24: Berechit/easyformer.git Additionally, I've updated the webhook URL in Jenkins as follows: http://192.168.0.24:8080/git/notifyCommit?url=http://192.168.0.24:40080/Berechit/easyformer.git&token=11b263dbb6e2a1f398bee5f391e98041a5 Despite these efforts, the issue persists. Do you have any further suggestions on how to troubleshoot and resolve these problems? Thank you for your assistance. Best regards, Erick Le jeu. 25 avr. 2024 à 16:27, 'Dirk Heinrichs' via Jenkins Users < jenkinsci-users@googlegroups.com> a écrit : > Am Donnerstag, dem 25.04.2024 um 14:44 +0200 schrieb Erick Mormin: > > 2. I also updated the webhook URL in GitLab to include this token, as > follows: ` > http://192.168.0.24:8080/job/EasyFormerPipeline/build?token=43272f4e87b1eff15b230e6b8f8395d5` > <https://urldefense.com/v3/__http://192.168.0.24:8080/job/EasyFormerPipeline/build?token=43272f4e87b1eff15b230e6b8f8395d5*60__;JQ!!Obbck6kTJA!YKnlNKE-rU9EEdXIaSTjE4uLDgnBlNewY2GQ08uq_NM2UiB4B8ux0pX0WPK0qxIv0RzRGsS4tj0K48muBnm3D5Q$> > . > > > The URL is still wrong. What you want is to trigger a repository scan, as > documented in the git plugin <https://plugins.jenkins.io/git/>: > > http://yourserver/git/notifyCommit?url=<URL of the Git > repository>&token=<Access token> > > where "URL of the Git repsoitory" must exactly match the one used in your > Jenkins job, which can be either SSH or HTTPS. > > This will make ALL jobs that use that same Git repository URL to check the > repository for updates and start builds accordingly. > > HTH... > > Dirk > > -- > > *Dirk Heinrichs* > Senior Systems Engineer, Delivery Pipeline > OpenText ™ Discovery | Recommind > *Phone*: +49 2226 15966 18 > *Email*: dhein...@opentext.com > *Website*: www.recommind.de > Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach > Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, > Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail sind nicht gestattet. > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/9aca319ddfc9ac046b556c7bbac61842797ed23c.camel%40opentext.com > <https://groups.google.com/d/msgid/jenkinsci-users/9aca319ddfc9ac046b556c7bbac61842797ed23c.camel%40opentext.com?utm_medium=email&utm_source=footer> > . > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPrX6vBHpKaCzKXo9AY30q_z8jD4AjoAGhD1y4MeH31SSQ8k_Q%40mail.gmail.com.
