• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Component/s: nuget-plugin
• Labels:

  None

[JENKINS-34421] Allow specifying the location of Nuget.config to use

Arnaud TAMAILLON created issue - 2016-04-24 20:33

Andrii Nikolaienko made changes - 2016-07-09 15:27

Assignee

New: Andrii Nikolaienko [ anikolaienko ]

Collapse comment: Andrii Nikolaienko added a comment - 2016-07-09 15:37

Andrii Nikolaienko added a comment - 2016-07-09 15:37

I am adding a new field (called 'Path') right above Schedule. I have concerns about it behavior and my idea includes two cases:
1) If field is empty plugin will still use NuGet.Config file from nuget.exe directory;
2) if user puts anything like 'NuGet.Config', '/Sources/NuGet.Config', 'Sources' or just '/' plugin will take NuGet.config file by the specified path, where root directory is the current workspace.

Is that good solution for that plugin?

Expand comment: Andrii Nikolaienko added a comment - 2016-07-09 15:37

Andrii Nikolaienko added a comment - 2016-07-09 15:37 I am adding a new field (called 'Path') right above Schedule. I have concerns about it behavior and my idea includes two cases: 1) If field is empty plugin will still use NuGet.Config file from nuget.exe directory; 2) if user puts anything like 'NuGet.Config', '/Sources/NuGet.Config', 'Sources' or just '/' plugin will take NuGet.config file by the specified path, where root directory is the current workspace. Is that good solution for that plugin?

R. Tyler Croy made changes - 2016-07-25 23:52

Workflow

Original: JNJira [ 170534 ]

New: JNJira + In-Review [ 183945 ]