Service for managing comments on GitHub
Go to file
Jakub Sokołowski 0f57359cb6
upgrade Octokit/rest: 16.2.0 > 16.30.1
Also add a yarn.lock to the repo

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2019-09-30 12:44:48 +02:00
src upgrade Octokit/rest: 16.2.0 > 16.30.1 2019-09-30 12:44:48 +02:00
test upgrade Octokit/rest: 16.2.0 > 16.30.1 2019-09-30 12:44:48 +02:00
.gitignore upgrade Octokit/rest: 16.2.0 > 16.30.1 2019-09-30 12:44:48 +02:00
Dockerfile don't build files to dist, just get them from src 2018-12-27 14:37:25 +01:00
LICENSE add MIT license 2018-12-22 12:04:50 +01:00
README.md fix url encoding 2019-09-30 12:29:06 +02:00
gulpfile.js improve sorting or builds by grouping them by commit 2019-01-15 20:09:26 +01:00
package.json upgrade Octokit/rest: 16.2.0 > 16.30.1 2019-09-30 12:44:48 +02:00
yarn.lock upgrade Octokit/rest: 16.2.0 > 16.30.1 2019-09-30 12:44:48 +02:00

README.md

Description

This is a minimal REST API intended for use with a Continuous Integration system for managing comments on GitHub.

The problem this solves is posting comments in a PR from multiple builds without spamming the comment section. Instead we post just one comment with a table and continue to update it.

Example Comment


Jenkins Builds

Commit #️⃣ Finished (UTC) Duration Platform Result
a088572b #3 2018-12-21 12:12:55 ~12 min android 📄log
a088572b #3 2018-12-21 12:13:18 ~12 min android 📄log
✔️ a088572b #3 2018-12-21 12:13:53 ~12 min ios 📦api
✔️ a088572b #3 2018-12-21 12:13:34 ~12 min android 📦apk 📲
✔️ a088572b #3 2018-12-21 12:14:44 ~12 min windows 📦exe

API

It exposes 3 calls:

  • POST /builds/:repo/:id - Add a new build result and update the PR comment.
  • POST /builds/:repo/:id/refresh - Re-render the PR comment for given ID.
  • POST /comments - Show currently managed comments in PRs.

By default it listens on localhost:8080.

Usage

$ cat << EOF
{
  "id": 1, "commit": "7367f3d5", "success": true, "platform": "linux", "duration": "~15 min",
  "url": "https://ci.status.im/job/status-react/job/prs/job/linux/job/PR-7123/1/",
  "pkg_url": "https://status-im-prs.ams3.digitaloceanspaces.com/StatusIm-181212-211210-5157d2-pr.AppImage"
}
EOF >> /tmp/body/json

$ curl -s -XPOST http://localhost:8000/builds/7123 -d@/tmp/body.json -H 'Content-Type: application/json'
{ "status": "ok" }

$ curl -s -XPOST http://localhost:8000/builds/7123/refresh
{ "status": "ok" }

You can also check all PRs the application knows about:

$ curl -s http://localhost:8000/comments
{
  "count": 2,
  "comments": [
    { "pr": "7000", "comment_id": 446940840 },
    { "pr": "7084", "comment_id": 446779864 }
  ]
}

Configuration

There are few environment variables you can set:

  • LISTEN_PORT - Self explanatory. (Default: 8000)
  • DB_SAVE_INTERVAL - How often database is written to disk. (Default: 5000)
  • DB_PATH - Path where the LokiJS DB file is stored. (Default: /tmp/builds.db)
  • GH_TOKEN - Required for GitHub API access.
  • GH_REPO_OWNER - Name of owner of repo to manage.
  • GH_REPO_NAMES - Whitelist of names of GitHub repos to manage. (Empty means all)

Building

  • yarn run start - For production use.
  • yarn run devel - For development use.
  • yarn run default - For building use.
  • yarn run release - To create and push the docker image use.