[pipelines] Stage can't support more than 25 stacks #11315
Assignees
Labels
@aws-cdk/pipelines
CDK Pipelines library
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
in-progress
This issue is being actively worked on.
p1
Milestone
Comments
JFox
added
bug
|
I really wonder if this can be fixed as it requires extra stages and stages cannot share cross references. |
|
I'm currently trying to solve this issue. I'll soon create a merge request if I'm able to achieve the correct result. |
victorlevasseur
added a commit
to victorlevasseur/aws-cdk
that referenced
this issue
Nov 29, 2020
CdkStage can now create multiple codepipeline stages. If the stage has not enough room remaining for the next stack, it will insert a new stage and continue processing it. Manually added actions are also added to the correct stage depending on their run order. Closes aws#11315
victorlevasseur
added a commit
to victorlevasseur/aws-cdk
that referenced
this issue
Nov 29, 2020
CdkStage can now create multiple codepipeline stages. If the stage has not enough room remaining for the next stack, it will insert a new stage and continue processing it. Manually added actions are also added to the correct stage depending on their run order. Closes aws#11315
victorlevasseur
added a commit
to victorlevasseur/aws-cdk
that referenced
this issue
Nov 29, 2020
CdkStage can now create multiple codepipeline stages. If the stage has not enough room remaining for the next stack, it will insert a new stage and continue processing it. Manually added actions are also added to the correct stage depending on their run order. Add afterPreparation method to CdkStage to allow a function to be executed after the CdkStage has been prepared (actions bound to their underlying codepipeline stage). Closes aws#11315 BREAKING CHANGE: IAction actions are bound to the underlying codepipeline stages of the CdkStage late. * **pipelines:** ShellScriptAction IGrantable interface can only be used after the action is effectively bound to the stage, usage of afterPreparation is required to use the action as an IGrantable
|
Treated as part of #10872. |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When attempting to deploy a pipeline with more than 25 stacks, the deploy fails due to the stage having more than 50 actions.
Reproduction Steps
Deploy a pipeline with > 25 stacks.
What did you expect to happen?
Deployment to succeed
What actually happened?
On deploy, the following error is hit:
Pipeline stage '<StageName>' has too many actions. There can only be up to 50 actions in a pipeline stage (Service: AWSCodePipeline; Status Code: 400; Error Code: InvalidStageDeclarationException; Request ID: xxx)Environment
Other
Tried to work it around by referencing cross-stage but got
dependency cannot cross stage boundarieserror.Similar issue, but for assets: #9353
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: