sourcegraph/dev/build-tracker
2024-08-13 13:22:41 +02:00
..
build Revert "chore(ci): rework build-tracker to use redis instead of in-memory store of build results" (#64436) 2024-08-13 13:22:41 +02:00
config bazel: transcribe test ownership to bazel tags (#62664) 2024-05-16 15:51:16 +01:00
notify build-tracker: remove old links (#63065) 2024-06-04 12:03:58 +01:00
.gitignore feat(build-tracker): Adds a build-tracking service to provide better notifications about build failures (#39355) 2022-08-02 17:25:39 +00:00
background.go Revert "chore(ci): rework build-tracker to use redis instead of in-memory store of build results" (#64436) 2024-08-13 13:22:41 +02:00
bigquery.go build-tracker: include timestamp in agent state change events (#62670) 2024-05-14 18:03:17 +00:00
BUILD.bazel Revert "chore(ci): rework build-tracker to use redis instead of in-memory store of build results" (#64436) 2024-08-13 13:22:41 +02:00
image_test.yaml build-tracker: deploy to MSP (#61510) 2024-04-03 11:49:57 +01:00
integration_test.go Revert "chore(ci): rework build-tracker to use redis instead of in-memory store of build results" (#64436) 2024-08-13 13:22:41 +02:00
main_test.go ci: use build creator when the build is a release build (#61545) 2024-04-03 16:52:41 +02:00
main.go Revert "chore(ci): rework build-tracker to use redis instead of in-memory store of build results" (#64436) 2024-08-13 13:22:41 +02:00
mocks_test.go build-tracker: emit agent state-change webhook events to BigQuery (#62598) 2024-05-12 16:20:04 +02:00
README.md Revert "chore(ci): rework build-tracker to use redis instead of in-memory store of build results" (#64436) 2024-08-13 13:22:41 +02:00
server_test.go Revert "chore(ci): rework build-tracker to use redis instead of in-memory store of build results" (#64436) 2024-08-13 13:22:41 +02:00

BUILD TRACKER

Build Tracker is a server that listens for build events from Buildkite and stores them in memory and sends notifications about builds if they've failed.

The server currently listens for two events:

  • build.finished
  • job.finished

For each job.finished event that is received, the corresponding build is updated with the job that has finished. On receipt of a build.finished event, the server will determine if the build has failed by going through all the contained jobs of the build. If one or more jobs have indeed failed, a notification will be sent over slack.

Deployment infrastructure

Build Tracker is deployed in the Buildkite kubernetes cluster of the Sourcegraph CI project on GCP. For more information on the deployment see infrastructure

Build

Execute the build.sh script which will build the docker container and push it to correct GCP registry. Once the image has been pushed the pod needs to be restarted so that it can pick up the new image!

Test

To run the tests execute go test .

Notification testing

To test the notifications that get sent over slack you can pass the flag -RunSlackIntegrationTest as part of your test invocation, with some required configuration:

export SLACK_TOKEN='my valid token'
export BUILDKITE_WEBHOOK_TOKEN='optional'
export GITHUB_TOKEN='optional'
go test . -RunSlackIntegrationTest

You can enable Slack client debugging by exporting the following environment variable BUILD_TRACKER_SLACK_DEBUG=1