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

Approach

kaalraa

Hi,

Could any one over here provide some suggestions or pointers as how to layout a process to move all the artifacts including DCT, DCR and PTs from a DEV box to Testing box?

Thanks in advance.

Find more posts tagged with

Comments

msrinivas

May be use OD?

kshitiz

Hi,

Could any one over here provide some suggestions or pointers as how to layout a process to move all the artifacts including DCT, DCR and PTs from a DEV box to Testing box?

Thanks in advance.

I would suggest use OpenDeply and use TeamSite to TeamSite deployment. This way you can preserve the extended attributes of your DCRs as well.

If that is not feasible in your case for some reason, then you need to extract all the extended attributes of your workarea content, store it temporarily somewhere, copy all the artifacts manually and then apply the extended attributes. Simple PERL scrips for extraction and applying extended attributes can do the trick.

gzevin

Hi,

Could any one over here provide some suggestions or pointers as how to layout a process to move all the artifacts including DCT, DCR and PTs from a DEV box to Testing box?

Thanks in advance.

if this is a one-off excersise, you might use a host of methods, starting with OD, ending with the old scripts that capture/restore EAs.

if this is a part of the process, you might think of a 'release workflow' that would ultimately use OD as well.

kaalraa

if this is a one-off excersise, you might use a host of methods, starting with OD, ending with the old scripts that capture/restore EAs.

if this is a part of the process, you might think of a 'release workflow' that would ultimately use OD as well.

Hey Greg,

It is going to be a part of process and as you said, to be used for every release. Could you please explain a bit more on your thoughts and suggestion?

Thanks.

gzevin

Hey Greg,

It is going to be a part of process and as you said, to be used for every release. Could you please explain a bit more on your thoughts and suggestion?

Thanks.

what I meant was that if this is a part of a process, you have a 'release workflow', that might contain even some approval steps (if needed). That workflow will take submitted files and take them through any pre/post-processing (if needed), to approval (if needed) and then to a dev/uat/production server, as appropriate. So you might implement your workflow as a pretty primitive streamlined set of tasks or make it a swiss-knife of workflows Smiley Happy

Even if you need to just deploy files, it's obviously easier to do from TeamSite proper, than to go to OD console separately.