Re: Issue with Jenkins and GitLab Integration

2024-04-25 Thread 'Dirk Heinrichs' via Jenkins Users
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

2024-04-25 Thread Erick Mormin
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

2024-04-25 Thread 'Dirk Heinrichs' via Jenkins Users
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

2024-04-25 Thread Erick Mormin
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=43272f4e87b1eff1

Re: Issue with Jenkins and GitLab Integration

2024-04-25 Thread Erick Mormin
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

2024-04-25 Thread 'Dirk Heinrichs' via Jenkins Users
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

2024-04-25 Thread Kris Stern
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 an

Regarding how to pass params in jenkinsfile while running the terrafrom plan

2024-04-25 Thread Ashok Reddy
Hi, I am trying to pass parameters in jenkinsfile while running the terraform plan. Can someone please help? parameters { stringParam(envName: 'work', defaultValue: 'gamma', choices:['gamma', 'epsilon', 'referecne'],description: 'Workspace/environment file to use for deployment')