telescope
telescope copied to clipboard
Seneca-CDOT
Investigate Slack integrations for failed or successful builds
What would you like to be added:
Let's see what we can do to add some notifications to our #telescope Slack channel. Maybe there are existing tools that we can leverage for this, or maybe we can build our own (possibly as a separate repo).
Why would you like this to be added:
We have a number of situations that would be good to know about when the occur. For example:
- dev or prod go down (e.g., something broke one of the servers)
- dev or prod get deployed (e.g., new build available)
Probably there are other things, but these are the main ones that occur to me.
Research: Github webhooks event: release Making a Slack bot
What I need to find is an event when a build occurs on master, and when it breaks.
A build on the staging/production boxes is done when this function is called: https://github.com/Seneca-CDOT/telescope/blob/master/tools/autodeployment/builds.js#L17-L31
If the code is === 0 then it passed, otherwise it failed, so pseudo-code would be:
if(code !==0) {
slackBot.sendMessage("Build failed...");
}
@sirinoks, what has been your progress related to this? I know that you were researching for any Slack APIs that would let you do this, but I don't know what you concluded with.
@sirinoks, what has been your progress related to this? I know that you were researching for any Slack APIs that would let you do this, but I don't know what you concluded with.
There has been no progress since Feb 15th. I still need to figure out the automation stuff and I haven't looked there.
@sirinoks, what has been your progress related to this? I know that you were researching for any Slack APIs that would let you do this, but I don't know what you concluded with.
There has been no progress since Feb 15th. I still need to figure out the automation stuff and I haven't looked there.
Perhaps you can talk to @DukeManh , I remember he added a Slackbot but it was in the wrong channel so it was removed
Perhaps you can talk to @DukeManh , I remember he added a Slackbot but it was in the wrong channel so it was removed
So, the problem isn't in the slackbot related stuff, but in automation stuff. But I'm pretty sure there is also someone to ask about that. Either way, I have limited time now. I might get to this, but I think I was told to prioritize docs for now. I'm sorry for my inconsistency, I also want to have this done, since it's pretty interesting.
@sirinoks, that's totally fine. In the case you'd prefer to prioritize documentation, we can push the issue to release 3.0. Let me know if you are okay with that.
