|
||||||||
|
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 |
||||||||
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Hi Oleg, hi Daniel.
Yes, this issue still occurs for us. It is still very rare. In some cases, months can pass between the issue appearing.
One thing we did notice is, that cancelling jobs via the HTTP/CLI interface produces this issue more often. Instead of cancelling the actual job, it will cancel a totally unrelated job and keep the original one running. The server where we observed that had > 30 build hosts with 12 executors each running.
The server in question is running jenkins 1.509.4 with SSH-slaves v1.5. We are currently in the process of moving to v1.565 (LTS), but so far, we've not used it for long enough to say that the issue really does not appear there, too.