-
Notifications
You must be signed in to change notification settings - Fork 202
(Update) MixStep Clarify #11643
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
base: main
Are you sure you want to change the base?
(Update) MixStep Clarify #11643
Conversation
Clarify how mixed serial and parallel work. Removed summary, and converted to single heading article
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68d30a87ec3d18354a7bdac5--harness-developer.netlify.app |
Hi @KinnonYee-harness what does this PR address? Due to the length of the page, collapsible sections keep the page manageable. |
@dewan-ahmed , there's a couple things this addresses We have a lot of customers trying to find the data in this page and often not being able to locate it. The other item has to do when we mix serial and parallel steps. The article currently infers that only serial steps after the parallel deployments are declared with the added limits, but what actually happens is that ALL steps in the stage inherit those limit declarations |
docs/continuous-integration/use-ci/set-up-build-infrastructure/resource-limits.md
Outdated
Show resolved
Hide resolved
docs/continuous-integration/use-ci/set-up-build-infrastructure/resource-limits.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with minor changes requested.
…/resource-limits.md Co-authored-by: Dewan Ishtiaque Ahmed <[email protected]>
…/resource-limits.md Co-authored-by: Dewan Ishtiaque Ahmed <[email protected]>
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: