Issue with Jenkins and GitLab Integration

75 views
Skip to first unread message

Erick Mormin

unread,
Apr 24, 2024, 9:31:13 AMApr 24
to Jenkins Users

Dear Jenkins Support, 

 

I am reaching out to you regarding difficulties I am encountering with integrating Jenkins and GitLab for my project. Below are the details of the problem I am facing: 

 

1. Problem Description: 

   While configuring the integration between Jenkins and GitLab, I followed the recommended steps to generate an SSH key in Jenkins, add it to my GitLab account, configure webhooks, and create credentials in Jenkins. However, despite these actions, I am facing errors when attempting to trigger builds from GitLab webhooks. 

 

2. Errors Encountered: 

   - When I try to trigger a build from a push on GitLab, I receive an HTTP 403 error with the message "No valid crumb was included in the request". 

   - Additionally, when Jenkins attempts to fetch changes from the GitLab repository, I receive a permission denied error with the message "Permission denied (publickey,password)". 

 

3. Actions Taken: 

   - I have verified that the SSH keys generated in Jenkins have been correctly added to my GitLab account. 

   - I have also verified that the credentials and webhook configurations in Jenkins are correct. 

 

4. Recommended Actions: 

   I am seeking your assistance in resolving this issue. Could you please: 

   - Verify if the configuration I have described is correct and if I have missed anything important? 

   - Provide guidance or recommendations for diagnosing and resolving the errors I am encountering? 

   - Suggest additional steps I could take to resolve this issue? 

 

5. Additional Information: 

   - Here are the details of my Jenkins and GitLab configuration: 

     - Jenkins Version: 2.440.3

     - GitLab Version: 16.10

     - Jenkins Configuration: please see the document in attachment

     - GitLab Configuration: please see the document in attachment

 

Thank you in advance for your help and assistance in resolving this problem. Please feel free to contact me if you need further information. 

 

Best regards, 


Erick MORMIN

Issue with Jenkins and GitLab Integration-EN.txt

Kris Stern

unread,
Apr 25, 2024, 5:54:23 AMApr 25
to Jenkins Users
Hi Erick,

I can try and reproduce your issue this weekend before getting back to you over the next few days. 

Best,
Kris

From: jenkins...@googlegroups.com <jenkins...@googlegroups.com> on behalf of Erick Mormin <erick....@gmail.com>
Sent: 24 April 2024 21:12
To: Jenkins Users <jenkins...@googlegroups.com>
Subject: Issue with Jenkins and GitLab Integration
 
--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a9b8bc67-ae1e-4e6c-a374-529f668b6b5cn%40googlegroups.com.

Dirk Heinrichs

unread,
Apr 25, 2024, 6:02:45 AMApr 25
to jenkins...@googlegroups.com
Am Mittwoch, dem 24.04.2024 um 06:12 -0700 schrieb Erick Mormin:

2. Errors Encountered: 

   - When I try to trigger a build from a push on GitLab, I receive an HTTP 403 error with the message "No valid crumb was included in the request". 


Does your Jenkins URL in the GitLab webhook conatin a valid Jenkins API token, like "http://your.jenkins/git/notifyCommit?token=<apt token>..."?

HTH...

Dirk
-- 
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
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.

Erick Mormin

unread,
Apr 25, 2024, 8:45:24 AMApr 25
to jenkins...@googlegroups.com

Hello Dirk,

Thank you for your follow-up. Here's a summary of the actions I've taken since our last discussion:

1. I added an authentication token to the GitLab webhook URL, as you suggested, using the following token: `43272f4e87b1eff15b230e6b8f8395d5`.

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`.

3. Unfortunately, during push event tests, I encountered a 403 error with the message "No valid crumb was included in the request".

4. I attempted to resolve this issue by adding a Jenkins-Crumb in the HTTP request header, but this did not solve the problem, and I continued to receive errors.

5. I also encountered an error when executing the webhook, with the message "Hook execution failed: Error while parsing rendered custom webhook template".

I'm now at a standstill and unsure of the next step to take. Do you have any suggestions on how to resolve these issues? If you need more information or screenshots to better understand the situation, please let me know.

Thank you in advance for your assistance.

Best regards,
Erick


--
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-use...@googlegroups.com.

Erick Mormin

unread,
Apr 25, 2024, 8:48:33 AMApr 25
to jenkins...@googlegroups.com
Hello Kris,

I wanted to update you on a question posed by Dirk Heinrichs. He asked whether the Jenkins URL in the GitLab webhook contains a valid Jenkins API token.

Here's the relevant information:

- GitLab webhook URL: http://192.168.0.24:8080/job/EasyFormerPipeline/build?token=43272f4e87b1eff15b230e6b8f8395d5

- Authentication token used: `43272f4e87b1eff15b230e6b8f8395d5`

- Jenkins-Crumb: `272d4a65b3a276b885c127c4444f871fedd00a73902eb0d5a27391dbc3b553c8`

Despite these efforts, I encountered errors during webhook execution, specifically: "Hook execution failed: Error while parsing rendered custom webhook template".

I'm currently seeking advice on how to resolve these issues. If you have any insights or suggestions, please let me know.

Thank you for your attention to this matter.

Best regards,
Erick


Dirk Heinrichs

unread,
Apr 25, 2024, 10:28:03 AMApr 25
to jenkins...@googlegroups.com
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`.

