How to deal with failing pipelines on the main branch? #500
-
|
Theoretically, when you have a large chunk (or any size for that matter) of deployment, and something fails either intermittently or structurally, what would be the procedure to remediate or repair? |
Beta Was this translation helpful? Give feedback.
Answered by
daltondhcp
Dec 22, 2021
Replies: 2 comments
-
|
Obviously it depends on the nature of the problem, but in general it shouldn't ever make it to main if it is failing, i.e. we should catch the problem during PR testing. What is the scenario more specifically? |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
daltondhcp
-
|
WhatIf does not execute the real thing. Only when the real thing happens
you will get real feedback. E.g. deploying a virtual machine.
Op wo 22 dec. 2021 08:35 schreef Johan Dahlbom ***@***.***>:
… Obviously it depends on the nature of the problem, but in general it
shouldn't ever make it to main if it is failing, i.e. we should catch the
problem during PR testing. What is the scenario more specifically?
—
Reply to this email directly, view it on GitHub
<#500 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPIYJF4HAN5LO2EO7MLYXDUSF5TTANCNFSM5KEU272A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Obviously it depends on the nature of the problem, but in general it shouldn't ever make it to main if it is failing, i.e. we should catch the problem during PR testing. What is the scenario more specifically?