Submit Your Ideas

We want to hear from you - vote for the features and improvements you'd most like to see, or submit your own ideas if you don't find them already listed.

Add ability to search logs of previous builds

It would be useful to be able to search logs across containers (within and between builds), especially given the frequent increase in the standard number of jobs per build in CircleCI 2.0. In instances of (for example) repeated but inconsistent errors, the current method involves navigating to separate pages/container tabs, then searching within the page at a browser level (which may require expanding collapsed sections).

Increasing discoverability of test failures within builds (including the error and where it occurred within the build) helps developers pinpoint and resolve them.

At a more macro level, even filtering by job title or branch (or failures!) would be an excellent way to zoom in on errors. The current method involves a lot of human pattern-matching, a notoriously error-prone process.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 26 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 27, 2018 13:08

    Searching and filtering are probably our top need now that we've moved to Circle 2.0 - the large number of jobs can be a challenge to scroll through looking for patterns like "random failures", and search/filter would greatly simplify this.  Please consider this for the future!