Ci integration

[isakstenstrom]

For some time, bb-portal has had hard-coded integrations against GitHub and GitLab, where invocations from the same workflow are grouped together into builds which have additional visualizations. This has worked well, but only when using any of those systems.

This PR makes the integration with CI systems configurable from the jsonnet file, allowing for integration with any CI system.

How to configure

A new configuration field has been added called invocationMetadataExtractor that accepts a Jmespath expression. Its purpose is to extract data from the environment variables Bazel is executed with. The result of the extractor is expected to be a JSON object with the following fields:

• username: The username to be associated with the invocation.
• hostname: The hostname for the computer that ran the invocation.
• sourceControls: An array of objects representing a repository used by the invocation. The entity SourceControl now only contains a repo, ref and commit sha, as well as urls for each of them.
• invocationTags: JSON object with key-values to be associated with the invocation.
• buildTags: JSON object with key-values to be associated with the build.

Invocations are grouped togehter as builds based on the buildTags. A new config field has been added called buildKey, and invocations that have the same combination of instanceName and buildTags[buildKey] are grouped in the same build.

The tags are visualized on each build and invocation. Additionally, the build and build details tables can be configured with extra columns where specified tags are shown and can be filtered for.

Here is an example invocationMetadataExtractor for GitHub Actions:

{
  "username": env.USER
  "hostname": env.HOSTNAME
  "sourceControls": [
    {
      "repo": env.GITHUB_REPOSITORY
      "repoUrl": (env.GITHUB_SERVER_URL && env.GITHUB_REPOSITORY) && join('/', [env.GITHUB_SERVER_URL , env.GITHUB_REPOSITORY]) || `null`
      "ref": env.GITHUB_REF
      "refUrl": (env.GITHUB_SERVER_URL && env.GITHUB_REPOSITORY && env.GITHUB_REF) && join('/', [env.GITHUB_SERVER_URL, env.GITHUB_REPOSITORY, 'tree', env.GITHUB_REF]) || `null`
      "commit": env.GITHUB_SHA
      "commitUrl": (env.GITHUB_SERVER_URL && env.GITHUB_REPOSITORY && env.GITHUB_SHA) && join('/', [env.GITHUB_SERVER_URL, env.GITHUB_REPOSITORY, 'commit', env.GITHUB_SHA]) || `null`
    }
  ]
  "invocationTags": {
    "workflow": env.GITHUB_WORKFLOW
    "workflow_url": (env.GITHUB_SERVER_URL && env.GITHUB_REPOSITORY && env.GITHUB_RUN_ID) && join('/', [env.GITHUB_SERVER_URL , env.GITHUB_REPOSITORY, 'actions', 'runs', env.GITHUB_RUN_ID]) || `null`
    "job": env.GITHUB_JOB
    "action": env.GITHUB_ACTION
  }
  "buildTags": {
    "repo": env.GITHUB_REPOSITORY
    "repo_url": (env.GITHUB_SERVER_URL && env.GITHUB_REPOSITORY) && join('/', [env.GITHUB_SERVER_URL , env.GITHUB_REPOSITORY]) || `null`
    "workflow": env.GITHUB_WORKFLOW
    "workflow_url": (env.GITHUB_SERVER_URL && env.GITHUB_REPOSITORY && env.GITHUB_RUN_ID) && join('/', [env.GITHUB_SERVER_URL , env.GITHUB_REPOSITORY, 'actions', 'runs', env.GITHUB_RUN_ID]) || `null`
  }
}

Relevant discussion: #211