Unable to manually start a smoke test in concourse

[mhalbritter]

When scheduling a new build for a smoke test in concourse, it waits for a resource named time-<name-of-the-test>.

I guess this is a side effect of how the "schedule on some random time in the night" is set up.

[wilkinsona]

It works now that time-spring-pulsar-app-test has produced its first version. In other words, this is only a problem when a new smoke test has been added and you want to run it immediately rather than waiting for it to be scheduled. I'm not sure that there's anything that we can (easily) do about that.

[mhalbritter]

Ah, I guess we can live with that.