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; } } }

Reverse Deployment and Version Control

Natasha

Hi All

I am running a reverse deployment between two teamsite hosts but the deployment is not preserving the previous versions of the file(copies the file and creates the version as 0+, although versions exist when viewed in STAGING)
Is it the default behavior or can it be changed to maintain the versions?
Your inputs will be appreciated.

OD - 6.1.1

Thanks
Natasha.

Find more posts tagged with

Comments

ISCBorisB

Hi All

I am running a reverse deployment between two teamsite hosts but the deployment is not preserving the previous versions of the file(copies the file and creates the version as 0+, although versions exist when viewed in STAGING)
Is it the default behavior or can it be changed to maintain the versions?
Your inputs will be appreciated.

OD - 6.1.1

Thanks
Natasha.

Before executing Deployment make sure that Deployment Target Workarea contains the latest Branch image from the STAGING

Adam Stoller

Hi All

I am running a reverse deployment between two teamsite hosts but the deployment is not preserving the previous versions of the file(copies the file and creates the version as 0+, although versions exist when viewed in STAGING)
Is it the default behavior or can it be changed to maintain the versions?
Your inputs will be appreciated.

OD - 6.1.1

Thanks
Natasha.

Have you read the manuals? Have you taken any training?
OpenDeploy (by itself) does not do versioning
(ControlHub, which is OpenDeploy with a built-in copy of TeamSite, does have some versioning capabilities, but that's a completely different thing)

OpenDeploy is mean to sync source and target directories (not version repositories) - as such, the behavior you're seeing would seem correct.

Natasha

Have you read the manuals? Have you taken any training?
OpenDeploy (by itself) does not do versioning
(ControlHub, which is OpenDeploy with a built-in copy of TeamSite, does have some versioning capabilities, but that's a completely different thing)

OpenDeploy is mean to sync source and target directories (not version repositories) - as such, the behavior you're seeing would seem correct.

I think you haven't understood my question or rather I should say i haven't able to put across it correctly.
Reverse Target - is a teamsite host and has files in the workarea which have been versioned say the current version is 5. Now when I run the deployment, all the previous versions are getting lost i.e the files which get copied become 0+.
Hope I have now clarified my query and looking forward to the answers.

Natasha

Before executing Deployment make sure that Deployment Target Workarea contains the latest Branch image from the STAGING

I submitted the content in the workarea before running the deployment so the content in the workarea is exact replica of STAGING.

Adam Stoller

I think you haven't understood my question or rather I should say i haven't able to put across it correctly.
Reverse Target - is a teamsite host and has files in the workarea which have been versioned say the current version is 5. Now when I run the deployment, all the previous versions are getting lost i.e the files which get copied become 0+.
Hope I have now clarified my query and looking forward to the answers.

Hmm - so after the deployment has occurred, TeamSite is seeing the files as if they are brand new (0+) instead of modified versions of the already existing files (e.g.: 5+).

And the workarea pre-existed, and was pre-populated before the deployment?

Do the versions of the files still exist in STAGING on the target TS Server?
If you do a submit with overwrite - do the files correct assume the next version (e.g.: 6) or do they seem to obliterate all history (e.g.: 1)?