{"action":"created","issue":{"url":"https://api.github.com/repos/ryanhiebert/tox-travis/issues/13","repository_url":"https://api.github.com/repos/ryanhiebert/tox-travis","labels_url":"https://api.github.com/repos/ryanhiebert/tox-travis/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/ryanhiebert/tox-travis/issues/13/comments","events_url":"https://api.github.com/repos/ryanhiebert/tox-travis/issues/13/events","html_url":"https://github.com/ryanhiebert/tox-travis/issues/13","id":152185587,"number":13,"title":"Implement unified results and pipeline joining similar to travis-after-all","user":{"login":"ssbarnea","id":102495,"avatar_url":"https://avatars.githubusercontent.com/u/102495?v=3","gravatar_id":"","url":"https://api.github.com/users/ssbarnea","html_url":"https://github.com/ssbarnea","followers_url":"https://api.github.com/users/ssbarnea/followers","following_url":"https://api.github.com/users/ssbarnea/following{/other_user}","gists_url":"https://api.github.com/users/ssbarnea/gists{/gist_id}","starred_url":"https://api.github.com/users/ssbarnea/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ssbarnea/subscriptions","organizations_url":"https://api.github.com/users/ssbarnea/orgs","repos_url":"https://api.github.com/users/ssbarnea/repos","events_url":"https://api.github.com/users/ssbarnea/events{/privacy}","received_events_url":"https://api.github.com/users/ssbarnea/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-05-01T07:35:30Z","updated_at":"2016-05-02T12:58:20Z","closed_at":null,"body":"Currently the `tox-travis` does not allow us to make a release if ALL travis jobs succeeded. People are probably using the travis-after-all approach on this. \r\n\r\nStill, it would be extremely helpful for any Python projects to integrate this into travis-tox as we do want to be able to consolidate the results of different executions and get a final single build report and do an automatic release if the outcome is positive."},"comment":{"url":"https://api.github.com/repos/ryanhiebert/tox-travis/issues/comments/216228038","html_url":"https://github.com/ryanhiebert/tox-travis/issues/13#issuecomment-216228038","issue_url":"https://api.github.com/repos/ryanhiebert/tox-travis/issues/13","id":216228038,"user":{"login":"ryanhiebert","id":425099,"avatar_url":"https://avatars.githubusercontent.com/u/425099?v=3","gravatar_id":"","url":"https://api.github.com/users/ryanhiebert","html_url":"https://github.com/ryanhiebert","followers_url":"https://api.github.com/users/ryanhiebert/followers","following_url":"https://api.github.com/users/ryanhiebert/following{/other_user}","gists_url":"https://api.github.com/users/ryanhiebert/gists{/gist_id}","starred_url":"https://api.github.com/users/ryanhiebert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryanhiebert/subscriptions","organizations_url":"https://api.github.com/users/ryanhiebert/orgs","repos_url":"https://api.github.com/users/ryanhiebert/repos","events_url":"https://api.github.com/users/ryanhiebert/events{/privacy}","received_events_url":"https://api.github.com/users/ryanhiebert/received_events","type":"User","site_admin":false},"created_at":"2016-05-02T12:58:20Z","updated_at":"2016-05-02T12:58:20Z","body":"This will require including an extra dependency, requests. It's not needed for the current functionality of tox-travis, so it makes me wonder if it should be opt-in to have the extra dependencies needed for this capability. This would be done with a extras require section, so the options for installation are:\r\n\r\n```sh\r\n# The same as it is now, just with more dependencies\r\npip install tox-travis\r\n```\r\n\r\nor\r\n\r\n```\r\n# The extra dependencies are explicitly requested\r\npip install tox-travis[after]\r\n```\r\n\r\nWhich is better?"}}