This is provided by the Build Trend Filter. Take a look at the documentation here on the wiki:
https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters#ViewJobFilters-FilterbyBuildTrend If this still doesn't help you, let me know, and I will definitely walk you through this. On Fri, Sep 21, 2012 at 8:51 AM, Xavier Nodet <xavier.no...@gmail.com>wrote: > Hi Jacob! > > From the 'Roadmap' section in > https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters, it seems > that these features you mention are not yet implemented. On the other hand, > you must know what you're talking about, as the maintainer of this plugin... > > So then it must be me: I didn't find a way to filter out jobs not run in > some time, or that started more than X hours ago. > > I'm using version 1.22 of the plugin, with Jenkins 1.456. > > Thanks. > > Xavier. > > On Mon, Sep 17, 2012 at 3:33 PM, Jacob Robertson < > jacob.robertson.w...@gmail.com> wrote: > >> The View Job Filters plugin is related to some of what you are asking >> for. For example, you could build a View that shows all jobs that have not >> been run in over a month. You might also be able to address your Hung >> builds scenario by creating a View for jobs that are currently building and >> were started over X hours ago. >> >> >> On Fri, Sep 14, 2012 at 11:50 AM, Xavier Nodet <xavier.no...@gmail.com>wrote: >> >>> Hi Fred, >>> >>> Yes, I know about this plugin. But it will only abort the build, >>> instead of notifying me. >>> And this may not always be the correct option. So I would have to use a >>> very large timeout... >>> >>> Thanks. >>> >>> -- >>> Xavier Nodet >>> >>> >>> On Fri, Sep 14, 2012 at 12:25 PM, Fred G <fred.g...@googlemail.com>wrote: >>> >>>> Hi Xavier, >>>> >>>> Have you tried the Build Timeout plug-in ( >>>> https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin) yet? >>>> It might help you >>>> with detecting blocked jobs. >>>> >>>> Regards, >>>> >>>> Fred >>>> >>>> >>>> On Thursday, September 13, 2012 12:48:20 PM UTC+2, Xavier Nodet wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I've been using Jenkins for a year now, and I'm missing the following >>>>> features... >>>>> Do they exist in a plugin that I missed? >>>>> >>>>> More context is available at http://xnodet.blogspot.fr/** >>>>> 2012/09/suggestions-for-**jenkins-on-multi.html<http://xnodet.blogspot.fr/2012/09/suggestions-for-jenkins-on-multi.html> >>>>> Thanks. >>>>> >>>>> Detect stale jobs >>>>> We sometimes have jobs that stop running (no new run is triggered, or >>>>> no available nodes). This is of course not intended, and it would be nice >>>>> to be able to detect those easily. I suppose that adding a 'Last build' >>>>> column to the list view, that would display the time since the job entered >>>>> its current state, would be nice. Something like 'Ended 8.6 hr' or >>>>> 'Queued >>>>> 1.3 hr' or 'Started 12 min'... >>>>> >>>>> Then I'd know that if the code changed 3 hours ago, I shouldn't see >>>>> any number larger than 3 hours... >>>>> >>>>> Detect hung jobs >>>>> We have many jobs running, typically 20 to 30 simultaneously. And some >>>>> builds last for several hours. It happens that tests hang, or are >>>>> abnormally slow. These situations should be detected as soon as possible >>>>> for investigation. >>>>> >>>>> Unfortunately, the 'Build History' list is not very helpful, for two >>>>> reasons. It has too few jobs for us: with 50 builds, only the last 5 hours >>>>> are covered, which is less than the duration of many of our builds. But >>>>> then if this limit was increased, we'd probably need a list of 200 or so >>>>> jobs, which would not be easy to handle. >>>>> >>>>> I would thus suggest to allow filtering on the 'building' status. >>>>> When this flag would be set, the 'Build History' would only display the >>>>> jobs that are currently being built. >>>>> >>>>> A view 'by revision' >>>>> I often need to check if a given revision of the source has been built >>>>> by a given job, or what is the latest revision that is good on a set of >>>>> jobs. For example, I may want to merge this revision to some 'stable' >>>>> branch for other teams to use. >>>>> >>>>> I think that a grid view with the following attributes would be very >>>>> useful for this: each line is a commit id or SVN revision, each column is >>>>> a >>>>> job, each cell is blue, red or gray (or even empty if this revision has >>>>> not >>>>> yet been part of a run of the job, or the run is not finished yet). >>>>> >>>>> >>>>> Do you think these would be useful additions? >>>>> >>>>> -- >>>>> Xavier Nodet >>>>> >>>>> >>> >>> >> > > > -- > Xavier Nodet > >
