Skip to content

GitHub Actions

Render GitHub user instead of CI hostname in Engflow UI

When the EngFlow BES receives a BEP stream from Bazel it can only attribute builds to the OS username of the CI runner that is running the invocation and/or the principal stated in the certificate used to authenticate to the BES. In many cases this is not actually the user that is responsible for the build.

To fix this, you can send the GitHub username to the BEP using [bazel keywords][1] and your EngFlow cluster will use that username in the UI.

Pipe the github.actor GitHub variable into the command you use to run bazel. Exposing this as an environment variable allows you to use it in a script if you choose to do so.

YAML
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
...
jobs:
  build:
    steps:
      ...
      - name: My Build
        ...
        env:
          ...
          GITHUB_ACTOR: ${{ github.actor }}
        run: |
          bazel build //:my_target
          ...
          --bes_keywords=engflow:Requester=$GITHUB_ACTOR
          ...