After deploying an update to an app I noticed that in one of my stopped environments it starting deploying the change. From what I’ve read this shouldn’t be happening.
You push a commit an app within this env, this app is likely in an autodeploy mode
Your env is starting, more precisely a lifecycle job configured to be triggered on env start
If your app was stopped, it looks like a bug on our end, if your app is stopped, even with auto-deploy activated, it shouldn’t triggers an application start.
Can you confirm the setup? Your app has autodeploy activated and was stopped?
No worries, to confirm you question, our setup has autodeploy activated and the apps are stopped. This is our blueprint environment for preview environments that is always stopped.
I have not noticed this behaviour recently, but when I posted this, it did happen a couple more times.