Currently the wdqs-frontend docker image builds from master, but only when build is manually triggered, or a new commit is made to wikibase-docker wmde git repo.
NEW IDEA
Use Blubber...
Do something after using blubber..
OLD IDEA
Instead some jenkins / github hook should hit the travis API / trigger a new build
As this requires a travis token it might be an idea to use a specific account for it that only has access to the wikibase-docker repo under the wmde org.
We have such a user, https://github.com/WikidataBuilder, the question is, who still has the password?
Possible solution
Triggering builds with the API: https://docs.travis-ci.com/user/triggering-build
Webhooks could also work but they would require some extra service to look at the webhooks and determine when the merge actually happened on master...
We could look into a gerrit plugin (as in T87768#3958112)
using the API...
We could create a tiny jenkins job triggering the travis API
The jenkins job could be small and generic, triggering the master build of the given github repo on travis.
Possible ENV vars for the image:
- AUTH_HEADER (secret token)
- REPO (example wmde/wikibase-docker)
This will require a travis user token for the requests..
We could also create a small travis job on the GUI repo... https://github.com/wikimedia/wikidata-query-gui triggering the same API request..