-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Another CLI (PID=72391) is currently synthing to cdk.out when having MaxConcurrentTasks > 0 #501
Comments
Hi @dannysteenman ✋ Yes as part of the update to MaxConcurrentTasks we added an extra parameter to the Default Deploy Command Since you have a |
Yes I've tested it and it works perfectly! Thanks David! |
reopened this with the intention to clarify this in the documentation |
Subject of the issue
In the latest version of orgformation you introduced maxconcurrenttasks for aws-cdk tasks which is great! However when I try to set the concurrenttasks to e.g. 10 then the deploy fails because cdk.out is locked on 1 tasks causing the other tasks to fail.
This is the task:
When the task gets deployed:
Your environment
Steps to reproduce
Create a cdk stack, then the cdk task in orgformation and set maxconcurrenttasks to > 1
Expected behaviour
I expect that this feature allows you to deploy cdk stacks simultaneously on multiple accounts in parallel when MaxConcurrentTasks > 1.
Actual behaviour
cdk.out gets locked (normal cdk behaviour) and that causes the other deploys to fail.
Note: this could be solved by having the ability to add
--output
to a randomcdk-<random hash>.out
folderThe text was updated successfully, but these errors were encountered: