-
Notifications
You must be signed in to change notification settings - Fork 313
Added push notifications when a build fails or finished #125
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
Conversation
Any idea why that build is failing? I trying |
@benbotwin looks like it might be due to wercker using an old version of go:
You could try adding a wercker.yml with a newer version |
apparently wrecker doesn't have any other versions. Also, i'll clean up these commits and make a new PR once I have this figured out |
@benbotwin does |
Nope. @ibash is there a list of wrecker boxes somewhere? I thought it was pulling containers from docker hub, but that doesn't seem to be the case. |
@ibash I got the build working and I squashed all the commits here 😄 . Let me know if there's anything you think would need adding or fixing |
Thanks @benbotwin! There seems to be one test that is not passing, barring that this is good to go! |
@ibash I'm not sure why that failed but it looks all good now :) |
Thank you!! |
Added push notifications when a build fails or finished
It's a lot nicer getting immediate feedback via a push notification when a build finishes. This way you never really need to look at the terminal other than for logs.