#778: 'latest' revision get's stuck on grid views when source step fails
--------------------+-------------------------------------------------------
Reporter: marcusl | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.9.+
Version: 0.7.12 | Keywords: web
--------------------+-------------------------------------------------------
Comment(by marcusl):
The last result is what I care about, and if I build an older revision
again, it would phase out the "latest", or at least be just below it.
The thing is, I have a JS-style fetcher for our intranet-frontpage which
gets this view and colors the projects title based on the most recent
build result. Having latest at the bottom is annoying. (There are some
projects that gets committed to rarely, but build each day. These
sometimes fail in checkout resulting 'latest'. I can't get latest off the
view until I commit a new thing.
I admit it's a narrow use case, but sorting by latest feels more natural
anyway.
I should probably scratch my own itch, right? :)
--
Ticket URL: <http://buildbot.net/trac/ticket/778#comment:7>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
