BuildStatusTrafficLight - Revision history

Bertrik Sikken: /* Status */

2019-01-07T17:54:16Z

Status

← Older revision		Revision as of 17:54, 7 January 2019
Line 23:		Line 23:
	2018-11-18 Soldered new, brighter LEDs into it and connected the ESP8266, no sound yet		2018-11-18 Soldered new, brighter LEDs into it and connected the ESP8266, no sound yet
	2018-11-02 Played with ESP8266 software, particular playing audio using the 1-transistor-circuit		2018-11-02 Played with ESP8266 software, particular playing audio using the 1-transistor-circuit
	2018-10-30 Received ~~that~~ hardware, opened it up etc.		2018-10-30 Received the hardware, opened it up etc.

	Future, things I would do better next time:		Future, things I would do better next time:

Bertrik Sikken: /* Status */

2018-11-26T12:22:03Z

Status

← Older revision		Revision as of 12:22, 26 November 2018
Line 28:		Line 28:
	* configure LEDs for common anode, so the ESP8266 sinks current instead of sourcing it		* configure LEDs for common anode, so the ESP8266 sinks current instead of sourcing it
	* rethink audio, the audio using ESP8266Audio library uses pin Rx, making serial comms impossible, perhaps just use PWM?		* rethink audio, the audio using ESP8266Audio library uses pin Rx, making serial comms impossible, perhaps just use PWM?
	* perhaps just remove the WiFi network again, WifiManager blocks startup until a WiFi connection is established. We don't need WiFi if we connect over serial port.

	== Hardware ==		== Hardware ==

Bertrik Sikken: /* Getting build status */

2018-11-26T12:21:30Z

Getting build status

