-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins v2.14
Gitlab v8.5
Gilab-plugin v1.3.0
git-client-plugin v1.19.7
git-plugin 2.5.2
I'm working on Gitlab SE & Jenkins integration.
When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins.
In jenkins the job execution is scheduled twice.
The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... "
The second one fails but it is probably started by git-plugin as it states:
"Started by an SCM change..."
It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin.
"Poll SCM" trigger is disabled in my job configuration.
In Jenkins log I see there is only one push notification from Gitlab which is correct.
I am expecting one push -> one build.
[JENKINS-36882] Gitlab integration - Double job execution
Facu Mateo
created issue -
Facu Mateo
made changes -
| Description |
Original:
I working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "${gitlabSourceBranch}" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build. |
New:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "${gitlabSourceBranch}" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build. |
Facu Mateo
made changes -
| Description |
Original:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "${gitlabSourceBranch}" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build. |
New:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "${gitlabSourceBranch}" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build. |
Facu Mateo
made changes -
| Description |
Original:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "${gitlabSourceBranch}" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build. |
New:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build. |
Facu Mateo
made changes -
| Description |
Original:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push one build. |
New:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push -> one build. |
| Assignee | Original: Mark Waite [ markewaite ] |
Facu Mateo
made changes -
| Description |
Original:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. I am expecting one push -> one build. |
New:
I'm working on Gitlab SE & Jenkins integration. When I push a commit to my git repository, a new push notification is sent from Gitlab to Jenkins. In jenkins the job execution is scheduled twice. The first one is correct and seems to be the result of Gitlab push notificación as it states "Started by GitLab push by... " The second one fails but it is probably started by git-plugin as it states: "Started by an SCM change..." It fails because the variable "gitlabSourceBranch" is not set. This shows me that this build wasn't started by the gitlab plugin. "Poll SCM" trigger is disabled in my job configuration. In Jenkins log I see there is only one push notification from Gitlab which is correct. I am expecting one push -> one build. |
Facu Mateo
added a comment - Yes, I know about some bugs in git-plugin that have the same effect and could be related. I will upload my job definition soon
Facu Mateo
added a comment - Yes, I know about some bugs in git-plugin that have the same effect and could be related. I will upload my job definition soon Facu Mateo
made changes -
| Attachment | New: config.xml [ 33414 ] |
You'll need to provide your job definition to confirm that you truly are not polling for SCM changes. The message seems to indicate that something is causing a poll for SCM changes, and that poll detects a change.