{"action":"created","issue":{"url":"https://api.github.com/repos/apache/spark/issues/5093","labels_url":"https://api.github.com/repos/apache/spark/issues/5093/labels{/name}","comments_url":"https://api.github.com/repos/apache/spark/issues/5093/comments","events_url":"https://api.github.com/repos/apache/spark/issues/5093/events","html_url":"https://github.com/apache/spark/pull/5093","id":63093225,"number":5093,"title":"[SPARK-4123][Project Infra][WIP]: Show new dependencies added in pull requests","user":{"login":"brennonyork","id":2230193,"avatar_url":"https://avatars.githubusercontent.com/u/2230193?v=3","gravatar_id":"","url":"https://api.github.com/users/brennonyork","html_url":"https://github.com/brennonyork","followers_url":"https://api.github.com/users/brennonyork/followers","following_url":"https://api.github.com/users/brennonyork/following{/other_user}","gists_url":"https://api.github.com/users/brennonyork/gists{/gist_id}","starred_url":"https://api.github.com/users/brennonyork/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brennonyork/subscriptions","organizations_url":"https://api.github.com/users/brennonyork/orgs","repos_url":"https://api.github.com/users/brennonyork/repos","events_url":"https://api.github.com/users/brennonyork/events{/privacy}","received_events_url":"https://api.github.com/users/brennonyork/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":98,"created_at":"2015-03-19T21:22:03Z","updated_at":"2015-03-26T22:59:19Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/apache/spark/pulls/5093","html_url":"https://github.com/apache/spark/pull/5093","diff_url":"https://github.com/apache/spark/pull/5093.diff","patch_url":"https://github.com/apache/spark/pull/5093.patch"},"body":"Starting work on this, but need to find a way to ensure that, after doing a checkout from `apache/master`, we can successfully return to the current checkout. I believe that `git rev-parse HEAD` will get me what I want, but pushing this PR up to test what the Jenkins boxes are seeing."},"comment":{"url":"https://api.github.com/repos/apache/spark/issues/comments/86747670","html_url":"https://github.com/apache/spark/pull/5093#issuecomment-86747670","issue_url":"https://api.github.com/repos/apache/spark/issues/5093","id":86747670,"user":{"login":"brennonyork","id":2230193,"avatar_url":"https://avatars.githubusercontent.com/u/2230193?v=3","gravatar_id":"","url":"https://api.github.com/users/brennonyork","html_url":"https://github.com/brennonyork","followers_url":"https://api.github.com/users/brennonyork/followers","following_url":"https://api.github.com/users/brennonyork/following{/other_user}","gists_url":"https://api.github.com/users/brennonyork/gists{/gist_id}","starred_url":"https://api.github.com/users/brennonyork/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brennonyork/subscriptions","organizations_url":"https://api.github.com/users/brennonyork/orgs","repos_url":"https://api.github.com/users/brennonyork/repos","events_url":"https://api.github.com/users/brennonyork/events{/privacy}","received_events_url":"https://api.github.com/users/brennonyork/received_events","type":"User","site_admin":false},"created_at":"2015-03-26T22:59:19Z","updated_at":"2015-03-26T22:59:19Z","body":"/cc @pwendell @srowen @nchammas \r\n\r\nAll complete. You can check out build 29250 up a few to get what the output would be like if a new dependency were added. One issue which I'd love to get some opinion on...\r\n\r\nRight now the initial post message to Github (i.e. the \"Test build started + patch merges cleanly\") will take up to 20 minutes to post **if** any `pom.xml` files were changed because it will then run and build both the current PR plus the master branch. This is purely because the \"This patch merges cleanly\" output is from a `pr_test` and runs in the core test loop. The easiest option to reflect the original way things have been posted would be to move the `pr_merge_ability` test out of the main test loop and have it execute independently. The other option would be to merely post the \"Test build started at ...\" message and remove the \"merges cleanly\" portion to be posted with in the post-test message.\r\n\r\nI'll admit I'm more in favor of the latter option as I think it keeps things clean as well as the fact that \"merges cleanly\" is slightly ambiguous given that Github reports on this as well. Thoughts? Whichever way we go I can get that final change up and then I'd say this is ready for review into master."}}