How to have latest cloned job commit when auto deploy is off

Hi @bchastanier the solution in the post you mention is to:

  1. Activate auto-deploy in blueprint env
  2. Stop blueprint
  3. This will always have the latest changes and blueprint won’t start on new commits

That I already do for my apps and it works just fine, when I deploy a preview environment 1) it will have the latest changes 2) if somethings is updated in my app the auto-deploy will kick in and update them and that is the expected behavior.

This is my current setup

The thing with this setup is that the Jobs have auto-deploy off and they are not getting the latest commits. This is by design.

Originally I had all with auto-deploy on, but then when a new commit got pushed for a Job the auto-deploy would start in the preview environment for that Job and it would create again external resources, because that it’s his job. That I do not want, the resource where already created when the preview environment was created, so having auto-deploy off is the way to go. But then we are back to square one, the Jobs are not getting the latest commits when the preview environment is created.

If there is currently a solution to this issue, don’t now yet how to implement it. Otherwise:


Have the option when auto-deploy is off, have a toggle with the option to have the latest commit.