revi-archive/llvm-premerge-checks
1
0
Fork 0
Code Activity

Update monitoring_main_branch.md

Browse source 
fixed link
This commit is contained in:
ChristianKuehnel 2022-02-07 09:59:29 +01:00 committed by GitHub
parent 1444797003
commit 2b9971ffc5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/monitoring_main_branch.md
View file

@ -28,7 +28,7 @@ revisions and this the probability of a false-positive pre-merge test is lower.
We would deploy another container as part of the existing Kubernetes cluster for
pre-merge testing. The image would be based on
[buildkite-premerge-debian]https://github.com/google/llvm-premerge-checks/blob/main/containers/buildkite-premerge-debian/Dockerfile)
[buildkite-premerge-debian](https://github.com/google/llvm-premerge-checks/blob/main/containers/buildkite-premerge-debian/Dockerfile)
, and we would just add the things needed for the Buildbot agent by resuing the
setup of an existing worker (e.g.
[clangd-ubuntu-clang](https://github.com/llvm/llvm-zorg/blob/main/Buildbot/google/docker/Buildbot-clangd-ubuntu-clang/Dockerfile.)