[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Alexander Borsuk commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor This is a critical issue that makes parallel/matrix builds unusable. In my pipeline I need to build for Mac and Linux. Obviously, it can be done in parallel. There are two build nodes available (Linux and Mac). The bug reproduces when one build node waits until another build node finishes. And another one waits until the first one finishes. This is a deadlock. 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.142612.1325650778000.556.1579190041047%40Atlassian.JIRA.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Alexander Borsuk updated an issue Jenkins / JENKINS-12290 Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor Change By: Alexander Borsuk Issue Type: Improvement Bug Priority: Major Critical 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.142612.1325650778000.516.1579189804988%40Atlassian.JIRA.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Tobias Gierke commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I just hit this bug, IMHO this is a core feature (being able to trigger another project and wait for it's completion without blocking an executor). 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.142612.1325650778000.279.1573718462828%40Atlassian.JIRA.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Tamas Hegedus commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I have a single jenkins server with two executors. I cannot run two pipelines in parallel because it immediately gets deadlocked as it cannot start the child jobs. I wonder why doesn't this issue have critical priority. It renders pipeline jobs useless in most cases. JENKINS-26959 was set critical and was closed as a duplicate of this issue. 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.142612.1325650778000.9246.1572957900866%40Atlassian.JIRA.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title
Petar Tahchiev edited a comment on JENKINS-12290
Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
I've just hit this issue :( My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order \ {{bom}}-> \ {{platform}}->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title
Petar Tahchiev edited a comment on JENKINS-12290
Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
I've just hit this issue :( My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order {{ bom }} -> {{ platform }} ->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title
Petar Tahchiev edited a comment on JENKINS-12290
Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
I've just hit this issue :( My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order \{{ bom }} -> \{{ platform }} ->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Petar Tahchiev commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I've just hit this issue My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order bom->platform->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Tiger Cheng commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor Also following and in agreement with Vasily that it is expected that if the childjob is asking for a node that is run by the parent node, that it should be allowed access to the node. Without this expectation working, our complex pipeline is unable to properly archive artifacts in the ideal clean manner it was designed for. The alternative is to seek for a solution to archive from nodes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Vasily L edited a comment on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I think the waiting parent job should share its executor for the children.Alternatively, it can just release the executor while blocked and pick the executor it up on unblock. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Vasily L commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I think the waiting parent job should share its executor for the children. Alternatively, it can just release the executor while blocked and pick the executor up on unblock. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Michal Wesolowski commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I'm also looking forward to see this resolved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Heiko Böttger commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor Hi is any one working on that? For me this problem make the parameterized jobs plugin unusable. I cannot risk that jenkins suddenly get stuck and block all builds. My scenario is as following: I have a buildscript which needs to be executed (on specific slave) to create a property files for each dependency I need to build. I use the parameterized job plugin to run a job for each dependency and wait until its finished. Here the problem starts as soon as I need to block until the end, the executed used by the main job is never releases. This issue can be easily reproduced using a slave with exactly one executor. Now I thought the Matrix Job used as upstream job type would solve the issue since it is executed as a flyweight job, however I need to execute the script for creating the dependencies on a specific slave which forces me to define a slave axis. The slave axis again is exeuted as a subtask which is not flyweight causing the same issues. One solution which will work is releasing the executor before blocking and acquire it again when the subtask is done. My current idea to workaround that is avoiding the need for a axis in the matrixjob and using a separate downstream job to create the property files which I will transfer to the matrxijob by using the copy artifacts plugin. That's rather complicated and I am still not sure whether that will work. Any better idea? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Roland Schulz edited a comment on JENKINS-12290 Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I think it is important. I have a multi-configuration project for both the build and the test step. Each have more configurations then I have executors/cores. Thus the job will always hang because no executors are available when it tries to trigger the test. Ideally the triggering job (in the example the "build" job) would not use any executor while it is waiting. Similar to how the multi-configuration master doesn't use an executor (fixed in 936). This would let me use the block feature as a work-around for 11409. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Roland Schulz commented on JENKINS-12290 Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I think it is important. I have a multi-configuration project for both the build and the test step. Each have more configurations then I have executors/cores. Thus the job will always hang because no executors are available when it tries to trigger the test. Ideally the triggering job (in the example the "build" job) would not use any executor while it is waiting. Similar to how the multi-configuration master doesn't use an executor (fixed in 936). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
cjo9900 commented on JENKINS-12290 Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor The case that you mention here is one of many possible cases I can think of the following Case A Parent (trigger+block) -> child(label=qwerty) A1: No nodes online that have label==qwerty A2: No nodes that have label defined. Case B Parent(label=qwerty)(trigger+block) -> child(label=qwerty) B1: Label qwerty has only one executor which is in use by parent Case C Parent(trigger+block) -> child C1: Master only has 1 executor This covers the simple cases, however if the parent is a Matrix project, we end up with an even more difficult probelm to solve. Case D Parent(x*y configurations) -> x*y matrix builds -> x*y child builds D1: Less than or equal x*y executors - Child builds cannot run So to be able to resolve this within the plugin at either configuration or runtime is very difficult. as we cannot just check if master has a single executor as other factors come into play, regarding Cloud services and job properties(label, resource, etc) that the child projects require. Problems: Configuration time. Can only check current situation of child projects + Nodes. Project list might be a parameter, so cannot determine the project list. Passing a label parameter to child project might affect checking. Cannot account for any cases where Cloud can allocate nodes. Runtime Cannot always garrenttee that a Node could be created for a Cloud instance Cannot control busy Executors that used by other projects, needed by started build. Implementation Ideas Get Node that we are being built on (own node) (or list of nodes containing all matrix siblings see below) get Projects to start get All Nodes get All Clouds foreach project + parameter set #check 1 can it be started on master with parameters? Yes does master == ownNode ( if master.numExecutors > 1 — Can run on master. ) else ( if master.numExecutors > 0 — Can run on master. ) No // cannot start on master try other Nodes forEach Node can it be started on node with parameters? Yes does node == ownNode ( if node.numExecutors > 1 — Can run on node. ) else ( if node.numExecutors > 0 — Can run on node. ) No // cannot start on master or existing Nodes try Cloud services forEach Cloud can Cloud start a required node Yes — Can create a node to run on No — No possible way that we can continue as we will block. This should handle most cases, if it can be implemented, however it assumes that any other builds that are ongoing on any executor will be able to finish and allow a proposed job to start. This may fail if the parent build is a Matrix build as this behaviour would not take into account the jobs siblings which also have similar blocking behaviour. This could be resolved by get current build get root build if these are the same there is no issue if are different and root build is a matrix we need to find out where all of child jobs are running/going to run on. Overall this could be done but is there a need for this? I feel that it would be better to just add a warning when enabling the "Block until the triggered projects finish their builds" item that informs the user that this might occur. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
