No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@U83S3MLQ0> can confirm, but I do not believe it does.  The service itself would prevent two updates from running concurrently, but it would be the second build would hit an error when it calls “pulumi update”, which would probably fail the overall operation.

Yeah, although I just found an orb that may do what I need!

<https://circleci.com/orbs/registry/orb/eddiewebb/queue>

Yes, Matt speaks the truth. The Pulumi Service can take care of concurrency so no two stack updates can happen at the same time… though like you are asking about, that isn’t good enough for a CI/CD environment.

Thanks for sharing that link, I’ll be sure to update our CircleCI docs to mention it.