-
Notifications
You must be signed in to change notification settings - Fork 11
Setup proper build/deploy pipeline with Cake #35
Comments
How's the progress of this? 😃 |
Closing as we have travis and appveyor builds. Please re-open if I have got this wrong. |
@dazinator I think the suggestion here was to use Cake in the same way that the main GitVersion repository does, so that it handles everything from the build, all the way through to the deployment of the nupkg's (assuming that there are some). |
Correct. Reopening. |
I think its going to be a million times easier to just add an appveyor nuget deployment provider on to the appveyor.yaml. AppVeyor is already doing everything you would expect, including running the unit tests etc. |
For an example of that see: https://github.com/dazinator/Dotnettency/blob/master/appveyor.yml#L22 |
@dazinator please check gitter. |
@dazinator: Well, NuGet is not the only deployment target. We want to push packages to VSTS, Homebrew, Apt, NPM, etc., too. |
@asbjornu For the GitTools.Core assembly? I can understand those targets for our exe's vsix's etc but this project is just a reusable library. |
@dazinator: Ah, no. You're correct. |
@asbjornu - :-) |
Sure. A more precise issue might be "Auto-deploy NuGet package". A PR implementing that with AppVeyor would be great. 😃 |
Yup -That is already done.. see my commit further up on this issue. :-) |
Mirror after GitVersions
The text was updated successfully, but these errors were encountered: