Re: Issue with Jenkins and GitLab Integration

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

Re: Issue with Jenkins and GitLab Integration

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 authe

Re: Issue with Jenkins and GitLab Integration

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

Re: Issue with Jenkins and GitLab Integration

Am Freitag, dem 26.04.2024 um 15:38 +0200 schrieb Erick Mormin: Jenkins Integration - URL: http://192.168.0.24:8080/git/notifyCommit?url=http://192.168.0.24:40080/Berechit/easyformer.git&token=75a8746bcf9c658b08491f27860f356d

Re: Issue with Jenkins and GitLab Integration

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

Re: Issue with Jenkins and GitLab Integration

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

Re: Issue with Jenkins and GitLab Integration

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 Error 403 Invalid access token HTTP ERR

Re: Issue with Jenkins and GitLab Integration

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 encou

Re: Issue with Jenkins and GitLab Integration

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`

Re: Issue with Jenkins and GitLab Integration

21:12 > *To:* Jenkins Users > *Subject:* Issue with Jenkins and GitLab Integration > > > 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

Re: Issue with Jenkins and GitLab Integration

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 GitL

Re: Issue with Jenkins and GitLab Integration

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 val

Re: Issue with Jenkins and GitLab Integration

Hi Erick, I can try and reproduce your issue this weekend before getting back to you over the next few days. Best, Kris From: jenkinsci-users@googlegroups.com on behalf of Erick Mormin Sent: 24 April 2024 21:12 To: Jenkins Users Subject: Issue with Jenkins

Issue with Jenkins and GitLab Integration

7-ae1e-4e6c-a374-529f668b6b5cn%40googlegroups.com. Issue with Jenkins and GitLab Integration I have performed the following configuration: root@easyformer:~# docker exec -it jenkins bash jenkins@192:/$ ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/var/jenkins_home/.