Skip to content

Instantly share code, notes, and snippets.

@isurusndr
Created December 26, 2017 11:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save isurusndr/88b4b5ae6367fe73464523894183abc1 to your computer and use it in GitHub Desktop.
Save isurusndr/88b4b5ae6367fe73464523894183abc1 to your computer and use it in GitHub Desktop.
// ------------
// Jenkins LED
// ------------
/*-------------
This program will toggle two led lights. Green led at D0 will remain flashing when turned on.
It wil blink red led at D1 on and off every second.
-------------*/
// First, we're going to make some variables.
// This is our "shorthand" that we'll use throughout the program:
int ledgreen = D0; // Instead of writing D0 over and over again, we'll write ledgreen
int ledred = D1; //led red
bool success = true; //variable to hold whether Jenkins build scucess or not
int ledToggle(String command);
// Having declared these variables, let's move on to the setup function.
// The setup function is a standard part of any microcontroller program.
// It runs only once when the device boots up or is reset.
void setup() {
// We are going to tell our device that D0 and D1 (which we named ledgreen and ledred respectively) are going to be output
// (That means that we will be sending voltage to them, rather than monitoring voltage that comes from them)
// It's important you do this here, inside the setup() function rather than outside it or in the loop function.
pinMode(ledgreen, OUTPUT);
pinMode(ledred, OUTPUT);
Particle.function("toggle", ledToggle);
//At the setup we will light up the green led
if(success){
digitalWrite(ledgreen, HIGH);
}
}
// Next we have the loop function, the other essential part of a microcontroller program.
// This routine gets repeated over and over, as quickly as possible and as many times as possible, after the setup function is called.
// Note: Code that blocks for too long (like more than 5 seconds), can make weird things happen (like dropping the network connection). The built-in delay function shown below safely interleaves required background activity, so arbitrarily long delays can safely be done if you need them.
void loop() {
//blink the red led if status is set as failed
if(!success)
{
digitalWrite(ledred, HIGH);
delay(1000);
digitalWrite(ledred, LOW);
delay(1000);
}
}
//Led toggle function we expose to api.particle.io
int ledToggle(String command) {
if (command == "red") {
digitalWrite(ledgreen, LOW);
digitalWrite(ledred, HIGH);
success = false;
return 1;
}
else if (command =="green") {
digitalWrite(ledgreen, HIGH);
digitalWrite(ledred, LOW);
success = true;
return 0;
}
return -1;
}
@echo off
setlocal
REM We use curl command line tool to send http requests. Replace Jenkins url with the base url to jenkins
REM We query Jenkins json api to check the status of all jenkins jobs. Result is stored into a temp file
curl --silent %JENKINS_URL%api/json>c:\temp.txt
set /p string = < c:\temp.txt
REM See if word 'red' is there in the json api result.
set SubString1=red
find /c "red" c:\temp.txt
if not errorlevel 1 goto found
REM delete the temp file and call toggle function in api.particle.io
REM set PHOTON_DEVICE_ID and PHOTON_ACCESS_TOKEN with your photon device id and access token
REM case all green, we send argument value 'green' into the particle function
del c:\temp.txt
curl https://api.particle.io/v1/devices/%PHOTON_DEVICE_ID%/toggle \ -d arg="green" -d access_token=%PHOTON_ACCESS_TOKEN% -k
goto :eof
:found
echo At least one SubString was found within "%string%".
del c:\test.txt
curl https://api.particle.io/v1/devices/%PHOTON_DEVICE_ID%/toggle \ -d arg="red" -d access_token=%PHOTON_ACCESS_TOKEN% -k
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment