search

brettswift / BuildBlink

using ThingM(.com)'s Blink(1) product, as a build light to notify you of your Continuous Integration Builds.
7 stars 2 forks source link

Expanding BuildBlink #9

Open cgorshing opened 7 years ago

cgorshing commented 7 years ago

I'd like to expand upon BuildBlink a bit more and would love to chat about how we can work together. I've added in Jenkins, ConcourseCI, CircleCI and merged Greg Stewart's Codeship.

https://github.com/cgorshing/BuildBlink

brettswift commented 7 years ago

I just pulled my blink light out of a drawer last week! I haven't been using it much but was recently thinking of reviving this. I didn't notice there was activity on these forks.

Thanks for adding all this support. I'd like to start using my lights again. I'll have to dust it off and get some builds running. Jenkins is good to see - I'm using both it and teamcity these days.

I'm curious to hear what ideas you have for this codebase. I see a ticket about multiple blink support, which is something I was thinking about initially.. I have two of these lights.

cgorshing commented 7 years ago

Other than adding in more support for build servers, I'm also wanting to add in support for other devices. A novation launchpad, and I've picked up a Google Chromecast device as well that I'd like to get working. There are other devices too, but I wanted to start off with these first.

I'm also thinking about having a "server" portion hosted on the cloud that the build servers could notify when builds are successful, this will help get rid of polling all the time as well as possibly keep people from having a VPN connection open to their internal network to check on the status of a build.

brettswift commented 7 years ago

That novation launchpad is quite the little toy. Chromecast is an interesting idea. I don't know much about the API's if you can push content directly or if your thought was to run a local web server and mirror it to the chrome cast. Either way - good ideas.

I've been working with AWS a bit lately, so running this against code build / code pipeline could be interesting.

Do you have any thoughts on how you wanted to move forward with this? I'm pretty happy with anything - just glad to see the revival of build blink!

I'd like to dust off my node.js cobwebs and work on this a little bit. You definitely seem to have a lot of momentum here.

cgorshing commented 7 years ago

For more immediate items, I've been trying to remove some duplication and will be reworking the BuildActivity's into a single data model.

Error handling is now beginning to be high on my list too. If someone tries this out, I'm wanting them to have something to go off of. I'm also wanting to make sure this fails silently, stays up and running, and then just tries again later (network outage, USB issue ...etc). I was thinking about having a color set for this (non-blinking) just to give some feedback that it is still working but not able to connect. (Of course, assuming we can still communicate to the device).

But now that there is a few servers supported. I'd like to rethink the configuration of the project too. Maybe work on the "helper" in constructing the config file. I've pretty much neglected that.

A big help is going to be just running this against your build servers and seeing what issues you find.

brettswift commented 7 years ago

Sure, I can help with that. It'd be nice to get some kind of automated release stuff set up. I could get something going with codeship to release new npm's.