This message was deleted.

https://www.pulumi.com/docs/troubleshooting/#:~:text=%5B409%5D%20Conflict%3A%20Another%20update%20is%20currently%20in%20progress.&text=The%20service%20makes%20sure%20that,you%20are%20attempting%20to%20update.

So you basically do

pulumi cancel

and

pulumi stack export | pulumi stack import

before running

pulumi up

in your cicd pipeline?

@sparse-spring-91820 i think in CI system u can enforce things not to run in parall, wait for the job instance to complete before running another instance of the same pipeline / job

@steep-beach-52652 As far I can see, Circleci doesn't have option to wait for the previous job to finish in order to start a new one for selected branches. It has only this option:

Auto-cancel redundant builds

With the exception of your default branch, we will automatically cancel any queued or running builds on a branch when a newer build is triggered on that same branch. Scheduled workflows and re-runs are not auto-canceled.

but I don't think I want it because we can run into some issues if pulumi job is canceled during deployment

its python (or other programming language), so maybe u can check in python if pulumi is already running then sleep till pulumi is not running already before applying changes

@steep-beach-52652 Thank you for your help! I don't think watch command will work for circleci cicd pipeline as it will last forever and it would cost a lot of money (but I don't think that circleci allows no-ending processes anyway because it will timeout)

not sure about circleci, but in jenkins for example i can keep running pulumi watch and keep pulling the changes every X seconds for example