Git Multi hosting solution using TFS Web Portal for backlogs
up vote
0
down vote
favorite
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 at 16:12
monkeydeus
1161111
add a comment |
up vote
0
down vote
favorite
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 at 16:12
monkeydeus
1161111
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
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 at 16:12
monkeydeus
1161111
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 at 16:12
monkeydeus
1161111
asked Nov 10 at 16:12
monkeydeus
1161111
edited Nov 10 at 16:38
asked Nov 10 at 16:12
monkeydeus
1161111
asked Nov 10 at 16:12
monkeydeus
1161111
asked Nov 10 at 16:12
monkeydeus
1161111
1161111
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
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
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
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
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
