{"action":"opened","issue":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6278","repository_url":"https://api.github.com/repos/travis-ci/travis-ci","labels_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6278/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6278/comments","events_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6278/events","html_url":"https://github.com/travis-ci/travis-ci/issues/6278","id":164368127,"number":6278,"title":"Make a clear statement about the possibility for running builds locally","user":{"login":"brechtm","id":652887,"avatar_url":"https://avatars.githubusercontent.com/u/652887?v=3","gravatar_id":"","url":"https://api.github.com/users/brechtm","html_url":"https://github.com/brechtm","followers_url":"https://api.github.com/users/brechtm/followers","following_url":"https://api.github.com/users/brechtm/following{/other_user}","gists_url":"https://api.github.com/users/brechtm/gists{/gist_id}","starred_url":"https://api.github.com/users/brechtm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brechtm/subscriptions","organizations_url":"https://api.github.com/users/brechtm/orgs","repos_url":"https://api.github.com/users/brechtm/repos","events_url":"https://api.github.com/users/brechtm/events{/privacy}","received_events_url":"https://api.github.com/users/brechtm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-07T17:47:59Z","updated_at":"2016-07-07T17:47:59Z","closed_at":null,"body":"I've been trying to get the Travis CI builds for my open source project running locally in a Docker image. Having the [Travis Docker images ](https://quay.io/organization/travisci) freely available is already a tremendous help. Thanks for that!\r\n\r\nHowever, I was hoping it would be possible to also automatically run all the builds from a `.travis.yml` configuration. The `travis compile` command (travis-build) seemed like the solution, but this was a disappointment. If multiple Python versions are specified in my `.travis.yml`, the generated build script is not a valid bash script. There are also some [other problems](https://github.com/travis-ci/travis.rb/issues/414) with the generated script.\r\n\r\nNext up, [travis-worker](https://github.com/travis-ci/worker). Because of the fact that its sources are available on GitHub and that it has a nice README with installation instructions, it seemed like I would be able to achieve what I se out to do. But besides installation instructions, there is no documentation whatsoever on how to use travis-worker. I can start it, and then it seems to wait for jobs to be queued. There is no information anywhere to be found on how to send jobs to travis-worker. I'm assuming these jobs are queued by another travis-ci component? Contrary to what the README for travis-worker suggests, I don't think it is realistic to run it on my local machine for debugging purposes.\r\n\r\nIf this is indeed correct, could this simply be stated clearly in your documentation and in the README of travis-worker. Judging from a bunch of StackOverflow posts and travis-ci issues here on GitHub, I believe this might save a lot of people some time."}}
{"actor":{"display_login":"brechtm"}}