-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Hudson ver. 1.393, matrix project, matrixtieparent plugin, post-build-batch-task plugin
I have a matrix project that completely builds on a slave node ("Build on multiple nodes", "Tie parent build to a node" vie matrixtieparent plugin). As a "Post-build Action", "Invoke batch tasks" is configured to run a batch task of the same project. Usually, this works fine and the batch task is execured after the matrix configurations are build. However, when the salve node becomes idle, the bach task is still in the build queue and stays there forever with "pending - Waiting for next available executor on MySlaveNode").
When a new job is added to the build queue, the pending job is finally executed.
This usually happen when may builds are in the queue. However, we also see it when hudson is idle and we start one project build manually.
- is related to
-
-
- Open
-
[JENKINS-7033] Job in build queue is not executed
Axel Heider
created issue -
Axel Heider
added a comment - Unfortunately, we have not found a way to repoduce this every time. However, there is a high change that this happen when I start a jon manually with master and slave idle.
Configuration:
Master: Windows, 4 executors
Slave: Linux, 2 executors, launched via SSH, "use exclusive for tied jobs, keep slave online as much as possible.
Axel Heider
added a comment - Unfortunately, we have not found a way to repoduce this every time. However, there is a high change that this happen when I start a jon manually with master and slave idle.
Configuration:
Master: Windows, 4 executors
Slave: Linux, 2 executors, launched via SSH, "use exclusive for tied jobs, keep slave online as much as possible. Axel Heider
added a comment - I wonder that I'm the only one seeing this happen - and it appears do be reproducible every time by now.
Axel Heider
added a comment - I wonder that I'm the only one seeing this happen - and it appears do be reproducible every time by now. 
torbent
made changes -
| Link | New: This issue is related to JENKINS-7667 [ JENKINS-7667 ] |
Now I have found a way to reproduce this always:
- Configuratuon: Windows Master, Linux Salve
- Matrix Job triggered by SVN commit runs fully on Linux Slave (also the parent vie matrix-tie-parent plugin)
- Job has one Batch task configured
- this batch Task is triggered as post build action (via "Invoke batch tasks")
When I start the build job manually, all matrix builds run and the batch task is put in the queue. But then the batch task does not run, it stays in thew queue. And it stays in the queue until another job arrives in the queue.
So, is it a problem with the post-build-Invoke-batch-task-plugin and the way it adds a job? It appears the problem always occurs for job on slaves, it occurs rarely for jobs on the master node.
Axel Heider
added a comment - - edited Now I have found a way to reproduce this always:
Configuratuon: Windows Master, Linux Salve
Matrix Job triggered by SVN commit runs fully on Linux Slave (also the parent vie matrix-tie-parent plugin)
Job has one Batch task configured
this batch Task is triggered as post build action (via "Invoke batch tasks")
When I start the build job manually, all matrix builds run and the batch task is put in the queue. But then the batch task does not run, it stays in thew queue. And it stays in the queue until another job arrives in the queue.
So, is it a problem with the post-build-Invoke-batch-task-plugin and the way it adds a job? It appears the problem always occurs for job on slaves, it occurs rarely for jobs on the master node.
Axel Heider
made changes -
| Description |
Original:
I have a matrix project that completely builds on a slave node ("Build on multiple nodes", "Tie parent build to a node" vie matrixtieparent plugin). As a "Post-build Action", "Invoke batch tasks" is configured to run a batch task of the same project. Usually, this works fine and the batch task is execured after the matrix configurations are build. However, when the salve node becomed idle, the bach task is still in the build queue anf stays there forever with "pending - Waiting for next available executor on MySlaveNode"). When a new job is added to the build queue, the pending job is finally executed. This usually happen when may builds are in the queue. However, we also see it when hudson is idle and we start one project build manually. |
New:
I have a matrix project that completely builds on a slave node ("Build on multiple nodes", "Tie parent build to a node" vie matrixtieparent plugin). As a "Post-build Action", "Invoke batch tasks" is configured to run a batch task of the same project. Usually, this works fine and the batch task is execured after the matrix configurations are build. However, when the salve node becomes idle, the bach task is still in the build queue and stays there forever with "pending - Waiting for next available executor on MySlaveNode"). When a new job is added to the build queue, the pending job is finally executed. This usually happen when may builds are in the queue. However, we also see it when hudson is idle and we start one project build manually. |
| Environment | Original: Hudson ver. 1.367, matrix project, matrixtieparent pluging | New: Hudson ver. 1.393, matrix project, matrixtieparent plugin, post-build-batch-task plugin |
Axel Heider
added a comment - Problem seen with Hudson 1.393 and 1.394 in Windows Master today. A matrix project building on the windows mater is configured to run 3 batch jobs after building. All three job remain in the build queue without getting executed.
Work around is now that an empty dummy project is build every 10 minutes so the build queue gets flushed.
Axel Heider
added a comment - Problem seen with Hudson 1.393 and 1.394 in Windows Master today. A matrix project building on the windows mater is configured to run 3 batch jobs after building. All three job remain in the build queue without getting executed.
Work around is now that an empty dummy project is build every 10 minutes so the build queue gets flushed. Axel Heider
added a comment - Problem still exists in 1.396 Axel Heider
added a comment - Todays I've seen another strange issue, however I canno reproduce it. I've set up a Dummy job that is triggered by many matrix jobs when they are done. This is supposed to add something to the build queue, so the neglected batch tasks from the matrix jobs waiting there finally get triggered. Now the Dummy job is also waiting in the build queue with the timeout/clock symbol. All executors are available but nothing happens. If I start the Dummy job manually, nothing happens, too. I have to add a new job to the queue to get it finally flushed to the executors.
Please have a review on the build queue handling.
Axel Heider
added a comment - Todays I've seen another strange issue, however I canno reproduce it. I've set up a Dummy job that is triggered by many matrix jobs when they are done. This is supposed to add something to the build queue, so the neglected batch tasks from the matrix jobs waiting there finally get triggered. Now the Dummy job is also waiting in the build queue with the timeout/clock symbol. All executors are available but nothing happens. If I start the Dummy job manually, nothing happens, too. I have to add a new job to the queue to get it finally flushed to the executors.
Please have a review on the build queue handling.
Can you find/post steps to reproduce the issue? How are the slave nodes configured?