I have one cloud build trigger in one of our projects that deploys an App Engine. I have also created a pubsub topic named 'cloud-builds' in this same project, and I see that build event messages are being sent to that topic during and at the end of builds.
I am attempting to use this topic in another project with a pubsub cloud build trigger. This works, but has no filtering, and as described on this page, its firing the build way too often: https://cloud.google.com/build/docs/automating-builds/create-pubsub-triggers#risks_associated_with_an_unfiltered_trigger Now, all I need to determine how to do is add the filtering so only successful builds with the right trigger ID are used. The documentation (https://cloud.google.com/build/docs/automating-builds/create-pubsub-triggers#using_cel_to_filter_build_events) says to add something like this to my cloud build trigger filter: filter: build.build_trigger_id == "redacted" && build.status == Build.Status.SUCCESS However, I am never able to save my trigger, as whatever I type into the filter fails syntax validation. All the examples given on that page fail. I have not been able to find any examples on the net, either. I have tried subsets of these, exactly as described in the documentation, and they all fail with syntax errors. How is this supposed to be entered into the cloud build trigger filter? We cannot have every one of the pubsub messages firing a build, as I saw at least 15 messages delivered when there was no filter, triggering 15 builds in quick succession, most of which failed due to app engine deployment concurrency. Please, need some assistance. Also, better documentation around this area would be good. Many thanks, Tom Harris -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/3d4b74b4-30c4-437b-b1c9-f55de84ade7dn%40googlegroups.com.
