Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Easier package publishing #11249

Open
bugproof opened this issue Sep 18, 2021 · 4 comments
Open

[Feature]: Easier package publishing #11249

bugproof opened this issue Sep 18, 2021 · 4 comments
Labels
Functionality:Push Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:Feature

Comments

@bugproof
Copy link

bugproof commented Sep 18, 2021

NuGet Product(s) Involved

NuGet.exe, dotnet.exe

The Elevator Pitch

The command to publish packages to nuget.org could be simplified. In Rust's package manager - cargo you just do cargo login apikey (just one time) and cargo publish and that's it.

Similar nuget subcommand could do the following:

  • Build project in release mode
  • Pack
  • Push to nuget.org

The api key could be saved in some json file or just use nuget setapikey

Additional Context and Details

No response

@chrisraygill
Copy link
Contributor

chrisraygill commented Sep 20, 2021

Hi, thanks for the suggestion @bugproof!

Is what you have in mind something like what's described in the this proposal? #10658

The proposal is still in progress, but the motivation and idea is there 😃

If so, please leave consider interacting with the associated issue!

@nkolev92 nkolev92 added WaitingForCustomer Applied when a NuGet triage person needs more info from the OP Functionality:Push and removed Triage:Untriaged labels Sep 21, 2021
@bugproof
Copy link
Author

bugproof commented Sep 21, 2021

@chgill-MSFT Similar to the proposal you mentioned but it should also build in release mode and create package for you so you don't have to specify nupkg path yourself. If that's the plan then feel free to close the issue. I was even thinking to create a custom dotnet-tool for this exact purpose. This doesn't seem like a lot of work.

dotnet tool install -g nuget-push or something like that

There should also be ability to set a default package source other than nuget.org but it's fine to just support nuget.org as it's the most commonly used. Ideally it should work just like cargo publish https://doc.rust-lang.org/cargo/reference/publishing.html

@ghost ghost added WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. and removed WaitingForCustomer Applied when a NuGet triage person needs more info from the OP labels Sep 21, 2021
@chrisraygill
Copy link
Contributor

Hi @bugproof!

We recently started doing some more research around this area. I would love to know, what motivates you to push packages from your local machine using the CLI as opposed to the NuGet.org upload UI?

cc @loic-sharma

@ghost ghost added WaitingForCustomer Applied when a NuGet triage person needs more info from the OP and removed WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. labels Oct 20, 2021
@bugproof
Copy link
Author

It's much faster. I don't have to visit NuGet.org just enter 1 short command and it's published. Much better experience.

Instead of:

  • Open your browser
  • Visit Nuget.org
  • Login
  • Pack
  • Drag and drop/look for nupkg on your drive

You just do:

  • Open terminal in project dir
  • Enter something like dotnet push/publish without any additional parameters you have to remember

@ghost ghost added WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. and removed WaitingForCustomer Applied when a NuGet triage person needs more info from the OP labels Oct 20, 2021
@nkolev92 nkolev92 added Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. and removed WaitingForClientTeam Customer replied, needs attention from client team. Do not apply this label manually. labels Nov 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:Push Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:Feature
Projects
None yet
Development

No branches or pull requests

4 participants