Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14253

Discard Old Builds does not remove builds from Matrix-Axes

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • SUSE Linux Enterprise Server 11.1 (x86_64); JDK 1.6.0_26; Jenkins 1.447.1

      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.

          [JENKINS-14253] Discard Old Builds does not remove builds from Matrix-Axes

          dlavelle added a comment -

          I believe we are experiencing the same issue. Discard old builds on a Matrix job deletes the build from the server but the GUI still shows it is there. If you try to click on the job you get a 404 error.

          Does anyone have a fix or this or an update?

          dlavelle added a comment - I believe we are experiencing the same issue. Discard old builds on a Matrix job deletes the build from the server but the GUI still shows it is there. If you try to click on the job you get a 404 error. Does anyone have a fix or this or an update?

          dlavelle added a comment -

          BTW we are using Jenkins 1.486

          dlavelle added a comment - BTW we are using Jenkins 1.486

          We are seeing this now also. I think it started at around version 1.480

          Steve Mitchell added a comment - We are seeing this now also. I think it started at around version 1.480

          We are also experiencing same issue. Have started using matrix builds on a few more projects now and have run out of disk space on jenkins server, which blocks any more builds running.
          Currently using version 1.486

          Robert O'Brien added a comment - We are also experiencing same issue. Have started using matrix builds on a few more projects now and have run out of disk space on jenkins server, which blocks any more builds running. Currently using version 1.486

          Kind of seeing the same problem after setting up slaves on Jenkins 1.560, builds are not properly deleted.

          Goffredo Marocchi added a comment - Kind of seeing the same problem after setting up slaves on Jenkins 1.560, builds are not properly deleted.

          Daniel Beck added a comment -

          Does anyone who experienced this in Jenkins 1.4xx still have this issue?

          How does Foo trigger Bar? Is Bar parameterized? What are the parameter types?

          Daniel Beck added a comment - Does anyone who experienced this in Jenkins 1.4xx still have this issue? How does Foo trigger Bar? Is Bar parameterized? What are the parameter types?

          Meanwhile I am no longer in charge of our Jenkins. I looked at a couple of jobs that did have the issue in the past and they no longer seem to have it. I go confirming that with the responsible guy ...

          Matthias Kraft added a comment - Meanwhile I am no longer in charge of our Jenkins. I looked at a couple of jobs that did have the issue in the past and they no longer seem to have it. I go confirming that with the responsible guy ...

          I haven't heard anything back from our Jenkins admins. As I already wrote, there doesn't seem to be an issue anymore. I have no idea when or how this was resolved, though. Nevertheless I am closing this now.

          If a watcher to this issue disagrees, feel free to reopen or duplicate and explain to Daniel, how this behavior can be reproduced.

          Matthias Kraft added a comment - I haven't heard anything back from our Jenkins admins. As I already wrote, there doesn't seem to be an issue anymore. I have no idea when or how this was resolved, though. Nevertheless I am closing this now. If a watcher to this issue disagrees, feel free to reopen or duplicate and explain to Daniel, how this behavior can be reproduced.

            Unassigned Unassigned
            makr Matthias Kraft
            Votes:
            9 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: