When slack is down Release Tools should be able to operate from ANY Release Managers workstation
😬
Problem Sometimes our tooling that we leverage external to us fails. Example, we leverage chatops to make calls to release tools' various rake tasks. We do this for convenience. But this requires both slack, and the integration between slack and our ops instance to work. Both of which we may not be able to rely on 100% of the time.
Thus, we should have the ability to validate that release-tools
is operable from a users' workstation.
🔍
Example This was one of those days: gitlab-org/release/tasks#5066 (closed)
🤔
Consideration - Create a rake task in
release-tools
that validates any given Release Manager has their workstation appropriately - Today an RM was attempting to run the publish command for a release, but was running into HTTP403's
- Since release-tools will commonly output some data to Slack, we should probably have a method of ensuring we bypass failures to post notifies and allow rake tasks to run to completion - this might already be the case, but worth validating?