![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
29/Jun/12 7:46 AM
|
|
Description:
|
We are experiencing a strange behavior of our Matrix projects. Say you have a Free-Style project "Foo" preparing sources, then triggering a Matrix project "Bar" which builds from these sources on various slave machines.
Both projects are configured to only keep the latest 10 builds. Looking on the project pages only the latest 10 builds are visible. Same in the project directories (e.g. jobs/Bar/builds). But when you look into the project pages from the slaves, as well as into the sub directories (e.g. jobs/Bar/configurations/axis-label/someslave/builds), all builds ever done are still there.
This seems to happen only to Matrix projects called by upstream projects. Standalone Matrix projects seem also been cleaned up in their sub directories.
As the Foo-project's build are not kept, clicking on an old build's trigger link within Bar's someslave project page only leads to a 404.
|
|
Environment:
|
SUSE Linux Enterprise Server 11.1 (x86_64); JDK 1.6.0_26; Jenkins 1.447.1
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Matthias Kraft
|
|
|
|
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
|
