OpenDeploy exclude_pattern Regex

I am using OpenDeploy 4.5.2 and want to exclude files that end with certain extensions, e.g. .log. However, I dont want to exclude files which may have the pattern 'log' in the file name, e.g. companylogo.gif

Have tinkered around with the exclude_pattern function and regex. Has anyone come up with anything to do this sort of thing in OpenDeploy 4.5.2?

Thanks,
Matthew.

Find more posts tagged with

Comments

Adam Stoller

It's been a while since I've used OpenDeploy 4.x - but I think you probably want to use a regex like:

\.log$

Let us know if that works

--fish
(Interwoven, Curriculum Development)

matthewc

Do I use:

exclude_pattern = \.log$
exclude_pattern = "\.log$"
exclude_pattern = '\.log$'
exclude_pattern regex = \.log$
exclude_pattern regex = "\.log$"
exclude_pattern regex = '\.log$'

Thanks,
Matthew.

Adam Stoller

Looking back at a 4.5 OpenDeploy manual starting around p. 54 ... it looks like:

source_exclude_pattern="\.log$"
or
destination_exclude_pattern="\.log$"
or
exclude_pattern="\.log$"

You can always run with the dont_do option to test each setting and verify what it *would* do before actually running the deployment (which I would again suggest you do in a test environment / with test data into a temporary target area - to verify results before putting it into use in production)

--fish
(Interwoven, Curriculum Development)

Migrateduser

Does this work the same way in 5.0.1?

Adam Stoller

Does this work the same way in 5.0.1?

Can you be more specific about the question?
Yes - there are regular-expression filters that you can utilize.
Yes - there is still the notion of source and target side filters (based on where the filter elment is placed within the cofiguration file).
No - there is no generic exclude from both source-and-target directive, you would have to specify the same filter in both the source and target locations within the deployment configuration file.

You might want to check out https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=2391 which covers the translation and limitations of the 5.0x implementation.

Or better, upgrade to either 5.5.1 SP2 or 5.6 and be able to do this kind of thing more easily (the DTD for deployment configuration files was cleaned up and expanded a bit)

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

Note: OD 5.6 expands filtering beyond what OD 5.5.1 supports. Smiley Wink

Todd Scallan
Senior Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

I'm still hoping that Interwoven, which uses various regex flavors in several of their applications, is planning on either creating some detailed documentation defining the valid syntax of each regex flavor used in all of its apps or pointing us to some detailed documentation that already exists. TeamSite uses a flavor of regex that is different from the OpenDeploy flavor which is different from the Metatagger flavor which is different than the perl flavor. To me, this was bad design as regex is difficult enough to master with a single flavor. Having more than one in your product suite is just wrong.

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