New builds not picking up changes to render.yaml

1

Is anyone seeing this?

Successive builds are not picking up changes made to render.yaml in the newer commits.

Oct. 29 09:26:13 PM  ==> Empty build command; skipping build
Oct. 29 09:26:13 PM  ==> Generating container image from build. This may take a few minutes...

For example, after adding a new buildCommand to render.yaml, the build doesn’t pick up the command and builds a container image as if buildCommand was not specified at all.
Another change made to startCommand isn’t picked up too. Build fails to deploy with the broken startCommand even though the latest commit fixed the startCommand.

I guess it’s some kind of cache invalidation issue for render.yaml. I tried clearing the build cache to no avail.

2

Hi there,

Thanks for reaching out.

We’ll need a little more to go on here, for example, were you auto-deploying or manual? Were “Syncs” showing under the Blueprint, what was their change message?

If you could share some specific examples of the issue you are experiencing that may help us troubleshoot it with you, e.g. any logs/errors/output, Blueprint Name/ID, service Name/ID, reproduction steps, etc. If you don’t want to share these details on the community forum, please feel free to raise a ticket with support@render.com

Thanks

Alan

1 Like
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.