-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Users/pspill/dotnet2 #4520
Users/pspill/dotnet2 #4520
Conversation
Tasks/DotNetCoreCLI/package.json
Outdated
"q": "^1.4.1", | ||
"archiver": "1.2.0" | ||
"archiver": "1.2.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check if we need OSS registration for this version of archiver.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
downgraded to approved archiver 1.0.1
Tasks/DotNetCoreCLI/packcommand.ts
Outdated
|
||
const dotnetPath = tl.which("dotnet", true); | ||
for (const file of filesList) { | ||
await dotnetPackAsync(dotnetPath, file, outputDir, nobuild, version, props, verbosity); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could/should we do this on parallel?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea, but I'm worried interleaved output on async tool.exec would be confusing on error,
Tasks/DotNetCoreCLI/packcommand.ts
Outdated
} | ||
} | ||
|
||
function dotnetPackAsync(dotnetPath: string, packageFile: string, outputDir: string, nobuild: boolean, version: string, properties: string[], verbosity: string) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: add function return type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
|
||
for (const packageFile of filesList) { | ||
|
||
await dotNetNuGetPushAsync(dotnetPath, packageFile, feedUri, apiKey, configFile, tempNuGetConfigDirectory); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here, would we benefit from parallel push?
import * as commandHelper from "nuget-task-common/CommandHelper"; | ||
|
||
|
||
const NUGET_ORG_V3_URL: string = "https://api.nuget.org/v3/index.json"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit. This should be in a common location.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
tl.debug(`All URL prefixes: ${urlPrefixes}`); | ||
} | ||
|
||
let accessToken = auth.getSystemAccessToken(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should all of the config code placed in a common location since it's the same as nugetRestore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not exactly the same, so factoring out common areas cleanly would take some work.
Tasks/DotNetCoreCLI/task.json
Outdated
}, | ||
"minimumAgentVersion": "2.0.0", | ||
"instanceNameFormat": "dotnet $(command)", | ||
"groups": [], | ||
"groups": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit. indenting
This PR contains the following changes for the DotNetCoreCLI build task:
UI and experience is consistent with NuGetCommand build task for restore/pack/push