Scan all builds only re-scans failed builds

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When I select "Scan all builds" in the scan-on-demand menu for a job, only failed jobs are re-scanned. As a result, successful builds that were not initially scanned at creation-time are not added to the statistics database.

      This is only really a problem if one changes the "Enable statistics logging of successful builds" option in the configuration and then expects historical successful builds to be added to the database. This is likely a fairly uncommon scenario, but my need for it stems from accidentally allowing the successful build logging to be disabled by https://issues.jenkins-ci.org/browse/JENKINS-59610 and now wanting to include successful builds from the period during which the misconfiguration was applied.

       

      Cheers

            Assignee:
            Tomas Westling
            Reporter:
            Stephen Humphries
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: