{"action":"created","issue":{"url":"https://api.github.com/repos/conda/conda-build/issues/2017","repository_url":"https://api.github.com/repos/conda/conda-build","labels_url":"https://api.github.com/repos/conda/conda-build/issues/2017/labels{/name}","comments_url":"https://api.github.com/repos/conda/conda-build/issues/2017/comments","events_url":"https://api.github.com/repos/conda/conda-build/issues/2017/events","html_url":"https://github.com/conda/conda-build/issues/2017","id":227792227,"number":2017,"title":"Parallel build execution","user":{"login":"msarahan","id":38393,"avatar_url":"https://avatars0.githubusercontent.com/u/38393?v=3","gravatar_id":"","url":"https://api.github.com/users/msarahan","html_url":"https://github.com/msarahan","followers_url":"https://api.github.com/users/msarahan/followers","following_url":"https://api.github.com/users/msarahan/following{/other_user}","gists_url":"https://api.github.com/users/msarahan/gists{/gist_id}","starred_url":"https://api.github.com/users/msarahan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msarahan/subscriptions","organizations_url":"https://api.github.com/users/msarahan/orgs","repos_url":"https://api.github.com/users/msarahan/repos","events_url":"https://api.github.com/users/msarahan/events{/privacy}","received_events_url":"https://api.github.com/users/msarahan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-05-10T19:55:10Z","updated_at":"2017-05-10T20:23:07Z","closed_at":null,"body":"@isuruf asked in a conda-forge meeting today about parallel execution of multiple builds.\r\n\r\nI'm concerned about potential resource overconsumption when multiple builds try to use all of the CPUs on a system.  Otherwise, I have no problem with the idea.  I think it will require proper expression of the build tree as a DAG (rather than its current crappy while loop form), and then it's just a question of having an intelligent job execution framework.  This is a reasonably large project.  If anyone would like to undertake it, I'd be happy for this to go into conda-build.  However, Continuum's needs in this area are met by the Concourse build system (https://github.com/conda/conda-concourse-ci), so I can't justify spending time on this myself."},"comment":{"url":"https://api.github.com/repos/conda/conda-build/issues/comments/300601523","html_url":"https://github.com/conda/conda-build/issues/2017#issuecomment-300601523","issue_url":"https://api.github.com/repos/conda/conda-build/issues/2017","id":300601523,"user":{"login":"msarahan","id":38393,"avatar_url":"https://avatars0.githubusercontent.com/u/38393?v=3","gravatar_id":"","url":"https://api.github.com/users/msarahan","html_url":"https://github.com/msarahan","followers_url":"https://api.github.com/users/msarahan/followers","following_url":"https://api.github.com/users/msarahan/following{/other_user}","gists_url":"https://api.github.com/users/msarahan/gists{/gist_id}","starred_url":"https://api.github.com/users/msarahan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msarahan/subscriptions","organizations_url":"https://api.github.com/users/msarahan/orgs","repos_url":"https://api.github.com/users/msarahan/repos","events_url":"https://api.github.com/users/msarahan/events{/privacy}","received_events_url":"https://api.github.com/users/msarahan/received_events","type":"User","site_admin":false},"created_at":"2017-05-10T20:23:07Z","updated_at":"2017-05-10T20:23:07Z","body":"That scheduling is exactly what I don't want to do myself for conda-build.  Scheduling is a problem for other libraries - perhaps someone could work dask's scheduler into conda-build.\r\n\r\nIt is just an extraordinarily hairy problem.  Right now, people can run more than one conda-build process at a time.  Under your proposal, there would need to be only one, or at least one central job dispatch server."}}
{"actor":{"display_login":"msarahan"}}