You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if there is a redundancy in the descriptions of Continuous Delivery and Continuous Integration on the main page. As defined there, CD encompasses CI. CI requires that "all feature work stops when the build is red". Then, CD requires "Use Continuous Integration" and that "all feature works stops when the pipeline is red".
If red build and red pipeline are distinguished here on purpose, there should be a definition of what comprises a "build" (e.g., are automatic tests part of this?). If there is no meaningful distinction, I suggest we drop it from the CD definition, as it is already included by requiring CI.
Best regards,
Michael
The text was updated successfully, but these errors were encountered:
Make perfect sense to me. The only objection I can think about would be that we want to put an emphasis on this point.
... Except if we have steps which could go red in the CD pipelines that are not part of CI. If that's the case, it's not redundant. But does it complies with the scope of minimal CD?
Hi,
I wonder if there is a redundancy in the descriptions of Continuous Delivery and Continuous Integration on the main page. As defined there, CD encompasses CI. CI requires that "all feature work stops when the build is red". Then, CD requires "Use Continuous Integration" and that "all feature works stops when the pipeline is red".
If red build and red pipeline are distinguished here on purpose, there should be a definition of what comprises a "build" (e.g., are automatic tests part of this?). If there is no meaningful distinction, I suggest we drop it from the CD definition, as it is already included by requiring CI.
Best regards,
Michael
The text was updated successfully, but these errors were encountered: