-
Notifications
You must be signed in to change notification settings - Fork 0
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
codepipeline notification #113
Comments
Good ticket, Will. I'd vote higher priority (see in the board). (p.s. meant to mention this; we plan to use label more effectively in automation with project board. in this case, i'd recommend you label "platform" that will automatically add into "OrcaBus: Platform" GH board. Since, we are using label; we can avoid prefix in issue ticket such that "pipeline:" would not be necessary) FYI too @mmalenic |
Also this should be "platform". Not "pipeline". |
FYI too @reisingerf @alexiswl @brainstorm |
currently deployed to bastion account and it seems that the account there do not have slack configured in the AWS Chatbot. I'm happy to configure this, unless I am missing permission from slack? @victorskl @reisingerf |
(note to self) This is on the basis of such that still using our exisiting AWS ChatBot Slack notification infrastructure. As this is still on bastion account. |
add pipeline notification to slack for failed/successful deployment
not critical as now is in dev mode, but might be useful to know if the pipeline is failing
The text was updated successfully, but these errors were encountered: