Trigger build if another repository updates

[ojii]

I want the build trigger to fire for project pymaging-png both when its own repository updates, as well as when the dependency project pymaging updates. It's important that this is configured in the pymaging-png package, so new packages don't have to change configuration in the core package.

The use case here is to have a build matrix of pymaging-png building against the latest stable version of pymaging, and the master branch of it. Like this, finding incompatibilities introduced by changes in either repo would be spotted more easily.

[michaelklishin]

It is a bit unrealistic to reliably implement this for 10+ supported languages, and Python alone will be challenging with its current packaging system. Sorry, no plans to do this.

[ojii]

How does this depend on the packaging? Let the travis.yml handle this. All I want is for the "sub" projects (or whatever you want to call them) to trigger to build. pymaging-png should be able to define "also build after pymaging builds". It's what I do in Jenkins right now and it's wonderful.

[michaelklishin]

No. Too much complexity, too few projects need this. Please use Jenkins, it was created for cases like this and it works very well.

[ojii]

I don't know about your first reason, I highly disagree with the second reason. Ah well, too bad, back to Jenkins.

[motiejus]

I was looking for something probably similar. Here is my situation:

• erlualib_examples depends on erlualib very heavily (real-world examples what you can do with erlualib).

I want to test erlualib_examples every time erlualib is updated. This is one of the ways to check if library change did not introduce incompatible changes in the examples repository.

This could be easily achieved using webhooks, since travis already supports them. The only thing we need now is a "public url", which we could POST when we want to trigger a build. See my hypothetical example:

erlualib/.travis.yml:

notifications:
  webhooks:
    urls:
      - http://hooks.travis-ci.org/erlualib_examples/please_build/master

Since you already have a mechanism to trigger a build, in theory we could use it. However, we need to provide token (as http auth) and some post data (travis_url and payload). Now webhooks do not allow neither http auth (and it shouldn't, for obvious reasons), nor custom http post parameters.

A way to implement this feature would be to "open up" the listener service, so it would be possible to trigger a build from a webhook.

[ojii]

another use case: any Django app. I'd love to automatically trigger a build on my Django apps (the stuff with getting the latest Django version is already in the matrix build config, so don't worry about that, packaging or anything) to see if they still work with the latest in development Django version.

[themihai]

We need this as well. What's so complex to add a hook which would trigger another build after success ?
We host all the templates on a common repository. It would make sense to rebuild when a dependency (e.g templates repository) is updated.

[knowledgewarrior]

I'd like this feature too. I want to be able to run a smoke test against production after a deployment of our application code.

[alwinmark]

same here. A webtrigger would be awesome

[lkrnac]

+1

[moizjv]

any updates ?