CloudBuild Trigger Name doesn't show up on GitHub.

46 views
Skip to first unread message

Evgenij Beloded

unread,
Nov 29, 2019, 5:07:46 PM11/29/19
to Google Cloud Developers

In description of Google Cloud Build app on GitHub here https://github.com/marketplace/google-cloud-build every build seems to be identifiable by name:
Screen Shot 2019-11-21 at 9.12.28 AM.png

In my current set up, however, every build is displayed by id, which is not very useful:


Screen Shot 2019-11-21 at 9.04.17 AM.png


Is there something I am not doing here?

Pierre-Yves Blain

unread,
Dec 3, 2019, 4:53:21 PM12/3/19
to Google Cloud Developers
In the description, the screenshot is only showing "Build" as an example.
Looking at the structure of a build config file, the "name" field [1] is actually used to specify a cloud builder [2].
Since multiple builds can specify the same cloud builder, this wouldn't uniquely identify the builds.
This is why getting the "id" is actually more useful for tracking individual builds.

[1] https://cloud.google.com/cloud-build/docs/build-config#name

Andrew Yurisich

unread,
Dec 9, 2019, 9:16:07 AM12/9/19
to Google Cloud Developers
I don't understand why the build config is used to generate metadata for the trigger object. Why not use the trigger name, which is required to be unique project-wide anyway?

Even if users have issues crossing wires when their GCP projects and github commit status contexts collide, I couldn't image it being a motivation for doing it the way it is currently.

Currently the only option I see is to set up a cloud function against the cloud build topic and manually update statuses that way.

Reply all
Reply to author
Forward
0 new messages