{"action":"created","issue":{"url":"https://api.github.com/repos/ipfs/infrastructure/issues/9","labels_url":"https://api.github.com/repos/ipfs/infrastructure/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/ipfs/infrastructure/issues/9/comments","events_url":"https://api.github.com/repos/ipfs/infrastructure/issues/9/events","html_url":"https://github.com/ipfs/infrastructure/issues/9","id":65609414,"number":9,"title":"Move off jenkins","user":{"login":"jbenet","id":138401,"avatar_url":"https://avatars.githubusercontent.com/u/138401?v=3","gravatar_id":"","url":"https://api.github.com/users/jbenet","html_url":"https://github.com/jbenet","followers_url":"https://api.github.com/users/jbenet/followers","following_url":"https://api.github.com/users/jbenet/following{/other_user}","gists_url":"https://api.github.com/users/jbenet/gists{/gist_id}","starred_url":"https://api.github.com/users/jbenet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbenet/subscriptions","organizations_url":"https://api.github.com/users/jbenet/orgs","repos_url":"https://api.github.com/users/jbenet/repos","events_url":"https://api.github.com/users/jbenet/events{/privacy}","received_events_url":"https://api.github.com/users/jbenet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-04-01T05:36:19Z","updated_at":"2015-04-01T20:25:39Z","closed_at":null,"body":"I've had it with jenkins. it's so painful to work with. I want to move off. It's currently broken-- it isn't building go-ipfs properly.\r\n\r\nI really like golang's build system: http://build.golang.org -- it is just https://github.com/golang/build -- ideally we could run our own version of that, equipped with ipfs to avoid re-downloading things multiple times (i.e. so tests get even faster). This sounds non-trivial to setup... \r\n\r\nSo perhaps in the meantime we could try to use travis for everything we do in jenkins. This may not work, particularly:\r\n- race tests will crawl or may just fail on travis\r\n- not sure if container tests (`3nodetest`) will work.\r\n\r\nThe jenkins tests in question are:\r\n- `test_sharness_expensive` ideally with fuse\r\n- `build_docker_image` to check it works\r\n- `build_all_commits` to check all commits build (probably redundant given `test_all_commits)`\r\n- `test_go`\r\n- `test_3node` requires containers\r\n- `test_go_race` likely to be very slow\r\n- `test_all_commits` runs `make test` on all commits.\r\n- `test_go_integration` runs some integration tests\r\n\r\nI think that -- instead of only testing `make test` on all commits, we should instead:\r\n\r\n- for _every commit_:\r\n  - go test\r\n  - go test race\r\n  - sharness (expensive)\r\n  - build docker image\r\n  - integration tests\r\n\r\nThis _might_ be as simple as making the repo test all these pieces and using travis.\r\n"},"comment":{"url":"https://api.github.com/repos/ipfs/infrastructure/issues/comments/88621108","html_url":"https://github.com/ipfs/infrastructure/issues/9#issuecomment-88621108","issue_url":"https://api.github.com/repos/ipfs/infrastructure/issues/9","id":88621108,"user":{"login":"chriscool","id":208954,"avatar_url":"https://avatars.githubusercontent.com/u/208954?v=3","gravatar_id":"","url":"https://api.github.com/users/chriscool","html_url":"https://github.com/chriscool","followers_url":"https://api.github.com/users/chriscool/followers","following_url":"https://api.github.com/users/chriscool/following{/other_user}","gists_url":"https://api.github.com/users/chriscool/gists{/gist_id}","starred_url":"https://api.github.com/users/chriscool/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chriscool/subscriptions","organizations_url":"https://api.github.com/users/chriscool/orgs","repos_url":"https://api.github.com/users/chriscool/repos","events_url":"https://api.github.com/users/chriscool/events{/privacy}","received_events_url":"https://api.github.com/users/chriscool/received_events","type":"User","site_admin":false},"created_at":"2015-04-01T20:25:39Z","updated_at":"2015-04-01T20:25:39Z","body":"First, yeah it is a good idea to test every commit as much as possible, at least as long as it doesn't take too much time.\r\n\r\nIf Travis works well, it looks like a good idea to do as much as possible using it.\r\n\r\nCan FUSE tests be done on Travis too?\r\n\r\nAs some tests cannot be done on Travis, maybe we can keep Jenkins only for these tests or use something else like http://buildbot.net/.\r\n\r\n\r\n"}}