Skip to content
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

Allow to set non-concurrent CI pipeline #479

Closed
4 tasks done
mkleszcz opened this issue Feb 13, 2024 · 0 comments · Fixed by #482
Closed
4 tasks done

Allow to set non-concurrent CI pipeline #479

mkleszcz opened this issue Feb 13, 2024 · 0 comments · Fixed by #482
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@mkleszcz
Copy link
Contributor

Description

Related to #453

For the new AWS accounts there is an issue with the AWS CodePipeline concurrent builds. Initially the concurrent builds are not possible so pipeline is not working.

Describe the solution you'd like

We should have a setting in the stack that will enable concurrent build by setting runOrders in the correct way. By default this should work as it is but there should be a way of changing this behavior and it should be documented in the docs.

Describe alternatives you've considered

No response

Additional context

No response

Validations

@mkleszcz mkleszcz added the enhancement New feature or request label Feb 13, 2024
@mkleszcz mkleszcz added this to the 2.4.3 milestone Feb 13, 2024
@mkleszcz mkleszcz mentioned this issue Feb 13, 2024
3 tasks
@mkleszcz mkleszcz self-assigned this Feb 15, 2024
@mkleszcz mkleszcz mentioned this issue Feb 16, 2024
3 tasks
mkleszcz added a commit that referenced this issue Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant