excludePattern for servers

I have a deployment where I dont want files ending in "staff.html" deployed to certain servers. As such, I placed my filters in each nodeRef, in the targetRules section:

...
[HTML]

[/HTML] ...

Here is my file list:
test1_promo_staff.html
test_promo.html
test_promo_staff.html

All three files are deployed, where I only expect test_promo.html to be deployed. Any ideas why they are being deployed? I thought that filters could be used for file-based deployments...

Find more posts tagged with

Comments

ISCBorisB

I thought that filters could be used for file-based deployments...

You absolutely can use filters in File List deployments.

Your problem is the wrong filters tag location. Filters are nested tags of source pathSpecification Tag
(or reverseTarget for reverse Deployment)

rohitspathak123

Also regarding the re-ex

Shouldn't the reg-ex be this ( delimiting . with \. )

[HTML][/HTML]

instead of
[HTML][/HTML]

Regards
Rohit

ISCBorisB

Also regarding the re-ex

Shouldn't the reg-ex be this ( delimiting . with \. )

[HTML][/HTML]

instead of
[HTML][/HTML]

Regards
Rohit

Good catch! rwinterpacht should have used your syntax, it's certainly better.

That said, this is not the main reason for configuration problem. If you check provided examples you will see that "test1_promo_staff.html" for
example is a match with both regexes

rwinterpacht

Funny, thats how I had it, and it still doesnt work. The reason I have it in targetRules section under nodeRef is because I want to exclude those files from our internet servers, so that they only deploy to the intranet servers. I know I *could* use more definitions, but that's tricky because the definition is passed in at run-time as an argument...and this kind of filter should work.

ISCBorisB

Funny, thats how I had it, and it still doesnt work

We use List Deployment filters extensively, all works as documented. If you want to attach Deployment
configuration with filters under pathSpecification I'll take a look

Adam Stoller

Funny, thats how I had it, and it still doesnt work. The reason I have it in targetRules section under nodeRef is because I want to exclude those files from our internet servers, so that they only deploy to the intranet servers. I know I *could* use more definitions, but that's tricky because the definition is passed in at run-time as an argument...and this kind of filter should work.

A target-side filter, such as the one included in targetRules means "ignore the existence of this file on the target side" - where you want to prohibit sending the file, you need to "ignore the existence of this file on the source side" and thus need to specify the filter within the source (pathSpecification) element.

If you need to eliminate such files from being deployed to some but not all target nodes - then yes, you will need to create multiple definitions and multiple replicationFarmSets - a pair being used for cases where you can deploy those files and the other pair being used for cases where you cannot deploy those files - and then ultimately you will also have two execDeploymentTasks - one for each of the pairings.