Mixing
Commit CI build outcome into repository
I have 2 git repositories in Azure devops, 1 for my back-end app & 1 for my front-end app, I want that in the CI release process it should take the outcome from the front-end build & commit it to the back-end repository into the wwwroot folder;
The reason why I need this is because I want that the back-end developers should have the front-end build from within their code, so they should be able to debug the back-end code with the front-end UI within visual studio
I have already tried to use the copy files task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/copy-files?view=vsts&tabs=yaml), but it don't do the job, either because I cannot seem to get the right target path, or because it also needs to be committed
azure-devops asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
add a comment |
I have 2 git repositories in Azure devops, 1 for my back-end app & 1 for my front-end app, I want that in the CI release process it should take the outcome from the front-end build & commit it to the back-end repository into the wwwroot folder;
The reason why I need this is because I want that the back-end developers should have the front-end build from within their code, so they should be able to debug the back-end code with the front-end UI within visual studio
I have already tried to use the copy files task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/copy-files?view=vsts&tabs=yaml), but it don't do the job, either because I cannot seem to get the right target path, or because it also needs to be committed
azure-devops asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
2
This is not a good approach. A better approach would be to use submodules so that the front-end code can be built and debugged on-demand by the back-end developers.
– Daniel Mann
Jan 2 at 20:25
@DanielMann The back-end developers have no reason to debug the front-end code, & it takes long to build the front-end, Why would they need to wait for the front-end build every time they want to debug the back-end
– Joseph Goldberger
Jan 2 at 20:44
2
Then publish the front-end build outputs as a package and have it referenced in the back-end project as a dependency that can be restored by their toolchain.
– Daniel Mann
Jan 2 at 20:50
add a comment |
I have 2 git repositories in Azure devops, 1 for my back-end app & 1 for my front-end app, I want that in the CI release process it should take the outcome from the front-end build & commit it to the back-end repository into the wwwroot folder;
The reason why I need this is because I want that the back-end developers should have the front-end build from within their code, so they should be able to debug the back-end code with the front-end UI within visual studio
I have already tried to use the copy files task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/copy-files?view=vsts&tabs=yaml), but it don't do the job, either because I cannot seem to get the right target path, or because it also needs to be committed
azure-devops asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
I have 2 git repositories in Azure devops, 1 for my back-end app & 1 for my front-end app, I want that in the CI release process it should take the outcome from the front-end build & commit it to the back-end repository into the wwwroot folder;
The reason why I need this is because I want that the back-end developers should have the front-end build from within their code, so they should be able to debug the back-end code with the front-end UI within visual studio
I have already tried to use the copy files task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/copy-files?view=vsts&tabs=yaml), but it don't do the job, either because I cannot seem to get the right target path, or because it also needs to be committed
azure-devops azure-devops asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
asked Jan 2 at 20:19
Joseph GoldbergerJoseph Goldberger
68116
68116
2
This is not a good approach. A better approach would be to use submodules so that the front-end code can be built and debugged on-demand by the back-end developers.
– Daniel Mann
Jan 2 at 20:25
@DanielMann The back-end developers have no reason to debug the front-end code, & it takes long to build the front-end, Why would they need to wait for the front-end build every time they want to debug the back-end
– Joseph Goldberger
Jan 2 at 20:44
2
Then publish the front-end build outputs as a package and have it referenced in the back-end project as a dependency that can be restored by their toolchain.
– Daniel Mann
Jan 2 at 20:50
add a comment |
2
This is not a good approach. A better approach would be to use submodules so that the front-end code can be built and debugged on-demand by the back-end developers.
– Daniel Mann
Jan 2 at 20:25
@DanielMann The back-end developers have no reason to debug the front-end code, & it takes long to build the front-end, Why would they need to wait for the front-end build every time they want to debug the back-end
– Joseph Goldberger
Jan 2 at 20:44
2
Then publish the front-end build outputs as a package and have it referenced in the back-end project as a dependency that can be restored by their toolchain.
– Daniel Mann
Jan 2 at 20:50
2
2
This is not a good approach. A better approach would be to use submodules so that the front-end code can be built and debugged on-demand by the back-end developers.
– Daniel Mann
Jan 2 at 20:25
This is not a good approach. A better approach would be to use submodules so that the front-end code can be built and debugged on-demand by the back-end developers.
– Daniel Mann
Jan 2 at 20:25
@DanielMann The back-end developers have no reason to debug the front-end code, & it takes long to build the front-end, Why would they need to wait for the front-end build every time they want to debug the back-end
– Joseph Goldberger
Jan 2 at 20:44
@DanielMann The back-end developers have no reason to debug the front-end code, & it takes long to build the front-end, Why would they need to wait for the front-end build every time they want to debug the back-end
– Joseph Goldberger
Jan 2 at 20:44
2
2
Then publish the front-end build outputs as a package and have it referenced in the back-end project as a dependency that can be restored by their toolchain.
– Daniel Mann
Jan 2 at 20:50
Then publish the front-end build outputs as a package and have it referenced in the back-end project as a dependency that can be restored by their toolchain.
– Daniel Mann
Jan 2 at 20:50
add a comment |
0
active
oldest
votes
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%2f54012644%2fcommit-ci-build-outcome-into-repository%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f54012644%2fcommit-ci-build-outcome-into-repository%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
2
This is not a good approach. A better approach would be to use submodules so that the front-end code can be built and debugged on-demand by the back-end developers.
– Daniel Mann
Jan 2 at 20:25
@DanielMann The back-end developers have no reason to debug the front-end code, & it takes long to build the front-end, Why would they need to wait for the front-end build every time they want to debug the back-end
– Joseph Goldberger
Jan 2 at 20:44
2
Then publish the front-end build outputs as a package and have it referenced in the back-end project as a dependency that can be restored by their toolchain.
– Daniel Mann
Jan 2 at 20:50