This is a common problem we see typically because Igor is not enabled. You can confirm this is true by looking at the Spinnaker Gate API to see if gate is getting any builds at all by executing the following:

curl http://${GATE_HOST}:8084/v2/builds

it should respond with an empty JSON array: []

You would also see in your Igor logs

2017-02-03 22:43:53.143  INFO 1 --- [readScheduler-1] c.n.s.igor.jenkins.JenkinsBuildMonitor   : - Polling cycle started -  
2017-02-03 22:43:53.143  INFO 1 --- [readScheduler-1] c.n.s.igor.jenkins.JenkinsBuildMonitor   : Checking for new builds for jenkins-prod  
2017-02-03 22:43:53.188  INFO 1 --- [readScheduler-1] c.n.s.igor.jenkins.JenkinsBuildMonitor   : finding new builds in jenkins-prod : 150 items  
2017-02-03 22:43:53.197  INFO 1 --- [readScheduler-1] c.n.s.igor.jenkins.JenkinsBuildMonitor   : Took 53ms to retrieve projects (master: jenkins-prod)  

If this is the case you'll want to enable Igor in your spinnaker-local.yml by going adding the following:

services:  
  igor:
    enabled: true

Make sure to restart Armory Spinnaker with the following:

services armory-spinnaker restart

Then curl the gate host again

curl http://${GATE_HOST}:8084/v2/builds

it should respond with your Jenkins host in the array: [jenkins-prod]

You can take a look at the Gate logs to make sure the requests are being sent to Igor:

docker logs -f igor

Feel free to reach out and run