![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Lucie Votypkova
|
|
Components:
|
disk-usage |
|
Created:
|
25/Mar/14 7:37 PM
|
|
Description:
|
We noticed the following strange behaviour on quite a lot of our jobs.
After all build steps and post build steps finished, the build is in some quite inconsistent state for up to exactly 5min:
- the Console is still spinning with no output
- the big ball of the job is still blinking
- starting the job again results in "current job is already building"
ALTHOUGH
- the build is shown as finished in the build history of the job
- it has disappeared from the slave it was running on
I especially liked the build history, when you start a new build #128, it says, build #127 is still in progress, and right below you see a quite finished build #127 ![]()
We double checked enabling and disabling the disk-usage-plugin, and it was clearly causing this issue. The 5min are probably some kind of timeout somewhere.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Marc Günther
|
|
|
|
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.
