Azure Pipelines: task PublishBuildArtifacts avoid zip












0















So I'm running this command



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)


And it is generating as Published Artifacts in a drop folder (Yes!), but as a zip file (myproj.zip).



I want to avoid the zip and would rather want the output as a full folder.



I'm researching but I cant find where this is being done.



The funny thing is that I tried it on my own CMD window and it is outputing the folder, but in Azure Pipelines it is generating a zip file.










share|improve this question























  • and even funnier, though I know they are not exactly the same, the vsbuild for netfw allows me to generate folder (not zip) and dotnet publish should be pretty much the same (since it uses msbuild in the background)

    – Kat Lim Ruiz
    Nov 12 '18 at 23:09













  • Could you look at this thread

    – Jayendran
    Nov 13 '18 at 2:58











  • What is your dotnet build task?

    – Shayki Abramczyk
    Nov 13 '18 at 7:39
















0















So I'm running this command



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)


And it is generating as Published Artifacts in a drop folder (Yes!), but as a zip file (myproj.zip).



I want to avoid the zip and would rather want the output as a full folder.



I'm researching but I cant find where this is being done.



The funny thing is that I tried it on my own CMD window and it is outputing the folder, but in Azure Pipelines it is generating a zip file.










share|improve this question























  • and even funnier, though I know they are not exactly the same, the vsbuild for netfw allows me to generate folder (not zip) and dotnet publish should be pretty much the same (since it uses msbuild in the background)

    – Kat Lim Ruiz
    Nov 12 '18 at 23:09













  • Could you look at this thread

    – Jayendran
    Nov 13 '18 at 2:58











  • What is your dotnet build task?

    – Shayki Abramczyk
    Nov 13 '18 at 7:39














0












0








0








So I'm running this command



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)


And it is generating as Published Artifacts in a drop folder (Yes!), but as a zip file (myproj.zip).



I want to avoid the zip and would rather want the output as a full folder.



I'm researching but I cant find where this is being done.



The funny thing is that I tried it on my own CMD window and it is outputing the folder, but in Azure Pipelines it is generating a zip file.










share|improve this question














So I'm running this command



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)


And it is generating as Published Artifacts in a drop folder (Yes!), but as a zip file (myproj.zip).



I want to avoid the zip and would rather want the output as a full folder.



I'm researching but I cant find where this is being done.



The funny thing is that I tried it on my own CMD window and it is outputing the folder, but in Azure Pipelines it is generating a zip file.







.net .net-core azure-devops azure-pipelines






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 '18 at 23:04









Kat Lim RuizKat Lim Ruiz

1,26611223




1,26611223













  • and even funnier, though I know they are not exactly the same, the vsbuild for netfw allows me to generate folder (not zip) and dotnet publish should be pretty much the same (since it uses msbuild in the background)

    – Kat Lim Ruiz
    Nov 12 '18 at 23:09













  • Could you look at this thread

    – Jayendran
    Nov 13 '18 at 2:58











  • What is your dotnet build task?

    – Shayki Abramczyk
    Nov 13 '18 at 7:39



















  • and even funnier, though I know they are not exactly the same, the vsbuild for netfw allows me to generate folder (not zip) and dotnet publish should be pretty much the same (since it uses msbuild in the background)

    – Kat Lim Ruiz
    Nov 12 '18 at 23:09













  • Could you look at this thread

    – Jayendran
    Nov 13 '18 at 2:58











  • What is your dotnet build task?

    – Shayki Abramczyk
    Nov 13 '18 at 7:39

















and even funnier, though I know they are not exactly the same, the vsbuild for netfw allows me to generate folder (not zip) and dotnet publish should be pretty much the same (since it uses msbuild in the background)

– Kat Lim Ruiz
Nov 12 '18 at 23:09







and even funnier, though I know they are not exactly the same, the vsbuild for netfw allows me to generate folder (not zip) and dotnet publish should be pretty much the same (since it uses msbuild in the background)

– Kat Lim Ruiz
Nov 12 '18 at 23:09















Could you look at this thread

– Jayendran
Nov 13 '18 at 2:58





Could you look at this thread

– Jayendran
Nov 13 '18 at 2:58













What is your dotnet build task?

– Shayki Abramczyk
Nov 13 '18 at 7:39





What is your dotnet build task?

– Shayki Abramczyk
Nov 13 '18 at 7:39












1 Answer
1






active

oldest

votes


















1














Please try the zipAfterPublish property (see also this page), optional in combination with the modifyOutputPath property.



This would result in the following yaml snippet:



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)
zipAfterPublish: false
modifyOutputPath: false





share|improve this answer
























  • lifesaver! +1000!, works perfect!, wow, I completely missed it from the docs

    – Kat Lim Ruiz
    Nov 15 '18 at 14:00













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271378%2fazure-pipelines-task-publishbuildartifacts-avoid-zip%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














Please try the zipAfterPublish property (see also this page), optional in combination with the modifyOutputPath property.



This would result in the following yaml snippet:



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)
zipAfterPublish: false
modifyOutputPath: false





share|improve this answer
























  • lifesaver! +1000!, works perfect!, wow, I completely missed it from the docs

    – Kat Lim Ruiz
    Nov 15 '18 at 14:00


















1














Please try the zipAfterPublish property (see also this page), optional in combination with the modifyOutputPath property.



This would result in the following yaml snippet:



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)
zipAfterPublish: false
modifyOutputPath: false





share|improve this answer
























  • lifesaver! +1000!, works perfect!, wow, I completely missed it from the docs

    – Kat Lim Ruiz
    Nov 15 '18 at 14:00
















1












1








1







Please try the zipAfterPublish property (see also this page), optional in combination with the modifyOutputPath property.



This would result in the following yaml snippet:



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)
zipAfterPublish: false
modifyOutputPath: false





share|improve this answer













Please try the zipAfterPublish property (see also this page), optional in combination with the modifyOutputPath property.



This would result in the following yaml snippet:



- task: DotNetCoreCLI@2
displayName: 'dotnet publish'
inputs:
command: 'publish'
publishWebProjects: false
projects: 'src/myproj/*.csproj'
arguments: -o $(build.artifactStagingDirectory)
zipAfterPublish: false
modifyOutputPath: false






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 15 '18 at 10:44









Herman CordesHerman Cordes

1,89363770




1,89363770













  • lifesaver! +1000!, works perfect!, wow, I completely missed it from the docs

    – Kat Lim Ruiz
    Nov 15 '18 at 14:00





















  • lifesaver! +1000!, works perfect!, wow, I completely missed it from the docs

    – Kat Lim Ruiz
    Nov 15 '18 at 14:00



















lifesaver! +1000!, works perfect!, wow, I completely missed it from the docs

– Kat Lim Ruiz
Nov 15 '18 at 14:00







lifesaver! +1000!, works perfect!, wow, I completely missed it from the docs

– Kat Lim Ruiz
Nov 15 '18 at 14:00




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271378%2fazure-pipelines-task-publishbuildartifacts-avoid-zip%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Full-time equivalent

さくらももこ

13 indicted, 8 arrested in Calif. drug cartel investigation