The URL is still wrong. What you want is to trigger a repository scan, as documented in the git plugin:

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.

Erick Mormin

unread,
Apr 25, 2024, 6:26:14 PMApr 25
to jenkins...@googlegroups.com
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 g...@192.168.0.24:Berechit/easyformer.git # timeout=10
Fetching upstream changes from g...@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 -- g...@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 g...@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


--
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-use...@googlegroups.com.

Dirk Heinrichs

unread,
Apr 26, 2024, 1:43:20 AMApr 26
to jenkins...@googlegroups.com
Am Freitag, dem 26.04.2024 um 00:25 +0200 schrieb Erick Mormin:

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>

Well, it has all the information you need: "Invalid access token". Make sure you provide a valid token (means: as created under "Manage Jenkins" -> "Security" -> "Git plugin notifyCommit access tokens").

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 g...@192.168.0.24:Berechit/easyformer.git # timeout=10
Fetching upstream changes from g...@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 -- g...@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 g...@192.168.0.24:Berechit/easyformer.git

Please check that cloning the repo works in general, by logging in to a shell on the Jenkins server, as the user that runs Jenkins, and executing a "git clone" command. If that works, it will usually also work from within Jenkins. Or, try to get it working with HTTP, first,

Additionally, I've updated the webhook URL in Jenkins as follows:

That's a type, I guess, and you mean ("in GitLab"), right?
I wrote that the repo URL (the part after "url=") must match exactly (means: letter by letter) the one used in the Jenkins Job. But you're using an HTTP URL here and an SSH URL in the job. That doesn't work.

Erick Mormin

unread,
Apr 26, 2024, 9:38:38 AMApr 26
to jenkins...@googlegroups.com
Hi Dirk,

I trust this email finds you well. I wanted to provide you with an update on our ongoing testing efforts and the challenges we're facing.

We've made progress in resolving the webhook issue in GitLab. The webhook is now successfully executed with an HTTP 200 response, indicating that it's functioning properly.

Here are the latest details of our webhook configuration in GitLab:



Manage Jenkins" -> "Security" -> "Git plugin notifyCommit access tokens
- URL: http://192.168.0.24:8080/manage/configureSecurity/
- Current access tokens: Nissan (Token: 75a8746bcf9c658b08491f27860f356d)

We are still encountering difficulties with fetching the Git repository in Jenkins. Despite our efforts, Jenkins prompts for a password when attempting to clone the repository, which is unexpected behavior for SSH authentication.

root@easyformer:~# docker ps
CONTAINER ID   IMAGE                     COMMAND                  CREATED      STATUS                  PORTS                                                                                                                         NAMES
016ce5d64dcb   jenkins/jenkins:lts       "/usr/bin/tini -- /u…"   8 days ago   Up 5 hours              0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 0.0.0.0:50000->50000/tcp, :::50000->50000/tcp                                      jenkins
b777b84a524b   gitlab/gitlab-ce:latest   "/assets/wrapper"        8 days ago   Up 25 hours (healthy)   0.0.0.0:40022->22/tcp, :::40022->22/tcp, 0.0.0.0:40080->80/tcp, :::40080->80/tcp, 0.0.0.0:40443->443/tcp, :::40443->443/tcp   gitlab
root@easyformer:~# docker exec -it jenkins bash
jenkins@192:/tmp$ git clone g...@192.168.0.24:Berechit/easyformer.git
Cloning into 'easyformer'...
g...@192.168.0.24's password:


