There may be a problem with live logs.
I’ve juste launch a new deployment and I’ve no new logs for magento-assets-builder.
I used auto-deploy feature, but if I deploy from the environment with " Deploy latest version for…", it has no effect too.
Ok I see, I guess there is a misunderstanding here. The trigger happens on environment deploy / redeploy, not on one service. So if you have auto deploy on your service and expect each deploy triggers the job, it won’t. I has to be an env action.
Do you have a CI? Maybe you can remove the autodeploy and trigger the env deploy from github action for example ? Or directly from your CI?
Pipelines usage and lifecylce jobs trigerring is not really clear…
The auto deploy feature was set for the environnement, not only a service:
So, lifecycle jobs triggering is expected…
Yes, sorry it’s a bit confusing, you are right, the autodeploy setting is set at env level, but is in fact implemented at service level (meaning only the given service having new commit will be deployed).
So now back to your issue, what you can do in your CI is either:
- Trigger env deploy in your CI job (the building job will be triggered) via the CLI
- Trigger deploy of the the building job and your app at the same time, order will apply and the build will happen before your app deploy, again via the CLI
In all cases better to disable auto deploy so your app is not deployed before the asset build is done