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

Issue with IncludePattern Filters | Deployment Failing

dolly1

All,

We have an assets branch which can contain subfolders like global, catalog etc. Now the requirement is anything inside global should get deployed to one target server and anything inside catalog should get deployed to another target server.

When we deploy edition it can contain both global and catalog folders and we are using filters for this.

< filters >
< includePattern regex="catalog" / >
< /filters >

and

< filters >
< includePattern regex="global" / >
< /filters >

in 2 different definitions in the same open deploy configuration file.

This pattern does not seem to be working because even though my one edition just contains global folder still both the definitions are getting executed and all the files are getting deployed on both the definitions (Servers) and hence the deployment is failing. Deployment is transactional.

Why it is failing because it is trying to deploy same file at the same location twice.

Ideally when my edition does not contain catalog folder at all it should not try to execute the other definition so its clearly looks the problem with filters.

My complete branching structure looks like

/default/main/mainBranch/assets/WORKAREA/waName/global/images/img.jpg
/default/main/mainBranch/assets/WORKAREA/waName/catalog/images/img2.jpg

Please help me in figuring out the issue.

TS 6.7.1 SP1
OD 6.1.1
Solaris 10

Find more posts tagged with

Comments

Migrateduser

Try adding your filter to BOTH the source and target tags. For example:

[HTML]

[/HTML]

Somewhere in the OpenDeploy docs it warns you about this and that in order to ensure that these types of filters work, you need to include them for both the source and target.

Migrateduser

[left]This didn't paste very well, but here's the section of the OpenDeploy Deployment Configuration Guide (Chapter 3 - Filters) where it tells you how source/target filters work:

Source-Side and Target-Side Filters Interaction[/left]

[font=Times New Roman][size=3][left]You can configure filters on the source side, target side, or both. How OpenDeploy uses

filters depends on the source-target filter relationship:
[/left]

[/size][/font]

[font=Wingdings][size=1][left]????

[/size][/font]

[font=Times New Roman][size=3]If the filter exists only on the source side, OpenDeploy ignores those excluded

source-side files and cannot deploy them. If the

[/size][/font]

[font=Courier][size=1]doDeletes

[/size][/font]

[font=Times New Roman][size=3]feature is enabled, those

excluded source-side files that are also present on the target-side will be deleted.
[/left]

[/size][/font]

[font=Wingdings][size=1][left]????

[/size][/font]

[font=Times New Roman][size=3]If the filter exists only on the target side, OpenDeploy assumes those excluded files

do not exist on the target, and will deploy any files that also exist on the source-side.
[/left]

[/size][/font]

[font=Wingdings][size=1][left]????

[/size][/font]

[font=Times New Roman][size=3]If the filter exists both on the source and target sides, OpenDeploy ignores the

excluded files on both sides, resulting in the target-side files being unaffected.

If you are using filters in conjunction with the

[/size][/font]

[font=Courier][size=1]doDeletes

[/size][/font]

[font=Times New Roman][size=3]transfer rules feature, you

must configure target-side exclusion filters to protect any files on the target that you do

not want to delete. Otherwise, OpenDeploy will delete any files on the target that are not

on the source, either because the files are physically not present in the source file

location, or because source-side exclusion filters have made it appear that the files are

not present. See

[/size][/font]

[font=Times New Roman][size=3][color=#0000ff][font=Times New Roman][size=3][color=#0000ff]“Transfer Rules” on page 132

[/color][/size][/font][/color][/size][/font]

[font=Times New Roman][size=3]for more information on configuring the
[/left]

[/size][/font]

[font=Courier][size=1]doDeletes

[/size][/font]

[font=Times New Roman][size=3]feature.

[/size][/font]