[JIRA] (JENKINS-50187) build-blocker-plugin does not block on node level for pipeline projects
Title: Message Title Denis Mone commented on JENKINS-50187 Re: build-blocker-plugin does not block on node level for pipeline projects I've managed to fix the issue at least locally, by adding an additional check for the ownerTask of the item, and returning the property afterwards. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189206.1521102438000.2098.1575640860855%40Atlassian.JIRA.
[JIRA] (JENKINS-50187) build-blocker-plugin does not block on node level for pipeline projects
Title: Message Title Denis Mone updated an issue Jenkins / JENKINS-50187 build-blocker-plugin does not block on node level for pipeline projects Change By: Denis Mone Attachment: check_ownerTask.patch Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189206.1521102438000.2100.1575640861051%40Atlassian.JIRA.
[JIRA] (JENKINS-50187) build-blocker-plugin does not block on node level for pipeline projects
Title: Message Title Denis Mone commented on JENKINS-50187 Re: build-blocker-plugin does not block on node level for pipeline projects We are facing the same issue in my company. I'd like to take this ticket and start working out a solution for the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189206.1521102438000.9419.1571296080142%40Atlassian.JIRA.
[JIRA] (JENKINS-50187) build-blocker-plugin does not block on node level for pipeline projects
Title: Message Title
Kent Granström updated an issue
Jenkins / JENKINS-50187
build-blocker-plugin does not block on node level for pipeline projects
Change By:
Kent Granström
Have integrated Jenkins with Atlassian Bitbucket where I trigger what we call "pre-merge" builds. This means once pull-requests are reday ready for merge we start a job that checks that they are really ready for merge. A failed build will prevent the merge. Any change on the target branch, or the source branch will trigger a new build. Since there are several pull requests that wants to merge to the develop branch many jobs can be triggered simultanously causing 2-3 or even more build jobs to be queued at once. We have 2 build slaves/agents that I have given the same label so they can be used simultanously to balance the load so to speak.Now then, in the job, I have entered a restriction for where this job can execute in the "Label _expression_": 'label-that-sits-on-two-slaves'.I have also entered a "Blocking jobs" -name like ABC* and then selecting the "block on node level" which leads me to believe that this would allow one of the "pre-merge" builds to use one of our agents and a second one to use the other slave and this seems to work for NON-PIPELINE jobs. Doing the same for a pipeline job, where specifying:{code:java}agent { label: 'label-that-sits-on-two-slaves' }{code}does not work. What is required to be able to automatically distribute a build-job on two or more agents simultanously and prevent them from running at the same time on the same agent using pipeline scripts?
Add Comment
[JIRA] (JENKINS-50187) build-blocker-plugin does not block on node level for pipeline projects
Title: Message Title
Kent Granström created an issue
Jenkins / JENKINS-50187
build-blocker-plugin does not block on node level for pipeline projects
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-blocker-plugin
Created:
2018-03-15 08:27
Environment:
Jenkins 2.111
Priority:
Critical
Reporter:
Kent Granström
Have integrated Jenkins with Atlassian Bitbucket where I trigger what we call "pre-merge" builds. This means once pull-requests are reday for merge we start a job that checks that they are really ready for merge. A failed build will prevent the merge. Any change on the target branch, or the source branch will trigger a new build. Since there are several pull requests that wants to merge to the develop branch many jobs can be triggered simultanously causing 2-3 or even more build jobs to be queued at once. We have 2 build slaves/agents that I have given the same label so they can be used simultanously to balance the load so to speak. Now then, in the job, I have entered a restriction for where this job can execute in the "Label _expression_": 'label-that-sits-on-two-slaves'. I have also entered a "Blocking jobs" -name like ABC* and then selecting the "block on node level" which leads me to believe that this would allow one of the "pre-merge" builds to use one of our agents and a second one to use the other slave and this seems to work for NON-PIPELINE jobs. Doing the same for a pipeline job, where specifying:
agent { label: 'label-that-sits-on-two-slaves' }
