compiler plugin

On Tue, Jul 12, 2016 at 02:58:35PM +0200, Stephan Bergmann <sbergman at
redhat.com> wrote:
> where the first link, <http://ci.libreoffice.org/job/lo_gerrit/25/>
is the
> one to the results of the new Clang+plugins bot.  However, it is
unclear to
> me how to navigate from that page to the relevant information about
the
> failure, <http://ci.libreoffice.org/job/lo_gerrit/Config=linux_clang_
dbgutil_64/25/console>.

This is well known issue of non-obvious way to find out where actually
the logs of Jenkins matrix job are. And if you think you were happy to
find the logs for the right patch set and platform combination, you
start the game from the beginning to find out where the logs for
another patch set/platform combinations are. There are *four* different
kind of meta data involved in the process:

1. Gerrit: find out the right comment in the comment table from the
Jenkins Matrix job (watch for the patch set it was commented on)
2. Jenkins: find out the matrix job that corresponds to the comment in
1
3. Jenkins: find out the right platform job from the matrix job in 2
4. Jenkins: find out single job build outcome for the platform job in 3

Too many steps? Confusing? Something that could be improved?

Khai from the Openstack project and myself wrote verify-status gerrit
plugin: [1], that maintains secondary verify notification channel (the
fist one is reviewers notification channel; the comment table on change
screen should only include human comments and no spam with build
start/end notifications), persists the data in its own database (one
table) and loads and visualizes the data per patch set on the change
screen. With this plugin deployed, all 4 steps above are gone. Either
drop down control is used with links to the build log per per job that
corresponds to the patch set currently loaded on the change screen. Or,
alternatively, dedicated verify-status panel from the plugin is
rendered directly on the change screen.

Announcement: [2]. Screenshot: [3].

ATM Jenkins trigger plugin must be extended to support this verify
channel, e.g. plugin ssh command must be invoked to add build events to
the plugin data: [4].

Needless to say, that ones this works, the notification fire hose that
spams comment table with build notifications should be shut down.
Moreover the data gathered in the plugin can be easily accessed and
evaluated either directly with database own SQL tools, or even remotely
per plugin own ssh command: [5].

* [1] https://gerrit.googlesource.com/plugins/verify-status/+/master/sr
c/main/resources/Documentation
* [2] http://lists.openstack.org/pipermail/openstack-infra/2016-March/0
04098.html
* [3] https://imgur.com/KDquXfy
* [4] https://gerrit.googlesource.com/plugins/verify-status/+/master/sr
c/main/resources/Documentation/cmd-save.md
* [5] https://gerrit.googlesource.com/plugins/verify-status/+/master/sr
c/main/java/com/googlesource/gerrit/plugins/verifystatus/commands/Verif
yStatusAdminQueryShell.java