-
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
DotNetCoreCLI - Pack missing doc & wierd usage #10831
Comments
I just lost several hours because of this bug. Could you emit a warning if |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Was this fixed in the meanwhile? |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Was this fixed in the meanwhile? |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Was this fixed in the meanwhile? |
Also I think there are differences between parameters:
- name: projects
type: string
steps:
- task: DotNetCoreCLI@2
inputs:
command: restore
projects: ${{ parameters.projects }} # other options omitted
- task: DotNetCoreCLI@2
inputs:
command: build
projects: ${{ parameters.projects }}
- task: DotNetCoreCLI@2
inputs:
command: pack
searchPatternPack: ${{ parameters.projects }} however, if I try to use this template with a multiline string, only restore and build succeed: variables:
projects: |
some/project/A.csproj
other/project/B.csproj
- template: my-template
parameters:
projects: $(projects) Those 2 projects will be found by the restore and build tasks and work fine, but the pack task seems to use different logic for discovering projects and requires a |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Was this fixed in the meanwhile? |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Was this fixed in the meanwhile? |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Was this fixed in the meanwhile? |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Was this fixed in the meanwhile? |
Note
This could be related to issue #9789
Required Information
Question, Feature?
Type: Feature / Cleaning
Enter Task Name: DotNetCoreCLIV2
Environment
Issue Description
DotNetCoreCLI@2 provide a documented way for packing, who is I think mispelling / hard to get into / easier to get lost.
Like:
projects
won't be used duringpack
cmd and will be override bysearchPatternPack
who is required but has a default. And it seem to have one aliaspackagesToPack
who is not set or documented.The text was updated successfully, but these errors were encountered: