Chris Hendrix
Chris Hendrix
Is [exposing your pipeline](http://concourse.ci/fly-expose-pipeline.html) not an available option in this use case?
This is something that would be a wonderful PR to accept. If you're interested, please start by looking at our [Contributing Guide](https://github.com/concourse/concourse/blob/master/CONTRIBUTING.md) I've also attached this to the Help Wanted...
This is something that would be a wonderful PR to accept. If you're interested, please start by looking at our [Contributing Guide](https://github.com/concourse/concourse/blob/master/CONTRIBUTING.md) I've also attached this to the Help Wanted...
@robbruce is this solved by concourse/concourse#1145?
Am I to understand this isn't going to land in any of the `2.x` releases and is being saved for `3.0.0`?
needs concourse/concourse#1027
Is this still broken? @tsaleh Concourse just published a new blog post.
do this please.
So are you proposing that the checks still happen, they just happen when a job they move into get triggered? Because you still need to run a check to figure...
Ok, so just so we're all aware that's still going to spin up check containers, and will still likely bring down your worker. The only benefit you get from that...