{"action":"opened","issue":{"url":"https://api.github.com/repos/GitTools/GitVersion/issues/1445","repository_url":"https://api.github.com/repos/GitTools/GitVersion","labels_url":"https://api.github.com/repos/GitTools/GitVersion/issues/1445/labels{/name}","comments_url":"https://api.github.com/repos/GitTools/GitVersion/issues/1445/comments","events_url":"https://api.github.com/repos/GitTools/GitVersion/issues/1445/events","html_url":"https://github.com/GitTools/GitVersion/issues/1445","id":343798883,"node_id":"MDU6SXNzdWUzNDM3OTg4ODM=","number":1445,"title":"Sort out CD","user":{"login":"dazinator","id":3176632,"node_id":"MDQ6VXNlcjMxNzY2MzI=","avatar_url":"https://avatars2.githubusercontent.com/u/3176632?v=4","gravatar_id":"","url":"https://api.github.com/users/dazinator","html_url":"https://github.com/dazinator","followers_url":"https://api.github.com/users/dazinator/followers","following_url":"https://api.github.com/users/dazinator/following{/other_user}","gists_url":"https://api.github.com/users/dazinator/gists{/gist_id}","starred_url":"https://api.github.com/users/dazinator/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dazinator/subscriptions","organizations_url":"https://api.github.com/users/dazinator/orgs","repos_url":"https://api.github.com/users/dazinator/repos","events_url":"https://api.github.com/users/dazinator/events{/privacy}","received_events_url":"https://api.github.com/users/dazinator/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-23T21:16:26Z","updated_at":"2018-07-23T21:16:26Z","closed_at":null,"author_association":"MEMBER","body":"\r\n- Build assets aren't automatically pushed anywhere at present.\r\n- No one wants the burden of manually doing it.\r\n\r\nSo:\r\n\r\nWe need to get our build assets pushed automatically to their respective deployment channels on every commit.\r\n\r\nStable assets (i.e of the back of a stable release) need to be pushed to stable deployment channels (i.e nuget.org etc)\r\n\r\nPre-release assets (everything that isn't a stable release) need to be pushed to unstable deployment channels (i.e appveyor nuget feed or nuget.org as a pre-release etc)\r\n\r\nWe have PR's waiting in the wings, and issues because people can't find the latest packages where they are expecting, and this is because we haven't been able to get a handle on the release process or are too reliant on manual intervention.\r\n\r\nThere appears to [be a cake script for deployments](https://github.com/GitTools/GitVersion/blob/master/deploy.cake#L81)` that does a lot of what we need - perhaps someone could clarify where this fits in to our build process (i.e does appveyor automatically execute it? Does it still work?)\r\n\r\nSee several of the [bottom comments here](https://github.com/GitTools/GitVersion/pull/1432) where we have talked about when deployment should be pushed - TLDR: push stable packages when stable tag is created. Everything else push unstable packages. This project is not currently set up for gitflow and AFAIK there is no intention to transition to that, so right now thoughts are we just issue a stable release by tagging a commit with a stable number.\r\n\r\nThis issue will be done when:\r\n\r\n1. The build process, automatically pushes all of the built artefacts to all necessary deployment channels (stable or unstable), after every commit. \r\n\r\nThe assets we need to be pushing (Please amend this table appropriately) are  as seen [here](https://github.com/GitTools/GitVersion/blob/master/deploy.cake#L81):\r\n\r\n- [ ] NuGetCommandLineBuild --> NuGet.org\r\n- [ ] NuGetRefBuild --> NuGet.org\r\n- [ ] NuGetExeDotNetCoreBuild --> NuGet.org\r\n- [ ] NuGetTaskBuild --> NuGet.org\r\n- [ ] NuGetExeBuild --> Chocolatey.org\r\n- [ ] GemBuild --> ?\r\n- [ ] GitVersionTfsTaskBuild--> ?\r\n- [ ] zip --> Docker Hub\r\n- [ ] zip-dotnetcore --> Docker Hub\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"dazinator"}}