Travis Slack integration about spark HOT 12 CLOSED

@amotenko - I'm already working on it.. will publish a pull request soon
re-assigning back to me..

from spark.

in #45 I added notification to slack on every build of master

from spark.

continuing to work on it with the staging server

from spark.

basic auto deploy is working on staging, relevant documentation:
https://github.com/Midburn/Spark/blob/master/docs/development/devops.md

from spark.

@amotenko - why did you close it?

from spark.

if I'm not mistaken we got everything , but correct me if I'm wrong

from spark.

I didn't open this issue but AFAIK some points from original description are not done yet:
[] Add all spark devs to sparksystem-alerts (if anyone wants to leave they can)
[] Add #sparksystem-alerts as a default channel for new devs on Slack
[] Nice to have: if you personally broke the build, you get a pm.

we have some limited integration, but I'm not sure what was the original intent

from spark.

I usually let the original reporter (in this case @ripper234) close the issue or at least give him a chance to respons before closing to make sure no idea is left behind..

also, explaining why issue is closed is required in my opinion for correct working flow

from spark.

Thanks @OriHoch.
@amotenko : I agree that in general when closing, an explanation should be mandatory.

However in this case I'm not really a part of the workflow these days, so I have no objection to closing if @amotenko wants. Closing it for now.

from spark.

@ripper234 , @OriHoch I know it sounds retarded but I wasn't aware of this aspect of open source project etiquette, so thank you for pointing this out.
Regarding the bullets above, I may be biased and please tell me if you feel that's wrong but I think that 'noise' should always be opt-in and not opt-out, especially for newcomers.
Regarding the last bullet, today with Travis we can't push a branch if it's breaking a build, so is this scenario possible?

from spark.

from spark.

@ArtyomKa - spark's travis runs on pull requests so you don't have to configure travis for each fork
you just have to open a pull request and mark it as in progress so it won't be merged..

from spark.