| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most instances seem to not support direct branch / revision filtering
in Changes API requests, that is, requests such as
<host>/api/v2/changes?revision=<revision-id>
timeout or return an error code.
In such cases, we issue a more general API request, and filter the
response by revision:
<host>/api/v2/changes?limit=<limit>&order=-changeid
We add a new custom var `buildbot-api-changes-direct-filter' to
control the relevant behaviour.
The mariadb instance seems to be the only instance that work better
with direct filtering, whereas python and buildbot seems to work with
both, and the remaining instances only supporting indirect filtering.
We also add a few more custom vars for limiting in API requests, and
fix some regressions introduced in the previous commit, about setting
the host.
|
| |
|
|
|
|
|
| |
With a prefix arg, `buildbot-{revision,branch,builder}-open' will
prompt for a buildbot host first.
Also separate out the logic of getting builders.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Pass buildbot-host between buffers
- Set buildbot-builders automatically
- When the Changes API does not return builds, fetch the builds in a
separate call
This last change allows `buildbot-revision-open' to work with more
instances, including python and buildbot.
Also updated README with these changes, as well as ELPA installation
info.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
There are still some weird "Foo should be imperative" complaints, but
they do not seem to be important.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
* .gitignore: Adding elc
* README.org: minor changes to intro and todos
* buildbot-client.el: minor formatting and documentation fix
* buildbot-utils.el: minor formatting fix
* buildbot-view.el: minor formatting and require fix
* buildbot.el: minor keywords and formatting fix
|
| |
|
|
|
| |
Also updated keybindings: n/p for next/previous failures; M-n/M-p for
next/previous header; f/b for next/previous header of the same thing.
|
| | |
|
| |
|
|
|
| |
It is not as exciting as the other views because there's no easy way
to get commit message or test results for each build
|
| | |
|
| |
|
|
| |
...by correcting outdated revision info when opening build view.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
- in branch view, show revisions with build stats and all builds
- in revision view, show branches with build stats and all builds
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Also, now one can press return at any header to go to the respective
object. For example, in step view, one can jump to the revision view
by pressing return at the revision header on top
|
| |
|
