{"action":"opened","issue":{"url":"https://api.github.com/repos/Vauxoo/travis2docker/issues/51","repository_url":"https://api.github.com/repos/Vauxoo/travis2docker","labels_url":"https://api.github.com/repos/Vauxoo/travis2docker/issues/51/labels{/name}","comments_url":"https://api.github.com/repos/Vauxoo/travis2docker/issues/51/comments","events_url":"https://api.github.com/repos/Vauxoo/travis2docker/issues/51/events","html_url":"https://github.com/Vauxoo/travis2docker/issues/51","id":149246634,"number":51,"title":"Use github's webhooks to trigger docker builds on hub.docker.com","user":{"login":"LuisAlejandro","id":324683,"avatar_url":"https://avatars.githubusercontent.com/u/324683?v=3","gravatar_id":"","url":"https://api.github.com/users/LuisAlejandro","html_url":"https://github.com/LuisAlejandro","followers_url":"https://api.github.com/users/LuisAlejandro/followers","following_url":"https://api.github.com/users/LuisAlejandro/following{/other_user}","gists_url":"https://api.github.com/users/LuisAlejandro/gists{/gist_id}","starred_url":"https://api.github.com/users/LuisAlejandro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LuisAlejandro/subscriptions","organizations_url":"https://api.github.com/users/LuisAlejandro/orgs","repos_url":"https://api.github.com/users/LuisAlejandro/repos","events_url":"https://api.github.com/users/LuisAlejandro/events{/privacy}","received_events_url":"https://api.github.com/users/LuisAlejandro/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-18T19:20:27Z","updated_at":"2016-04-18T19:20:27Z","closed_at":null,"body":"I really don't know if this issue belongs here, but as this is the tool that generates docker containers for each of our projects, i guess it's the best place.\r\n\r\n**Proposal:**\r\n\r\nUse the webhooks from github to trigger a new build of a docker image hosted in hub.docker.com, each time a dependency of that image is updated with a commit (or merge) in the main branch (currently 8.0).\r\n\r\nFor example, lets say, our \"very_profitable_client\" image has the following odoo dependencies:\r\n\r\n- addons-vauxoo\r\n- odoo-ifrs\r\n- odoo-afrs\r\n\r\nAnd, let's say, \"odoo-ifrs\" gets updated with a new merge. This would trigger an inmediate build on hub.docker.com, which will result in an up-to-date image that then developers would only have to do `docker pull vauxoo/very_profitable_client`.\r\n\r\n**What would be needed?**\r\n\r\nEach of our client images should be uploaded to hub.docker.com (there are paid plans if we want to keep them private). And then each dependency component should be configured on github to trigger the images that depend on them.\r\n\r\nWhat do you think?\r\n@moylop260 @zaoral @nhomar @ruiztulio @osvalr \r\n"}}