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
plaintext(`:double_vertical_bar: ${pipeline.name} has been paused`)
),
section(
markdown(`The deployment pipeline has been paused due to detected issues in ${pauseCause}. Here are the steps you should follow to address the situation:\n
:mag_right: *Step 1: Review the Errors*\n Review the errors in the *<${gocdLogsLink}|GoCD Logs>*.\n
:sentry: *Step 2: Check Sentry Release*\n Check the *<${sentryReleaseLink}|Sentry Release>* for any related issues.\n
:thinking_face: *Step 3: Is a Rollback Necessary?*\nDetermine if a rollback is necessary by reviewing our *<${IS_ROLLBACK_NECESSARY_LINK}|Guidelines>*.\n
:arrow_backward: *Step 4: Rollback Procedure*\nIf a rollback is necessary, use the *<${ROLLBACK_PLAYBOOK_LINK}|GoCD Playbook>* or *<${GOCD_USER_GUIDE_LINK}|GoCD User Guide>* to guide you.\n
:arrow_forward: *Step 5: Unpause the Pipeline*\nWhether or not a rollback was necessary, make sure to unpause the pipeline once it is safe to do so.`)
),
];
if(ccUsers.length>0){
blocks.push(
context(
markdown(
`cc'ing the following ${
uniqueUsers.length>10 ? `10 of ${uniqueUsers.length} ` : ''
}people who have commits in this deploy:\n${ccString}`
)
)
);
}
returnblocks;
},
, we are starting to introduce more usages of it (#790). We should refactor the deployFeed to make the flow of finding authors and pinging them in response to a failure more reusable.
The text was updated successfully, but these errors were encountered:
For a while we only ever had one usage of replyCallback:
eng-pipes/src/brain/gocdSlackFeeds/index.ts
Lines 236 to 293 in f4b4c07
The text was updated successfully, but these errors were encountered: