buildkite proxy is running on a separate 32-core node

google / llvm-premerge-checks

CI system for premerge-testing in LLVM project

Apache License 2.0

41 stars 37 forks source link

buildkite proxy is running on a separate 32-core node #233

Open ChristianKuehnel opened 4 years ago

ChristianKuehnel commented 4 years ago

It looks like the buildkite proxy is running on an otherwise empty n1-standard-32 node gke-llvm-premerge-chec-jenkins-agents-7806fdd2-hz4h. I guess this could also be deployed to the default-pool or a n1-standard-1 node.

Nothing major, but we could save some hardware resources there...

ChristianKuehnel commented 4 years ago

Right now it looks like we have 4 builders running with 6 nodes up. I changed the "jenkins-agents" cluster to autoscale 0-2, as it's not really loaded right now. Maybe we can also migrate the remaining services somewhere else. Not sure if we really need this cluster at all...