Deploying When SRC-IS-OLDER

Under what circumstances should OpenDeploy deploy a file where the reason is "src-is-older". Been trying to figure this one out but have not been able to.

We are using the "Directory Comparison" method of deploying on Teamsite 5.5.2 and OD 5.5.1.

If a file in an edition is older than the file on the target, does it replace it...it appears yes. If this is the case, it seems to me that there would have to have been a number of things that would have to occur.

1) a file would have to be deleted from a workarea, and this "deletion" submitted and published.

2) an older version of the file brought into the workarea, submitted, published and then deployed.

Would this scenario then give the reason as "src-is-older"? If not what would?

Below is an excerpt from the deploy log
-------------------------------------------------------------------------
08MAY03:10:54 Received 'get' request for (.\financials\confcalls.htm)
08MAY03:10:54 Sending [.\financials\confcalls.htm] [reason src-is-older] -- OK

Find more posts tagged with

Comments

Migrateduser

Here's an excerpt from the OD 5.6 Admin Guide concerning file comparison rules:

"If a source-side file’s modification date is newer than its target-side equivalent, then the file is deployed. You can also configure the deployment to deploy source-side files that have modification dates older than its target-side equivalent using the revert option, or if there is a difference in modification date either way using the dateDifferent option."

Situations that can cause the source file to be older include:
+ someone updating the target file with a newer file independently (i.e., went outside of your normal process)
+ someone replacing the source file with an older version of the file

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

daved1

Been out a while. Thanks for the response.

Has "dateDifferent='yes'" always meant deploy if there is any difference in dates?

Our backup deploy config files from our intial install back in November of 2001 have this rule set. I don't remember a reason to wanting both older and newer files deployed, but I think we now only want newer "dated" files. Time to change the config..

Thanks again for the reply.

Dave Deeds
Idaho Power Company

nipper

The default is date different only newer, but there is a flag for ship date different no matter what. check the manual

daved1

Post Script to My Last Reply....

If open deploy is set to only deploy newer files, does this thens preclude us from deploying a previous edition out.

Say we deploy some some updatged files, discover a problem with the code and need to replace them with older versions sitting in a previous editon.

nipper

Actually I don't think it will fail, rather it will just not overwrite newer files. For rollback you will want a "special" rollback deployment.

HTH

Andy

Adam Stoller

I don't know about "always" - but the 5.x "test.xml" deployment configuration has dateDifferent="yes" in it, and I think a lot of folks just copy-and-modify that configuration file and tend to leave that setting in place rather than determining if they really want it for their deployments...

As has been pointed out - the good thing about using dateDifferent="yes" is that it allows you to deploy both older and newer files ... but this is also the "bad" thing about it.

As the nipper responded, it's probably a good idea to have a special roll-back deployment configuration (possibly using revert="yes" rather than dateDifferent="yes" - they're mutually exclusive) and make the rest of your "normal" deployments with dateDifferent="no" [the default].

--fish
(Interwoven Senior Technical Consultant)