Creating a radiator

Paul Hammant edited this page Jun 5, 2017 · 6 revisions

Note: For all below, step names can have spaces in and be any case (as long as you're consistent) in using that in the update cycle, it will all work. Many will chose one-character or numerical codes for the step names and expand them on the browser side.

A radiator that anyone anywhere with the URL can see

Run this command for a new radiator:

$ curl -X POST -F 'stepNames=<FirstStep>,<SecondStep>,<etc>' \

Look at the response that comes back and note the 'radiator code' (code). It will be something like dca82kmq5m7skgt8ad. Also, note the 'secret' which is similar but slightly shorter (that one only the build engineers need to know).

A radiator that is locked down to certain TCP/IP addresses

If you know all your egress IP addresses and want to restrict updating and viewing of your radiator to those IP addresses, then add one more param:

$ curl -X POST -F 'stepNames=<FirstStep>,<SecondStep>,<etc>' \
    -F 'ips=,'

If you are mounting your SmartTV or FireStick in the guest Wi-Fi network, you will to first work out what the egress IP addresses that network uses. Google for 'what is my IP address' on each TV. You'll also need to know the the egress IP addresses of the nodes in the CI infrastructure that would update builds and steps. The radiator, on creation, will be locked to those IP addresses. Assuming you specified them with the -F param above.

You can't change the egress IP addresses after the creation of the radiator - just create a new radiator.

Don't worry you can change the restricted IP addresses later too.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.