Below are the latest logs from the Jenkins 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 g...@192.168.0.24:Berechit/easyformer.git # timeout=10
Fetching upstream changes from g...@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 -- g...@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 g...@192.168.0.24:Berechit/easyformer.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1241)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1305)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:101)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:88)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- g...@192.168.0.24:Berechit/easyformer.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout:
stderr: Permission denied, please try again.
Permission denied, please try again.
g...@192.168.0.24: Permission denied (publickey,password).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2846)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2185)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:635)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:997)
... 11 more

ERROR: Error fetching remote repo 'origin'
ERROR: Maximum checkout retry attempts reached, aborting.

We are actively working to resolve this issue and will keep you updated on our progress.

Thank you for your ongoing support and assistance.

Best regards,
Erick

--
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-use...@googlegroups.com.

Dirk Heinrichs

unread,
Apr 26, 2024, 9:54:19 AMApr 26
to jenkins...@googlegroups.com
Am Freitag, dem 26.04.2024 um 15:38 +0200 schrieb Erick Mormin:

We are still encountering difficulties with fetching the Git repository in Jenkins. Despite our efforts, Jenkins prompts for a password when attempting to clone the repository, which is unexpected behavior for SSH authentication.

That depends. If you're NOT using an SSH key, it will of course prompt for a password.

root@easyformer:~# docker ps
CONTAINER ID   IMAGE                     COMMAND                  CREATED      STATUS                  PORTS                                                                                                                         NAMES
016ce5d64dcb   jenkins/jenkins:lts       "/usr/bin/tini -- /u…"   8 days ago   Up 5 hours              0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 0.0.0.0:50000->50000/tcp, :::50000->50000/tcp                                      jenkins
b777b84a524b   gitlab/gitlab-ce:latest   "/assets/wrapper"        8 days ago   Up 25 hours (healthy)   0.0.0.0:40022->22/tcp, :::40022->22/tcp, 0.0.0.0:40080->80/tcp, :::40080->80/tcp, 0.0.0.0:40443->443/tcp, :::40443->443/tcp   gitlab
root@easyformer:~# docker exec -it jenkins bash
jenkins@192:/tmp$ git clone g...@192.168.0.24:Berechit/easyformer.git
Cloning into 'easyformer'...
g...@192.168.0.24's password:

OK, you're running this inside a Docker container, so I guess you need to get the private key you use for authenticating to your GitLab server into this container somehow.

OTOH, to get this working inside your job, you need to make sure that the credential record you select in the SCM section is an SSH credential, not a "username/password" one.

Bye...

Dirk Heinrichs

unread,
Apr 26, 2024, 9:59:11 AMApr 26
to jenkins...@googlegroups.com
Am Freitag, dem 26.04.2024 um 15:38 +0200 schrieb Erick Mormin:

Glad you got it working. However, this will still not trigger build in until the "?url=..." parameter matches exactly the repository URL in your job's SCM configuration. So you either need to use the SSH URL from the job configuration here, too, or change the job configuration to use the HTTP URL used here.

Bye...

Erick Mormin

unread,
Apr 27, 2024, 5:46:30 PMApr 27
to jenkins...@googlegroups.com
Subject: Issue with accessing GitLab repository from Jenkins

Dear Dirk,

I hope this email finds you well. I am reaching out to you because we are currently experiencing an issue with accessing a GitLab repository from our Jenkins instance, and I would like to request your assistance in resolving it.

Problem Description:
We have configured Jenkins to access a GitLab repository hosted at `192.168.0.24:Berechit/easyformer.git`, but we are encountering authentication errors when attempting to retrieve changes from this repository. Despite several checks, we have been unable to resolve the issue.

Verified Elements:
- Correct configuration of SSH keys in GitLab and Jenkins.
- Permissions on the GitLab repository have been checked and appear to be correct.
- SSH keys have been manually tested from the Jenkins container and appear to be functioning correctly.
- Jenkins logs indicate an authentication error when attempting to retrieve changes from the repository.
WARNING: Unknown parameter(s) found for class type 'jenkins.plugins.git.GitStep': credentials
The recommended git tool is: NONE
No credentials specified
 > 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 g...@192.168.0.24:Berechit/easyformer.git # timeout=10
Fetching upstream changes from g...@192.168.0.24:Berechit/easyformer.git
 > git --version # timeout=10
 > git --version # 'git version 2.39.2'
 > git fetch --tags --force --progress -- g...@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 g...@192.168.0.24:Berechit/easyformer.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:999)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1241)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1305)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:101)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:88)
	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- g...@192.168.0.24:Berechit/easyformer.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: Permission denied, please try again.
