[MacPorts] #55978: buildbot new view implementations

MacPorts noreply at macports.org
Tue Mar 6 20:52:28 UTC 2018


#55978: buildbot new view implementations
-------------------------+-----------------
 Reporter:  mojca        |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  website      |    Version:
 Keywords:  buildbot     |       Port:
-------------------------+-----------------
 This is a draft description of ideas for implementing some new views for
 Buildbot 1.0.
 Alternatively, even if these don't get implemented in Bulidbot, it would
 be nice to implement them elsewhere as some standalone views / links.

 == View nr. 1: List of commits ==

 An equivalent of
 https://github.com/macports/macports-ports/commits/master with clickable
 links to builds from individual commits.

 Perhaps with a calendar & clock widget to let the user select the time of
 when that commit was noticed by buildbot and added to the build queue. Or
 maybe some timeline graph where the user could simply slide on timeline to
 get the commits around the selected time slot.

 For example:

 || color or check: failure/success || timestamp || short commit message ||
 committer || author || link to view nr. 2 ||

 == View nr. 2: Overview of a particular commit or individual forced build
 ==

 Top of the page: full info about commit:
 - committer name & timestamp
 - author name & timestamp
 - short & full commit message
 - URL to commit on github
 - potentially URLs to track tickets and PRs (if applicable)

 And then the summary:

 ||           || 10.13  || 10.12 || 10.11 || 10.10   || 10.9    || 10.8
 ||
 || port list || OK     || OK    || OK    || OK      || OK      || OK
 ||
 || port A    || OK     || OK    || FAIL  || OK      || FAIL    || SKIP
 ||
 || port B    || FAIL   || FAIL  || FAIL  || SKIP    || SKIP    || SKIP
 ||
 || port C    || SKIP   || OK    || OK    || FAILDEP || FAILDEP || FAILDEP
 ||

 == View nr. 3: Overview of history of builds of a particular port ==

 Top of the page: all relevant info about the port
 - name
 - current version
 - latest version (from livecheck)
 - maintainers (potentially with links to github profiles and/or existing
 trac pages)
 - maybe link to https://repology.org
 - maybe additional info like hyperlinks to dependencies' pages, ...
 constructed from separate scripts

 And then some kind of a table like this one:

 ||          ||      || ver || 10.13 || 10.12 || 10.11 || 10.10 || 10.9
 || 10.8 ||
 || commit A || time || 0.9 || OK    || OK    || OK    || OK    || FAILDEP
 || SKIP ||
 || commit B || time || 0.8 || OK    || OK    || OK    || OK    || FAILDEP
 || SKIP ||
 || force    || time || 0.8 ||       ||       || OK    ||       ||
 ||      ||
 || commit C || time || 0.8 || OK    || OK    || FAIL  || FAIL  || FAILDEP
 || SKIP ||
 || commit D || time || 0.7 || OK    || OK    || OK    || OK    || OK
 || SKIP ||

 with the ability to go back and forth in time to older and newer
 commits. The 'commit A' part would be a hyperlink to view nr. 2.

 "Faildep" in this or previous view would contain name of dependency
 and a link to the build page of the failed build where we marked the
 port as broken.

--
Ticket URL: <https://trac.macports.org/ticket/55978>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list