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

excludes

msrich

TS 5.5.2 (W2K) deploying to Solaris via OD 5.5.1.

I'm having trouble exluding deeper sub-directories. I've tried excludePath and excludePattern. Any help appreciated. See attached file.

Find more posts tagged with

Comments

Migrateduser

What is the initial "." for in your regex's?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

msrich

I was following instrn on p.207 of OD Admin Guide (v5.0):

"The paths always begin with "./"

I just removed these '.' characters and deployed again. I'll attach the log, which looks similar to how it always looks. It always looks like it's sending all files from all directories I'm trying to exclude. Thanks for your help.

Migrateduser

You don't need the dot, and if you did you'd have to escape it with a "\" symbol as a dot means "any character" in regex speak. You may also need to escape your "/" symbols as well.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Edited by Smitty77 on 05/12/03 01:34 PM (server time).

msrich

Thanks, but I'm not sure where you're looking and seeing backslashes. I have forward slashes in the XML config file. Maybe there are backslashes in the log, but I didn't "ask for" them.

From my latest the XML file:

<filters >
<excludePattern regex="/vsa/scripts/site_env\.js" />
<excludePath subPath="cgi-bin" />
<excludePattern regex="/vsa/technical/current_do_not_deploy/" />
<excludePattern regex="/vsa/technical/future_do_not_deploy/" />
<excludePattern regex="/vsa/technical/introduction_do_not_deploy/" />
<excludePattern regex="/vsa/technical/specification_do_not_deploy/" />
</filters>

Migrateduser

Try this and see if it works:

<filters >
<excludePattern regex="/vsa/scripts/site_env\.js" />
<excludePath subPath="cgi-bin" />
<excludePattern regex="[/\]current_do_not_deploy" />
<excludePattern regex="[/\]future_do_not_deploy" />
<excludePattern regex="[/\]introduction_do_not_deploy" />
<excludePattern regex="[/\]specification_do_not_deploy" />
</filters>

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

Why not just use

<excludePath subPath="foo/bar" />

for all your subdirs you want to exclude?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

msrich

The [/\] seems to work.

I had tried the excludePath like you mentioned in the last note, e.g.,

<excludePath subPath="vsa\technical\future_do_not_deploy" />

...but it didn't work. Maybe it needs the forward slashes instead.

msrich

I have a file (site_env.js) in 'dir_A' that I don't want in place on my target and a file by the same name (in 'dir_B' on the source) that I do want in place on the target.

I thought maybe I'd always deploy both, with the 'dir_B' file overlaying the 'dir_A' file on the target, but I can't seem to get the 'doDeletes' and file comparison rules right to get this working. Can youi help?

The file is the only file in the second-cited local directory ('dir_B' in my description).

Adam Stoller

Are you saying you have two distinct source files that deploy to the same target area in the same deployment?
I don't believe this is supported in OpenDeploy as the deployments would be running concurrently and there's no way to ordain which source file ends up in the target area first or second.

This is generally not a good working premise - either you need to exclude one of the files from being deployed at all - or better, remove the contention at the source level.

--fish
(Interwoven Senior Technical Consultant)

msrich

Gotcha.

Can you suggest how I can the file from dir_A from being deployed? I've tried various syntax w/excludePattern, but I don't think it's working. Do I need to have an exclude line in the pathspec within the source section of the XML as well as within the target?

My fear is that specifications within the target are in force for any and all source path_specs; this might pose a problem when I want to exclude the file from one source_dir and deploy it only from another.

One flavor of syntax I had been trying as a source filter is as follows:

<excludePattern regex=".*vsa\scripts\site_env\.js" />

Adam Stoller

If you want to prevent the file from being deployed - the filter needs to be in in the <pathSpecification> container. If you want to prevent the file from being deleted, the filter also needs to be in either the <target> container or within the <targetRules> container within the <pathSpecification> container.

  <source>
    <sourceXXX ...>
      <pathSpecification>
        <path .../>
        <filters>
          <!-- Prevent from being deployed -->
        </filters>
        <targetRules ...>
          <filters>
            <!-- Prevent from being deleted if using doDeletes -->
            <!-- optional location (1) -->
          </filters>
        </targetRules>
      </pathSpecification>
    </sourceXXX>
  </source>
  <target>
    <targetFilesystem .../>
    <filters>
      <!-- Prevent from being deleted if using doDeletes -->
      <!-- optional location (2) -->
    </filters>
  </target>

<excludePatter regex=".*vsa\scripts\site_env\.js"/>

For path separators you either need to use '/' or '\\' - a single '\' is an escape-sequence.

--fish
(Interwoven Senior Technical Consultant)

msrich

Works like a charm. Thanks for the keys to the kingdom.

PaulW

Ghoti,

I am doing it in the exact format you are stating, but it is not preventing the files from being deleted. Is there something different which needs to be done for OD5.0.1?

Michael

Things in OD 5.0.1 are indeed different. See
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=2391

Cheers
Michael