doDeletes and excludePath

tvaughan

Hi,

I was led to believe that with OD5.5.1, you'd be able to use comparison-based deployments (as opposed to filebased) that allowed you to exclude directories from being deleted on the target machine. I appear, however, to be misled.

Here's my situtation. I have this 2-level branch structure:

/default/main/corporate/about_us
                        blah
                        warning

/default/main/corporate/share/images
                              includes
                              javascript

That branch structure contains the branch "corporate" with all these corporate assets and the sub-branch "share" that hold more tightly-monitored and tightly-controlled global branding assest.

The branches get deployed to a web server with this docroot structure:

/www/docroot/corporate/about_us
                       blah
                       images
                       include
                       javascript
                       warning

What I thought'd I'd be able to do with OD 5.5.1 is to define an area-based deployment that I can run from my corporate branch that excludes the directories contained within my share branch.

I'd like to enable the "doDeletes" functionality so that the people who clutter up the corporate branch with **** can periodically clean up their old stuff and deploy the clean corporate directories to the web server.

However, if I just blindly enable the area-based comparison, when such a 'clean deployment' happens, OD will delete the images, include and javascript directories because they aren't part of the corporate branch (which serves as the source image for the area-based comparison).

Thus, I'd like to have the images, include and javascript directories listed in an excludePath parameter somewhere so that they aren't blown away when a corporate deployment happens.

I would also like to avoid assembling some "master" branch that is the result of a bunch of copies of the corporate and share branch. I know that's an option, but it is both tedious, confusing for the user, and wasteful. Is what I want possible in 5.5.1 SP2?

TIA
Tom