Build pipeline for xaml files
I am trying to have a CI/CD pipeline for my project for which the output of the development is multiple xaml files.
I am trying to build a pipeline in Azure Devops tool. For build pipelines we have to select a task (for eg: for powershell scripts there is a powershell task) . Since our project files are xamls , what could we select here and complete our build pipeline?
Basically what are the build activities(like sonarQube and HPFortify for java project) that we can do on xaml files ? If there is none, can I bypass and have an empty build so that we can enter the release pipeline without much build checks.
We dont need to package it into a separate package. It can remain as xaml files after the build and the CD pipelines can deploy it to a folder in the server.
continuous-integration azure-devops azure-pipelines continuous-deployment cd
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
add a comment |
I am trying to have a CI/CD pipeline for my project for which the output of the development is multiple xaml files.
I am trying to build a pipeline in Azure Devops tool. For build pipelines we have to select a task (for eg: for powershell scripts there is a powershell task) . Since our project files are xamls , what could we select here and complete our build pipeline?
Basically what are the build activities(like sonarQube and HPFortify for java project) that we can do on xaml files ? If there is none, can I bypass and have an empty build so that we can enter the release pipeline without much build checks.
We dont need to package it into a separate package. It can remain as xaml files after the build and the CD pipelines can deploy it to a folder in the server.
continuous-integration azure-devops azure-pipelines continuous-deployment cd
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
add a comment |
I am trying to have a CI/CD pipeline for my project for which the output of the development is multiple xaml files.
I am trying to build a pipeline in Azure Devops tool. For build pipelines we have to select a task (for eg: for powershell scripts there is a powershell task) . Since our project files are xamls , what could we select here and complete our build pipeline?
Basically what are the build activities(like sonarQube and HPFortify for java project) that we can do on xaml files ? If there is none, can I bypass and have an empty build so that we can enter the release pipeline without much build checks.
We dont need to package it into a separate package. It can remain as xaml files after the build and the CD pipelines can deploy it to a folder in the server.
continuous-integration azure-devops azure-pipelines continuous-deployment cd
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
I am trying to have a CI/CD pipeline for my project for which the output of the development is multiple xaml files.
I am trying to build a pipeline in Azure Devops tool. For build pipelines we have to select a task (for eg: for powershell scripts there is a powershell task) . Since our project files are xamls , what could we select here and complete our build pipeline?
Basically what are the build activities(like sonarQube and HPFortify for java project) that we can do on xaml files ? If there is none, can I bypass and have an empty build so that we can enter the release pipeline without much build checks.
We dont need to package it into a separate package. It can remain as xaml files after the build and the CD pipelines can deploy it to a folder in the server.
continuous-integration azure-devops azure-pipelines continuous-deployment cd
continuous-integration azure-devops azure-pipelines continuous-deployment cd
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
asked Nov 23 '18 at 9:22
rahul rajrahul raj
3317
3317
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If your build artifact is just a bunch of XAML files then simply use a copy task to copy these to $(Build. ArtifactStagingDirectory) and then use a publish drop task to take the contents of $(Build. ArtifactStagingDirectory) and store it on the server and you're done.
You don't have to have a build task you just need the files required for your release which the above couple of steps will do nicely.
answered Nov 23 '18 at 15:29
Colin BColin B
2166
Thanks Colin. Let me try this out
– rahul raj
Nov 26 '18 at 4:50
Hi @ColinB I tried this. But there was one problem due to the security settings in my organization. If I plan to publish this into my build server or onto an azure VM, the security settings will block it. Since the build agent have a dynamic ip address(I think) it is difficult for the security team to open a port for a paricular ip. Is there a solution that you can suggest for this.Thanks@Colin
– rahul raj
Jan 15 at 8:26
The agent requires internet access (over SSL). The agent initiates this connection on an outgoing request and Azure DevOps just responds to this. If your organisation is shutting down internet access from the agent over SSL then I'm sorry this will never work for you.
– Colin B
Jan 21 at 11:28
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443779%2fbuild-pipeline-for-xaml-files%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
If your build artifact is just a bunch of XAML files then simply use a copy task to copy these to $(Build. ArtifactStagingDirectory) and then use a publish drop task to take the contents of $(Build. ArtifactStagingDirectory) and store it on the server and you're done.
You don't have to have a build task you just need the files required for your release which the above couple of steps will do nicely.
answered Nov 23 '18 at 15:29
Colin BColin B
2166
Thanks Colin. Let me try this out
– rahul raj
Nov 26 '18 at 4:50
Hi @ColinB I tried this. But there was one problem due to the security settings in my organization. If I plan to publish this into my build server or onto an azure VM, the security settings will block it. Since the build agent have a dynamic ip address(I think) it is difficult for the security team to open a port for a paricular ip. Is there a solution that you can suggest for this.Thanks@Colin
– rahul raj
Jan 15 at 8:26
The agent requires internet access (over SSL). The agent initiates this connection on an outgoing request and Azure DevOps just responds to this. If your organisation is shutting down internet access from the agent over SSL then I'm sorry this will never work for you.
– Colin B
Jan 21 at 11:28
add a comment |
If your build artifact is just a bunch of XAML files then simply use a copy task to copy these to $(Build. ArtifactStagingDirectory) and then use a publish drop task to take the contents of $(Build. ArtifactStagingDirectory) and store it on the server and you're done.
You don't have to have a build task you just need the files required for your release which the above couple of steps will do nicely.
answered Nov 23 '18 at 15:29
Colin BColin B
2166
Thanks Colin. Let me try this out
– rahul raj
Nov 26 '18 at 4:50
Hi @ColinB I tried this. But there was one problem due to the security settings in my organization. If I plan to publish this into my build server or onto an azure VM, the security settings will block it. Since the build agent have a dynamic ip address(I think) it is difficult for the security team to open a port for a paricular ip. Is there a solution that you can suggest for this.Thanks@Colin
– rahul raj
Jan 15 at 8:26
The agent requires internet access (over SSL). The agent initiates this connection on an outgoing request and Azure DevOps just responds to this. If your organisation is shutting down internet access from the agent over SSL then I'm sorry this will never work for you.
– Colin B
Jan 21 at 11:28
add a comment |
If your build artifact is just a bunch of XAML files then simply use a copy task to copy these to $(Build. ArtifactStagingDirectory) and then use a publish drop task to take the contents of $(Build. ArtifactStagingDirectory) and store it on the server and you're done.
You don't have to have a build task you just need the files required for your release which the above couple of steps will do nicely.
answered Nov 23 '18 at 15:29
Colin BColin B
2166
If your build artifact is just a bunch of XAML files then simply use a copy task to copy these to $(Build. ArtifactStagingDirectory) and then use a publish drop task to take the contents of $(Build. ArtifactStagingDirectory) and store it on the server and you're done.
You don't have to have a build task you just need the files required for your release which the above couple of steps will do nicely.
answered Nov 23 '18 at 15:29
Colin BColin B
2166
answered Nov 23 '18 at 15:29
Colin BColin B
2166
answered Nov 23 '18 at 15:29
Colin BColin B
2166
answered Nov 23 '18 at 15:29
Colin BColin B
2166
2166
Thanks Colin. Let me try this out
– rahul raj
Nov 26 '18 at 4:50
Hi @ColinB I tried this. But there was one problem due to the security settings in my organization. If I plan to publish this into my build server or onto an azure VM, the security settings will block it. Since the build agent have a dynamic ip address(I think) it is difficult for the security team to open a port for a paricular ip. Is there a solution that you can suggest for this.Thanks@Colin
– rahul raj
Jan 15 at 8:26
The agent requires internet access (over SSL). The agent initiates this connection on an outgoing request and Azure DevOps just responds to this. If your organisation is shutting down internet access from the agent over SSL then I'm sorry this will never work for you.
– Colin B
Jan 21 at 11:28
add a comment |
Thanks Colin. Let me try this out
– rahul raj
Nov 26 '18 at 4:50
Hi @ColinB I tried this. But there was one problem due to the security settings in my organization. If I plan to publish this into my build server or onto an azure VM, the security settings will block it. Since the build agent have a dynamic ip address(I think) it is difficult for the security team to open a port for a paricular ip. Is there a solution that you can suggest for this.Thanks@Colin
– rahul raj
Jan 15 at 8:26
The agent requires internet access (over SSL). The agent initiates this connection on an outgoing request and Azure DevOps just responds to this. If your organisation is shutting down internet access from the agent over SSL then I'm sorry this will never work for you.
– Colin B
Jan 21 at 11:28
Thanks Colin. Let me try this out
– rahul raj
Nov 26 '18 at 4:50
Thanks Colin. Let me try this out
– rahul raj
Nov 26 '18 at 4:50
Hi @ColinB I tried this. But there was one problem due to the security settings in my organization. If I plan to publish this into my build server or onto an azure VM, the security settings will block it. Since the build agent have a dynamic ip address(I think) it is difficult for the security team to open a port for a paricular ip. Is there a solution that you can suggest for this.Thanks@Colin
– rahul raj
Jan 15 at 8:26
Hi @ColinB I tried this. But there was one problem due to the security settings in my organization. If I plan to publish this into my build server or onto an azure VM, the security settings will block it. Since the build agent have a dynamic ip address(I think) it is difficult for the security team to open a port for a paricular ip. Is there a solution that you can suggest for this.Thanks@Colin
– rahul raj
Jan 15 at 8:26
The agent requires internet access (over SSL). The agent initiates this connection on an outgoing request and Azure DevOps just responds to this. If your organisation is shutting down internet access from the agent over SSL then I'm sorry this will never work for you.
– Colin B
Jan 21 at 11:28
The agent requires internet access (over SSL). The agent initiates this connection on an outgoing request and Azure DevOps just responds to this. If your organisation is shutting down internet access from the agent over SSL then I'm sorry this will never work for you.
– Colin B
Jan 21 at 11:28
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443779%2fbuild-pipeline-for-xaml-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
