CI should produce nupkgs as artifacts
See original GitHub issueRight now, it is rather tricky to depend on HEAD using paket, as you need to invoke build.sh
. I propose that the CI should produce a .nupkg
.
As an aside, it appears that the NuGet
fake target is borked.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Create And Publish A NuGet Package Into Azure Artifacts ...
In this article, you will learn how to create and publish a NuGet Package into Azure Artifacts using CI/CD Pipeline.
Read more >TeamCity Artifact Deployment - Steve Ellwood - Medium
NET I know that my project can produce a package on build and it's this artifact that we are interested in ie the...
Read more >Publish NuGet packages with Azure Pipelines (YAML ...
Publish NuGet packages. To publish packages to an Azure Artifacts feed from your pipeline, you must set the Project Collection Build Service ......
Read more >Publishing Artifacts in an Azure DevOps Release Pipeline
Learn how to take an existing Azure DevOps pipeline build artifact, package it up and publish to an Azure Artifacts NuGet feed.
Read more >How to Use CI/CD Pipelines for Your NuGet Packages
It's pretty straightforward: a build artifact will only make its way to the final stage (Production), once it's been tested in a number...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The new release is out: https://www.nuget.org/packages/FSharpPlus/1.1.0-CI00271
Yes, let’s do that !