Permission denied, please try again.
Actions Taken:
- Restarted the Jenkins instance.
- Checked permissions and SSH configurations in GitLab and Jenkins.
- Manually tested SSH keys from the Jenkins container.

root@easyformer:~# ssh -T g...@192.168.0.24
g...@192.168.0.24's password:

root@easyformer:/tmp# git clone g...@192.168.0.24:Berechit/easyformer.git
Clonage dans 'easyformer'...
g...@192.168.0.24's password:

Request for Assistance:
We would like to request your expertise to help us resolve this issue. Do you have any additional suggestions on what we could check or avenues we could explore to resolve this situation?

Thank you in advance for your valuable assistance.

Best regards,
Erick MORMIN

--
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-use...@googlegroups.com.

Mark Waite

unread,
Apr 27, 2024, 6:54:48 PMApr 27
to Jenkins Users
On Saturday, April 27, 2024 at 3:46:30 PM UTC-6 erick....@gmail.com wrote:
Subject: Issue with accessing GitLab repository from Jenkins

Problem Description:
We have configured Jenkins to access a GitLab repository hosted at `192.168.0.24:Berechit/easyformer.git`, but we are encountering authentication errors when attempting to retrieve changes from this repository. Despite several checks, we have been unable to resolve the issue.

Verified Elements:
- Correct configuration of SSH keys in GitLab and Jenkins.
- Permissions on the GitLab repository have been checked and appear to be correct.
- SSH keys have been manually tested from the Jenkins container and appear to be functioning correctly.
- Jenkins logs indicate an authentication error when attempting to retrieve changes from the repository.
WARNING: Unknown parameter(s) found for class type 'jenkins.plugins.git.GitStep': credentials The recommended git tool is: NONE No credentials specified
That message likely means that your pipeline includes the step:

git credential: 'abc' url: 'your-git-repo-url'

The "credential" parameter is not a valid parameter for the "git" step.  Use the Pipeline syntax snippet generator to use the correct parameter name. The Git client plugin documentation page includes a 90 second video that shows how to use the generator

Erick Mormin

unread,
Apr 28, 2024, 4:16:57 AMApr 28
to jenkins...@googlegroups.com
Subject: Update on GitLab-Jenkins Integration Issue

Hi Mark and Dirk,

I hope this email finds you well. I wanted to give you an update on our ongoing efforts to resolve the GitLab-Jenkins integration issue.

We've made significant progress in addressing the webhook problem in GitLab. The webhook is now executing successfully with an HTTP 200 response, indicating that it's functioning as expected.

Here are the latest details regarding our webhook configuration in GitLab:
- SSL Verification: Unchecked
- Trigger: Push events

Manage Jenkins" -> "Security" -> "Git plugin notifyCommit access tokens
- URL: http://192.168.0.24:8080/manage/configureSecurity/
- Current access tokens: Nissan (Token: 75a8746bcf9c658b08491f27860f356d)

However, we are still encountering difficulties with fetching the Git repository in Jenkins. Despite our efforts, Jenkins prompts for a password when attempting to clone the repository, which is unexpected behavior for SSH authentication.

Here are the latest logs from the Jenkins build :
WARNING: Unknown parameter(s) found for class type 'jenkins.plugins.git.GitStep': credentials
The recommended git tool is: NONE
No credentials specified

We are actively working to resolve this issue and will keep you updated on our progress.

I will also send you the following documents for reference:

1. Issue Jenkins GitLab Integration-Project Documents tittle-28042024-EN
2. Issue Jenkins GitLab Integration-Groovy Pipeline-28042024-EN
3. Issue Jenkins GitLab Integration-Build Logs-28042024-EN
4. Issue Jenkins GitLab Integration-Installation Notes-28042024-EN

Thank you for your continued support and assistance.

Best regards,
Erick

Sans virus.www.avast.com

--
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-use...@googlegroups.com.
Issue Jenkins GitLab Integration-Project Documents tittle-28042024-EN.txt
Issue Jenkins GitLab Integration-Groovy Pipeline-28042024-EN.txt
Issue Jenkins GitLab Integration-Installation Notes-28042024-EN.txt
Issue Jenkins GitLab Integration-Build Logs-28042024-EN.txt
Reply all
Reply to author
Forward
0 new messages