Nuget Source Conflict

[nerumo]

I'm having a special scenario, which leads to an error during publish. I use a central gitlab project as a package registry, lets call it "registry project". I have a project A, that depends on a nuget Package that is in the "registry project". So for building the project, I need a nuget.config, that contains the package source "https://gitlab.com/api/v4/projects//packages/nuget/index.json".

It's the same url, that is needed for pushing project A to the project. Now the dotnet nuget add source command failes because of a conflict: error: The source specified has already been added to the list of available package sources. Provide a unique source.. I did not find a way to hack my way around it.

Could you make the dotnet nuget add source command optional? This would allow me to control the nuget.config myself. Alternatively, allow the add source command to fail if that error message appears (but feels a bit magic to me)

Could I support you in any way? Thank you already for all your work you put into this

[Kampfmoehre]

The question is on how to detect the duplicate. Since MS tends to localize errors we can not check the output for a certain string and there also isn't a special exit code when this happens.

I am not sure if we can give the url directly to the --source argument of dotnet nuget push, the docs are not very descriptive here so I'll have to test it.

If that doesn't work, all we can do is either adding a ignoreAddSourceError config option (which feels not very good) or completely remove that part and require the user to manually add the source and then specify the name for it - that would be a breaking change I also want to avoid.

[nerumo]

I agree, non of it feels great. How about reading the list of sources first?
dotnet nuget list source --format short gives the following output

some pseudocode

const output = execa('dotnet nuget list source --format short');
if (!output.includes(gitlabSourceUrl)) {
   execa('dotnet nuget add source ...');
}

what do you think?

[Kampfmoehre]

Yes that might work.

@nerumo can you test 2.0.1 if it works for you?

[nerumo]

it worked, thank you! 💪

as a sidenote: if the nuget config already contains the source, the source must be named "gitlab". it would be possible to read that from the output as well (without --format short), but the parsing of this is rather ugly and probably not worth the effort.

[Kampfmoehre]

Hm that could be a problem. I guess instead of parsing command output we could also just check the nuget.config file but that would not work if the config is set somehwere else. I will see if I can come up with some Regex for parsing the output.