Files in different directories to be placed under one directory using OD

HI ALl,

I want to deploy files under different directories to a single directory using open deploy.

Is it possible through opendeploy configuration?

Suppose abc.jpg, bcd.jpg, def.jpg from x,y,z directories to be placed under IMG directory

PLease help me

Find more posts tagged with

Comments

Rick Poulin

Yes, it's possible but there are things to consider. Specifically, if you're going to do area comparisons, you'll either want doDeletes=false, or you'll need to carefully set inclusion/exclusion filters for each source area. Filelist-based deployments might be less complex, but you'll still have to be careful about files overwriting each other.

sheikh1

HI ALl,

I want to deploy files under different directories to a single directory using open deploy.

Is it possible through opendeploy configuration?

Suppose abc.jpg, bcd.jpg, def.jpg from x,y,z directories to be placed under IMG directory

PLease help me

OpenDeploy default configuration doesn't allow you to deploy all in one directory. Either you have to change the source directory structure (or) pass the original filelist to the target server and run a dnr script to move your deployed files to desired target directory.

Adam Stoller

OpenDeploy default configuration doesn't allow you to deploy all in one directory. Either you have to change the source directory structure (or) pass the original filelist to the target server and run a dnr script to move your deployed files to desired target directory.

First - what do you mean by "default configuration"? OpenDeploy doesn't have a "default configuration" - it has several OOTB use-case-specific and/or as many home-grown customized configurations as you want - but nothing is "default".

Second - OpenDeploy has no problem deploying files from multiple source areas to a single target area - you simply have to use multiple definitions or a definition with multiple pathSpecification elements (assuming all the source locations live within a common source area path) in order to do it. (Keeping in mind the information already provided by rpoulin)

You seem to be assuming "facts" not in evidence in the thread. We have no information about the context of the question in terms of when / how / how frequently, such operations are needed by the OP. Until that information is provided, about saying "you have to change [this]" or "run a dnr script to [do that]"

sheikh1

First - what do you mean by "default configuration"? OpenDeploy doesn't have a "default configuration" - it has several OOTB use-case-specific and/or as many home-grown customized configurations as you want - but nothing is "default".

I know there is no default, default is not the correct word but what I mean here is when you add multiple definitions it is still not acceptable as a ideal solution because when there is a new directory created and a new file is added in to it you need to have to modify the OD config file to add the new definition to support it, LMK if it's incorrect, unless or otherwise the source tag can accept a regular expression value for filelist or workarea path which I haven't seen or known of.

Second - OpenDeploy has no problem deploying files from multiple source areas to a single target area - you simply have to use multiple definitions or a definition with multiple pathSpecification elements (assuming all the source locations live within a common source area path) in order to do it. (Keeping in mind the information already provided by rpoulin)

I don't think multile definition solution will be a best fit for this scenario even if is directory comparision or filelist deployment

You seem to be assuming "facts" not in evidence in the thread. We have no information about the context of the question in terms of when / how / how frequently, such operations are needed by the OP. Until that information is provided, about saying "you have to change [this]" or "run a dnr script to [do that]"

I just tried to provide few among the possible available options for this scenario, but nothing against here to any one or offensive to rick or you, I know we had similar encounter in the past but all is in the good will of our devnet users.
cheers,

Rick Poulin

I don't think multile definition solution will be a best fit for this scenario even if is directory comparision or filelist deployment

I think maybe you're assuming that the OP is looking for a single deployment that collapses an arbitrary source directory structure into a single folder. If that is indeed the case, you're right in saying OpenDeploy doesn't do that. You'd have to write something custom to collapse it in a temp folder or something, before deploying it out. (or, if you know the structure ahead of time, map individual folders as separate sources)

Fish and I assumed that the requirement is to deploy multiple sources (i.e. different branches) to a single target folder, which is not an unusual scenario.

In contrast, I didn't even think about the collapsing-arbitrary-structure scenario because I can't come up with a use case where someone would need to do that.