How to get Thoughtworks Go.CD to trigger pipelines quicker

[Muhammad Rehan Saeed]

Go pipelines can sometimes take an age to start after a Git commit and push. Is there a setting or way to get it to pick up changes quicker?

[Ivan Moore]

Hi,

If you are using something like bitbucket or github, you can set up a "web hook" (in bitbucket or github) to post JSON to a web app when a repository is pushed to. We have written a web app which parses the JSON to find out which repository has changed and trigger the appropriate pipelines in GoCD (using a POST to /go/api/pipelines/<pipeline-name>/schedule). Our code works out which pipelines to trigger by using gomatic https://github.com/SpringerSBM/gomatic to find out which pipelines specify the git repository that just got pushed to.

This requires writing some code. Maybe someone else has done an open-source version of this sort of thing?

It isn't a lot of code - I'll see whether we can open source what we've done (but no promises).

It is a real pity GoCD doesn't provide handling of "web hooks" itself.

I haven't searched - is there a feature request for this already?

Ivan

On 3 March 2016 at 17:25, Muhammad Rehan Saeed <rehan...@gmail.com> wrote:

Go pipelines can sometimes take an age to start after a Git commit and push. Is there a setting or way to get it to pick up changes quicker?

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Muhammad Rehan Saeed]

I was hoping there was some simple configuration setting which would reduce a polling interval etc. What you have built sounds amazing and really should be built into Go.CD itself. Myself and the community I'm sure would really appreciate open sourcing of your code.

[Ketan Padegaonkar]

Have you tried this?