Yes!
For Travis and Ruby, there is the travis-blink1 ruby gem.
For GitLab CI, here’s how to Integrate GitLab CI with blink(1) on Cloudpipes.
For TeamCity, there’s BuildBlink written in Node by @brettswift.
For Python, see “Continuous Integration with python and blink(1)” by Michael Davies.
Also, just about any CI system will have the ability to execute scripts. In this case, you can have it run a properly formatted blink1-tool command.
Yes! If your phone can load a web page it can control blink(1). The blink(1) service provided by the Blink1Control app on your computer can appear as a web app for your phone or any other network enabled device.
Short answer: use “blink1control-tool” instead of “blink1-tool”!
Only one program can access the blink(1) device at a time. If running the Blink1Control app, you can either use the Blink1Control HTTP REST API or use “blink1control-tool”, a command-line program that has the same command-line switches as “blink1-tool” but does so
You can find “blink1control-tool” in the blink1-tool releases page. (You may need to scroll down, it doesn’t need updating as often so it may be on an older releases section)
In general, the blink(1) low-level APIs are compiled with GCC and Makefiles.
- Check out the code from https://github.com/thingm/blink1-tool/
- Install compilation prerequisites as described in the READM
make
blink1-tool is written to work on any platform that libusb is supported on. We regularly provide compiled versions for:
- Mac 10.6+
- Win XP+
- Linux Ubuntu
- Raspberry Pi
- Beaglebone
It is very easy to compile for your own platform and we have seen compiled versions created on:
- OpenWrt
- Arduino Yun
The blink(1) mk3 is visually almost identical to the mk2. It comes in a smaller box but comes with the same 5ft USB extension cable.
Internally, the mk3 uses a new USB chip that is more powerful and allows for firmware upgrades over USB.
You read more about the differences on our blink(1) variations page at https://blink1.thingm.com/blink1-variations/