{"action":"created","issue":{"url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/issues/573","repository_url":"https://api.github.com/repos/jenkinsci/blueocean-plugin","labels_url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/issues/573/labels{/name}","comments_url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/issues/573/comments","events_url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/issues/573/events","html_url":"https://github.com/jenkinsci/blueocean-plugin/pull/573","id":185550641,"number":573,"title":"JENKINS-38847# API to create multi-branch pipeline for given SCM","user":{"login":"vivek","id":38139,"avatar_url":"https://avatars.githubusercontent.com/u/38139?v=3","gravatar_id":"","url":"https://api.github.com/users/vivek","html_url":"https://github.com/vivek","followers_url":"https://api.github.com/users/vivek/followers","following_url":"https://api.github.com/users/vivek/following{/other_user}","gists_url":"https://api.github.com/users/vivek/gists{/gist_id}","starred_url":"https://api.github.com/users/vivek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vivek/subscriptions","organizations_url":"https://api.github.com/users/vivek/orgs","repos_url":"https://api.github.com/users/vivek/repos","events_url":"https://api.github.com/users/vivek/events{/privacy}","received_events_url":"https://api.github.com/users/vivek/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/labels/work-in-progress","name":"work-in-progress","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-10-27T01:19:13Z","updated_at":"2016-10-27T16:09:44Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/pulls/573","html_url":"https://github.com/jenkinsci/blueocean-plugin/pull/573","diff_url":"https://github.com/jenkinsci/blueocean-plugin/pull/573.diff","patch_url":"https://github.com/jenkinsci/blueocean-plugin/pull/573.patch"},"body":"# Description\r\n\r\nSee [JENKINS-38847](https://issues.jenkins-ci.org/browse/JENKINS-38847).\r\n\r\nWork in progress. Following tasks to be completed before review:\r\n[ ] Basic implementation of API to create multi-branch pipeline for given GitHub org\r\n\r\nBasic implementation is in place. If you make this POST request on this PR branch, you will have an organization folder with name cloudbeers created with only one branch PR-demo.\r\n\r\nReason I do not have it marked completed is to probably be able to change request/response format.\r\n\r\n```\r\ncurl -v -u admin:admin -H 'Content-Type: application/json' http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/  -d '{\r\n  \"name\" : \"cloudbeers\",\r\n  \"scmProviderId\" : \"github\",\r\n  \"credentialId\" : \"...\", \r\n  \"repos\" : [ \"PR-demo\" ]\r\n}'\r\n```\r\n* Only **name** and **scmProviderId** are required element\r\n* This still needs ironing out few things:\r\n** creation request should be bit more generic so that it works in general with most generic job type\r\n\r\n[ ] Show org's in progress pipeline status \r\n* Return in progress pipelines with status in the response of /pipelines/:orgName/pipelines\r\n\r\n[ ] Implement PUT in the implementation for /pipelines/:orgName/ to update its setting - e.g. to update repos to be scanned\r\n[ ] Testing and test cases\r\n\r\n# Submitter checklist\r\n- [x] Link to JIRA ticket in description, if appropriate.\r\n- [ ] Change is code complete and matches issue description\r\n- [ ] Appropriate unit or acceptance tests or explanation to why this change has no tests\r\n- [ ] Reviewer's manual test instructions provided in PR description. See Reviewer's first task below.\r\n- [ ] Ran Acceptance Test Harness against PR changes.\r\n\r\n# Reviewer checklist\r\n- [ ] Run the changes and verified the change matches the issue description\r\n- [ ] Reviewed the code\r\n- [ ] Verified that the appropriate tests have been written or valid explanation given\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/issues/comments/256691701","html_url":"https://github.com/jenkinsci/blueocean-plugin/pull/573#issuecomment-256691701","issue_url":"https://api.github.com/repos/jenkinsci/blueocean-plugin/issues/573","id":256691701,"user":{"login":"vivek","id":38139,"avatar_url":"https://avatars.githubusercontent.com/u/38139?v=3","gravatar_id":"","url":"https://api.github.com/users/vivek","html_url":"https://github.com/vivek","followers_url":"https://api.github.com/users/vivek/followers","following_url":"https://api.github.com/users/vivek/following{/other_user}","gists_url":"https://api.github.com/users/vivek/gists{/gist_id}","starred_url":"https://api.github.com/users/vivek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vivek/subscriptions","organizations_url":"https://api.github.com/users/vivek/orgs","repos_url":"https://api.github.com/users/vivek/repos","events_url":"https://api.github.com/users/vivek/events{/privacy}","received_events_url":"https://api.github.com/users/vivek/received_events","type":"User","site_admin":false},"created_at":"2016-10-27T16:09:44Z","updated_at":"2016-10-27T16:09:44Z","body":"@michaelneale @i386 Yes we should remove this tight coupling, I will move GitHub specific implementation out in to a separate plugin living as separate plugin (outside of blueocean repo). In terms of user experience for this flow, do we expect this plugin to be separately installed or pulled in by blueocean aggregator? I guess we can decide on this later but something to consider for out of the box experience."}}
{"actor":{"display_login":"vivek"}}