← Older revision		Revision as of 12:21, 26 November 2018
Line 58:		Line 58:
	where jobname is the name of your build job.		where jobname is the name of your build job.
	Then look for the value of the "result" field at the top level of the JSON, it can take on the following values:		Then look for the value of the "result" field at the top level of the JSON, it can take on the following values:
	* "FAILURE"		* "FAILURE" mapped to red light
	* "UNSTABLE"		* "UNSTABLE" mapped to yellow light
	* "SUCCESS"		* "SUCCESS" mapped to green light
	* null, in case a build is still in progress		* null, in case a build is still in progress, mapped to yellow flashing

	== External links ==		== External links ==
	* [https://wiki.jenkins.io/display/JENKINS/Traffic+Light+Plugin Jenkins traffic light plugin] seems to have the wrong kind of interface, designed to directly drive a bunch of wireless 230V sockets instead of just sending the information like I need		* [https://wiki.jenkins.io/display/JENKINS/Traffic+Light+Plugin Jenkins traffic light plugin] seems to have the wrong kind of interface, designed to directly drive a bunch of wireless 230V sockets instead of just sending the information like I need
	* [https://jobs.zalando.com/tech/blog/signalling-your-jenkins-build-status-with-a-mini-usb-traffic-light Signalling Your Jenkins Build Status with a Mini USB Traffic Light]		* [https://jobs.zalando.com/tech/blog/signalling-your-jenkins-build-status-with-a-mini-usb-traffic-light Signalling Your Jenkins Build Status with a Mini USB Traffic Light]

Bertrik Sikken at 16:42, 23 November 2018

2018-11-23T16:42:44Z

← Older revision		Revision as of 16:42, 23 November 2018
Line 42:		Line 42:

	The toy traffic light features a built-in speaker. I haven't put in a sound circuit yet.		The toy traffic light features a built-in speaker. I haven't put in a sound circuit yet.
	Usage of the ESP8266Audio library in software is problematic because this library sends audio over pin Rx, making serial communication ~~impossible~~.		Usage of the ESP8266Audio library in software is problematic because this library sends audio over pin Rx, making serial communication difficult.

	== Software ==		== Software ==
	Source code can be found [https://github.com/bertrik/BuildStatusLight on github].		Source code can be found [https://github.com/bertrik/BuildStatusLight on github].

	It is written in C/C++ for Arduino for quick and easy development ~~using existing libraries, like WifiManager, PubSubClient~~.		It is written in C/C++ for Arduino for quick and easy development.

	The ~~initial plan is to simply listen to an MQTT stream.~~		The traffic light listens on the serial port to receive commands (like 'set 1'),
	~~Another plan is to listen~~ on the serial port ~~and~~ receive commands ~~from there.~~		A python script running on a PC inside the LAN script polls the Jenkins server over ethernet.
	A python script running on a PC inside the LAN script polls the Jenkins server over ethernet ~~and sends a command to the traffic light over serial~~.

	=== Getting build status ===		=== Getting build status ===

	To get the Jenkins build state, poll the following URL		To get the Jenkins build state, poll the following URL to receive JSON status data
	http://jenkins/job/jobname/lastBuild/api/json		http://jenkins/job/jobname/lastBuild/api/json
	where jobname is the name of your build job.		where jobname is the name of your build job.
Line 62:		Line 61:
	* "UNSTABLE"		* "UNSTABLE"
	* "SUCCESS"		* "SUCCESS"
	* null, in case a build is in progress		* null, in case a build is still in progress

	== External links ==		== External links ==
	* [https://wiki.jenkins.io/display/JENKINS/Traffic+Light+Plugin Jenkins traffic light plugin] seems to have the wrong kind of interface, designed to directly drive a bunch of wireless 230V sockets instead of just sending the information like I need		* [https://wiki.jenkins.io/display/JENKINS/Traffic+Light+Plugin Jenkins traffic light plugin] seems to have the wrong kind of interface, designed to directly drive a bunch of wireless 230V sockets instead of just sending the information like I need
	* [https://jobs.zalando.com/tech/blog/signalling-your-jenkins-build-status-with-a-mini-usb-traffic-light Signalling Your Jenkins Build Status with a Mini USB Traffic Light]		* [https://jobs.zalando.com/tech/blog/signalling-your-jenkins-build-status-with-a-mini-usb-traffic-light Signalling Your Jenkins Build Status with a Mini USB Traffic Light]

Bertrik Sikken: /* Hardware */

2018-11-22T09:48:02Z

Hardware

← Older revision		Revision as of 09:48, 22 November 2018
Line 31:		Line 31:

	== Hardware ==		== Hardware ==
	I use an ESP8266 (Wemos D1 mini) along with a modified toy traffic light ~~(see below)~~.		I use an ESP8266 (Wemos D1 mini) along with a [https://aliexpress.com/item/verkeerslicht/32836170176.html modified toy traffic light].

	~~I'm using [https://aliexpress.com/item/verkeerslicht/32836170176.html this~~ toy traffic light~~], modified for use with the ESP8266.~~		The toy traffic light lights the lanterns in order, speaking some Chinese for each lantern.
	It lights the lanterns in order, speaking some Chinese for each lantern.
	The lanterns are basically white LEDs behind a colored piece of transparent plastic.		The lanterns are basically white LEDs behind a colored piece of transparent plastic.

	~~I removed the original circuit (8-pin chip).~~
	I replaced the white LEDs with high-brightness coloured ones (red, orange, green).		I replaced the white LEDs with high-brightness coloured ones (red, orange, green).
	~~The~~ ESP8266 can ~~officially~~ source about 12 mA and sink about 20 mA of current,		I removed the original circuit (8-pin chip) and put in an ESP8266 to accept commands and control the LEDs.
			It can source about 12 mA and sink about 20 mA of current,
	I'm using a single 150 ohm resistor in the common ground wire of the LEDs (couldn't find a 100 ohm resistor at the space ...)		I'm using a single 150 ohm resistor in the common ground wire of the LEDs (couldn't find a 100 ohm resistor at the space ...)
	~~It would be better to actually put it in a common Vcc wire, because the ESP8266 can more easily sink current than it can source it.~~

	I haven't put in ~~the~~ sound circuit yet.		The toy traffic light features a built-in speaker. I haven't put in a sound circuit yet.
	Usage of the ESP8266Audio library in software is problematic because this library sends audio over pin Rx, making serial communication impossible.		Usage of the ESP8266Audio library in software is problematic because this library sends audio over pin Rx, making serial communication impossible.

Bertrik Sikken: /* Status */

2018-11-22T09:44:25Z

Status

← Older revision		Revision as of 09:44, 22 November 2018
Line 28:		Line 28:
	* configure LEDs for common anode, so the ESP8266 sinks current instead of sourcing it		* configure LEDs for common anode, so the ESP8266 sinks current instead of sourcing it
	* rethink audio, the audio using ESP8266Audio library uses pin Rx, making serial comms impossible, perhaps just use PWM?		* rethink audio, the audio using ESP8266Audio library uses pin Rx, making serial comms impossible, perhaps just use PWM?
			* perhaps just remove the WiFi network again, WifiManager blocks startup until a WiFi connection is established. We don't need WiFi if we connect over serial port.

	== Hardware ==		== Hardware ==

Bertrik Sikken: /* Getting build status */

2018-11-22T09:42:56Z

Getting build status

← Older revision		Revision as of 09:42, 22 November 2018
Line 59:		Line 59:
	http://jenkins/job/jobname/lastBuild/api/json		http://jenkins/job/jobname/lastBuild/api/json
	where jobname is the name of your build job.		where jobname is the name of your build job.
	Then look for the "result" field at the top level of the JSON, it can take on the following values:		Then look for the value of the "result" field at the top level of the JSON, it can take on the following values:
	* "FAILURE"		* "FAILURE"
	* "UNSTABLE"		* "UNSTABLE"

Bertrik Sikken: /* Getting build status */

2018-11-22T09:42:36Z

Getting build status

← Older revision		Revision as of 09:42, 22 November 2018
Line 58:		Line 58:
	To get the Jenkins build state, poll the following URL		To get the Jenkins build state, poll the following URL
	http://jenkins/job/jobname/lastBuild/api/json		http://jenkins/job/jobname/lastBuild/api/json
	where jobname is the name of your build job		where jobname is the name of your build job.
	~~and then~~ look for the "result" field at the top level of the JSON, it can take on the following values:		Then look for the "result" field at the top level of the JSON, it can take on the following values:
	* "FAILURE"		* "FAILURE"
	* "UNSTABLE"		* "UNSTABLE"

Bertrik Sikken: /* Getting build status */

2018-11-22T09:42:18Z

Getting build status

← Older revision		Revision as of 09:42, 22 November 2018
Line 57:		Line 57:

	To get the Jenkins build state, poll the following URL		To get the Jenkins build state, poll the following URL
	http://jenkins/job/<jobname>/lastBuild/api/json		http://jenkins/job/jobname/lastBuild/api/json
	and then look for the "result" field at the top level of the JSON, it can take on the following values		where jobname is the name of your build job
			and then look for the "result" field at the top level of the JSON, it can take on the following values:
	* "FAILURE"		* "FAILURE"
	* "UNSTABLE"		* "UNSTABLE"

Bertrik Sikken: /* Hardware */

2018-11-22T09:41:37Z

Hardware

← Older revision		Revision as of 09:41, 22 November 2018
Line 42:		Line 42:
	It would be better to actually put it in a common Vcc wire, because the ESP8266 can more easily sink current than it can source it.		It would be better to actually put it in a common Vcc wire, because the ESP8266 can more easily sink current than it can source it.

	I haven't put in the sound circuit yet~~, that would be on the RX pin along with usage~~ of the ESP8266Audio library in software ~~and the 1-transistor driving circuit~~.		I haven't put in the sound circuit yet.
			Usage of the ESP8266Audio library in software is problematic because this library sends audio over pin Rx, making serial communication impossible.

	== Software ==		== Software ==