nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deploying one site from multiple branches to multiple environments

Adam Stoller

Hopefully the image attached will help explain what I'm asking about.
Environment:[indent]TS/SP/LS 7.2.1 on Linux[/indent]Scenario:[indent]We want to distinctly version development work from release candidates within TeamSite by using multiple branches, and this would mean having the same "site" name in both the "development" branch and its associated "release" branch. [/indent]Issue:[indent]I was recently told that you cannot have the same site name in multiple branches.
While I can understand this in terms of deploying the content / data to a single environment, I want to find out if this restriction (assuming that it was accurate to begin with, which it sounds like it was) still holds true if the "development" branch deploys to a "development" environment and the "release" branch deploys to the "production" deployment, and (a la Ghost Busters) we never cross the streams.[/indent]Request[indent]Can anyone, with actual knowledge of the abilities / limitations in this regard confirm whether this can, or cannot, be done?[/indent]

Find more posts tagged with

Comments

kaleemS

Hey, we are in the same boat.

Currently, I am looking at reference "Deploy Multiple Sites to Multiple Runtime Instances" in "SitePublisher Developer Guide".
I updated my configuration accordingly but I got error --
When I try to submit files to the new runtime I get the following error.
Could not invoke method: deployFiles, reason: null

I will let you know , if I resolved it.

Adam Stoller

Hey, we are in the same boat.

Currently, I am looking at reference "Deploy Multiple Sites to Multiple Runtime Instances" in "SitePublisher Developer Guide".
I updated my configuration accordingly but I got error --
When I try to submit files to the new runtime I get the following error.
Could not invoke method: deployFiles, reason: null

I will let you know , if I resolved it.

Do you have the same site name in multiple branches?
If not - then it's not the issue I'm trying to get an answer for (though I'd still be interested in seeing your resolution - but in a separate thread please)

If so - then yes, please let me know what you find out.

kaleemS

Yes, I do have the same site name in multiple branches.
However, I am also looking solution for deploying one site to multiple environments.

HKN1104

Hey, we are in the same boat.

Currently, I am looking at reference "Deploy Multiple Sites to Multiple Runtime Instances" in "SitePublisher Developer Guide".
I updated my configuration accordingly but I got error --
When I try to submit files to the new runtime I get the following error.
Could not invoke method: deployFiles, reason: null

I will let you know , if I resolved it.

Ghoti is not looking for Deploying to Multiple Environments. He is talking about same site name in Dev and release branches.

If it is Multiple Environments, He knew it long back.

Thanks

Adam Stoller

Ghoti is not looking for Deploying to Multiple Environments. He is talking about same site name in Dev and release branches.

If it is Multiple Environments, He knew it long back.

Thanks

No - I am talking about deploying to multiple environments - look at the title on the thread and re-read the initial posting.

I was told that what I'm looking to do is not technically possible - and I want to see if anyone else can confirm that it is / is not technically possible.

What I am not talking about is deploying a single site on a single branch to multiple environments (though I imagine I'll be looking at that too - however, there is a new thread on that, so it's not an issue for this thread)

HKN1104

Hopefully the image attached will help explain what I'm asking about.
Environment:[indent]TS/SP/LS 7.2.1 on Linux[/indent]Scenario:[indent]We want to distinctly version development work from release candidates within TeamSite by using multiple branches, and this would mean having the same "site" name in both the "development" branch and its associated "release" branch. [/indent]Issue:[indent]I was recently told that you cannot have the same site name in multiple branches.
While I can understand this in terms of deploying the content / data to a single environment, I want to find out if this restriction (assuming that it was accurate to begin with, which it sounds like it was) still holds true if the "development" branch deploys to a "development" environment and the "release" branch deploys to the "production" deployment, and (a la Ghost Busters) we never cross the streams.[/indent]Request[indent]Can anyone, with actual knowledge of the abilities / limitations in this regard confirm whether this can, or cannot, be done?[/indent]

Hi Ghoti

FOO_Dev and FOO Branch has same folder structure and has file name with xyz.site

FOO_Dev Branch : xyz.site is deploying to either Dev or prod: On Run time, we see it in Sites folder with FOO_dev branch name/sites/xyz.site:

FOO Branch: xyz.site is deploying to either Dev or Prod: On Run time, FOO branch name/sites/xyz.site.

I Tested in my Machine, With same Folder Structure and Same File name, I deployed it successfully and For reconfirmation, I checked in Run time Server, As Said, It created with branch name and then file name

Adam Stoller

[...]
I Tested in my Machine, With same Folder Structure and Same File name, I deployed it successfully and For reconfirmation, I checked in Run time Server, As Said, It created with branch name and then file name

Thanks for the confirmation - I also, last night, got pretty much the same information (though not confirmed like yours) that, given my scenario, the site on each branch would be treated as distinct sites and thus the information in Appendix F of the SitePublisher Developer's Guide should suffice.

Now all I have to do is get it all set up (so far it's just been theoretical)...

I'm going to close the thread now - and re-open it after I (eventually) get it done.

Thanks again.