Git Multi hosting solution using TFS Web Portal for backlogs
tldr:
I don't know if my question is more Git-based, or TFS Web Portal based. My best case scenario is that we have multiple branches off a main branch, and each sub-branch is the top-level source for managing a backlog via TFS Web Portal. E.g instead of using /Main, my teams job board in TFS would use Main/Product 1, and another sister team could have a board based on Main/Product 2.
Been doing a little more research - is Forking the answer to my problem?
=========================================================================
I wasn't sure how to phrase the title - we currently have a consolidated solution hosted in TFS using VSTS that several 'product teams' are working from.
Ultimately a release to prod would be from /Main, but product teams could manage their branches and deploy to dev or qa independent of the other teams. More details below, but ultimately I'd like to make it so that if other teams want to use TFS Web Portal to manage their particular branch they can, but thay by using it to manage OUR branch, we aren't making decisions or precluding them from doing so. I don't know if TFS can go by branch, or if it needs separate repositories for each job board?
Product team in this case means you might create a view or controller or business logic class for your particular product, but, you are still working in the overall solution - shared homepage, etc.
In addition, several of our pages display work queues that span all products. So even if some items in the solution are product-specific, many are not, so breaking out projects by product does not seem viable to me.
I'd like to move this solution onto Git, and have sub-branches for each product, I have done that before and it worked fine for our needs. However on this new project, each product team is being managed independently, and since we are using Azure/TFS web portal for hosting the code, I'm concerned if we use a git repo, that means everyone will have to work from the same work board, or if we want to use TFS web portal to manage our backlog, that means we are making the decision for everyone, or precluding other product teams from creating their own backlog on a branch.
git tfs
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
add a comment |
tldr:
I don't know if my question is more Git-based, or TFS Web Portal based. My best case scenario is that we have multiple branches off a main branch, and each sub-branch is the top-level source for managing a backlog via TFS Web Portal. E.g instead of using /Main, my teams job board in TFS would use Main/Product 1, and another sister team could have a board based on Main/Product 2.
Been doing a little more research - is Forking the answer to my problem?
=========================================================================
I wasn't sure how to phrase the title - we currently have a consolidated solution hosted in TFS using VSTS that several 'product teams' are working from.
Ultimately a release to prod would be from /Main, but product teams could manage their branches and deploy to dev or qa independent of the other teams. More details below, but ultimately I'd like to make it so that if other teams want to use TFS Web Portal to manage their particular branch they can, but thay by using it to manage OUR branch, we aren't making decisions or precluding them from doing so. I don't know if TFS can go by branch, or if it needs separate repositories for each job board?
Product team in this case means you might create a view or controller or business logic class for your particular product, but, you are still working in the overall solution - shared homepage, etc.
In addition, several of our pages display work queues that span all products. So even if some items in the solution are product-specific, many are not, so breaking out projects by product does not seem viable to me.
I'd like to move this solution onto Git, and have sub-branches for each product, I have done that before and it worked fine for our needs. However on this new project, each product team is being managed independently, and since we are using Azure/TFS web portal for hosting the code, I'm concerned if we use a git repo, that means everyone will have to work from the same work board, or if we want to use TFS web portal to manage our backlog, that means we are making the decision for everyone, or precluding other product teams from creating their own backlog on a branch.
git tfs
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
add a comment |
tldr:
I don't know if my question is more Git-based, or TFS Web Portal based. My best case scenario is that we have multiple branches off a main branch, and each sub-branch is the top-level source for managing a backlog via TFS Web Portal. E.g instead of using /Main, my teams job board in TFS would use Main/Product 1, and another sister team could have a board based on Main/Product 2.
Been doing a little more research - is Forking the answer to my problem?
=========================================================================
I wasn't sure how to phrase the title - we currently have a consolidated solution hosted in TFS using VSTS that several 'product teams' are working from.
Ultimately a release to prod would be from /Main, but product teams could manage their branches and deploy to dev or qa independent of the other teams. More details below, but ultimately I'd like to make it so that if other teams want to use TFS Web Portal to manage their particular branch they can, but thay by using it to manage OUR branch, we aren't making decisions or precluding them from doing so. I don't know if TFS can go by branch, or if it needs separate repositories for each job board?
Product team in this case means you might create a view or controller or business logic class for your particular product, but, you are still working in the overall solution - shared homepage, etc.
In addition, several of our pages display work queues that span all products. So even if some items in the solution are product-specific, many are not, so breaking out projects by product does not seem viable to me.
I'd like to move this solution onto Git, and have sub-branches for each product, I have done that before and it worked fine for our needs. However on this new project, each product team is being managed independently, and since we are using Azure/TFS web portal for hosting the code, I'm concerned if we use a git repo, that means everyone will have to work from the same work board, or if we want to use TFS web portal to manage our backlog, that means we are making the decision for everyone, or precluding other product teams from creating their own backlog on a branch.
git tfs
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
tldr:
I don't know if my question is more Git-based, or TFS Web Portal based. My best case scenario is that we have multiple branches off a main branch, and each sub-branch is the top-level source for managing a backlog via TFS Web Portal. E.g instead of using /Main, my teams job board in TFS would use Main/Product 1, and another sister team could have a board based on Main/Product 2.
Been doing a little more research - is Forking the answer to my problem?
=========================================================================
I wasn't sure how to phrase the title - we currently have a consolidated solution hosted in TFS using VSTS that several 'product teams' are working from.
Ultimately a release to prod would be from /Main, but product teams could manage their branches and deploy to dev or qa independent of the other teams. More details below, but ultimately I'd like to make it so that if other teams want to use TFS Web Portal to manage their particular branch they can, but thay by using it to manage OUR branch, we aren't making decisions or precluding them from doing so. I don't know if TFS can go by branch, or if it needs separate repositories for each job board?
Product team in this case means you might create a view or controller or business logic class for your particular product, but, you are still working in the overall solution - shared homepage, etc.
In addition, several of our pages display work queues that span all products. So even if some items in the solution are product-specific, many are not, so breaking out projects by product does not seem viable to me.
I'd like to move this solution onto Git, and have sub-branches for each product, I have done that before and it worked fine for our needs. However on this new project, each product team is being managed independently, and since we are using Azure/TFS web portal for hosting the code, I'm concerned if we use a git repo, that means everyone will have to work from the same work board, or if we want to use TFS web portal to manage our backlog, that means we are making the decision for everyone, or precluding other product teams from creating their own backlog on a branch.
git tfs
git tfs
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
edited Nov 10 '18 at 16:38
monkeydeus
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
asked Nov 10 '18 at 16:12
monkeydeusmonkeydeus
1141211
1141211
add a comment |
add a comment |
0
active
oldest
votes
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%2f53240838%2fgit-multi-hosting-solution-using-tfs-web-portal-for-backlogs%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%2f53240838%2fgit-multi-hosting-solution-using-tfs-web-portal-for-backlogs%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
