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

exclude regex

summergs

Hello!

Branch stucture: /default/main/HOME
Home Branch has Workarea, Staging, Edition, and SubBranches
SubBranch names are dynamically created and therefor names are random.
SubBranches contain Workarea, Staging, Edition

I am trying to:
Exclude everything in OD from HOME branch (works)
Exclude everything in SubBranches EXCEPT SubBranch name and files in STAGING/IMAGES folder (maintaining file structure on target) i.e. SubBranchName/Images/*.*

Tried several regexs no luck, any ideas?

Find more posts tagged with

Comments

Adam Stoller

Please present what you tried and what occurred - also please provide (as an attachment) the deployment configuration that you are using.

Also - what version of OpenDeploy (including service pack and/or patches) and what platform(s)? This information may make a difference for the answer to your question.

--fish
(Interwoven Senior Technical Consultant)

summergs

Hi Fish,

Thanks for responding. I am running OD 551 wrapper build 6054.

I have attached the TEST config file. In this simple version I expected to see my SubBranch containing only the Edition folder (and it contents) and WorkArea folder (and its contents). Instead, I still get all folders (and their contents) under the SubBranch. Help?

Adam Stoller

<excludePath subPath="(^|[\\V])STAGING([\\V]|$)" />
Most likely the above is the exclusion that isn't working. For one thing I'm not sure the regex does any thing like what you want, nor whether it would work at all in the context given. If you can upgrade to OpenDeploy 5.6 SP1, you'll gain the advantage of being able to use includePath and includePattern which might help you, but I guess I'm still a bit confused over what you are trying to do.

You'll have Y:\default\main/HOME\sub-branch1\... and perhaps Y:\default\main\HOME\sub-branch2\..., etc. - and they would all be set to deploy into the same target root area (C:\inetpub\wwwroot\deployed\sub-branch1\, etc.) and I don't think you'll end up with what you're hoping for.

I think you'd be better served by creating a definition for each of the sub-branches - all the way through to the STAGING or EDITION directory - and then specifying a path of "./images" or whatever, and then proceeding from there to identify the target directories etc.

--fish
(Interwoven Senior Technical Consultant)