Vinay Anantharaman
Vinay Anantharaman

Reputation: 139

Google Cloud Builds Trigger for GitHub Repo says "No tag matches" Always

Build Trigger Setup

Things I've Looked at

Current Results and Expectation

I expect there to be tags matched because the repo has some tags. I push some new tags and nothing has changed.

Upvotes: 3

Views: 1886

Answers (1)

williamli
williamli

Reputation: 4104

Note: Google Cloud Build's GitHub Marketplace Plugin is still in Alpha, so its features are not reliable and it is not unusual to run into breaking changes... and there is no active support for it.

The screen you are seeing is from Google Cloud Platform -> Cloud Build -> Triggers. It is different and unrelated to the Google Cloud plugin found inside the GitHub Marketplace (I know, it is confusing).

The triggers you setup currently pull in GitHub repos into Google Cloud Source Repositories before your triggers are executed.

The GitHub plugin, I have been having some issues with it these few days and I think they are introducing some new breaking changes on it soon, but when it worked, it does not require any triggers and purely looks at the cloudbuild.yaml file to do builds automatically. I had to create separate scripts inside the cloudbuild.yaml to setup different build based on tags / branches (Cloud Build Triggers let you do all these inside the UI), but what you get as part of the GitHub plugin is this "GitHub Checks Events" (the green check / red cross) next to the corresponding commits in GitHub and also a very brief details page. The GitHub plugin is currently acting weird on me and I am in the process of switching over to use Cloud Build Triggers until they have sorted it out.

enter image description here enter image description here

I think they are working on something to bridge the difference between Google Cloud Build Triggers and the Cloud Build GitHub plugin... just a feeling from the current log messages I see inside Cloud Build...

Upvotes: 1

Related Questions