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

FileList Deployment

Bhargav Coca

Let me refresh my concept, file based deployement is used to deploy the files which are specified in "$iwhome/tmp/filelist.txt" and all those files which have a date difference from that of staging are deployed to the Production.

So lets assume there are several files in our "filelist.txt" is it like all those files get deployed or only those files with date difference get deployed?? I am little confused here.

If say only those files with Date difference get deployed, how can i get the list of files which are deployed into an other filelistdeployed.txt??

Please advice.

Thanks

Find more posts tagged with

Comments

nipper

The datedifferent and file list are 2 different areas of the XML. If you use datedifferent=no on a filelist, then the filelist will be overwritten no matter what the dates.

Migrateduser

Let me refresh my concept, file based deployement is used to deploy the files which are specified in "$iwhome/tmp/filelist.txt" and all those files which have a date difference from that of staging are deployed to the Production.

So lets assume there are several files in our "filelist.txt" is it like all those files get deployed or only those files with date difference get deployed?? I am little confused here.

If say only those files with Date difference get deployed, how can i get the list of files which are deployed into an other filelistdeployed.txt??

Please advice.

Thanks

filelist deployments does not compare the data difference between workarea and STAGING area on the source TeamSite server, it deploys all the files that are changed or different from the target server that is specified in the deployment configuration file. If you submit all the files that are deployed to STAGING then you can comparea the files on the source server to get the list of files deployed.

Bhargav Coca

I agree with both of you. But say in your configuration file you specify this

since you have dateDifferent="yes", it will deploy only those files which are of Date Difference right? Please correct me if i am not.

I think no matter you specify yes or no, for a filelist based deployement all the files which are specified in filelist.txt will be deployed..

Assumins this is not the case, how can i get the files whicha re deployed using a CLT??

Thanks

nipper

If you have dateDifferent=yes then it should only deploy the files in your list that are actually different.

Now, if after testing you find that this is incorrect, then a bug should be filed. You can also peruse the DTD and verify my comments, it tends to be the best documentation.

Migrateduser

Assumins this is not the case, how can i get the files whicha re deployed using a CLT??

Thanks

I don't think there is a CLT that will tell you which files are deployed or re-deployed, you need to parse the od in memory log or log file to get this data.

Bhargav Coca

Nipper you are wrong, even though i specify date difference to be "yes" filelist will deploy the entire list.

here is my sample manifest file after deplyment, here only Test1.txt has been modified.
[html]

[/html]

Adam Stoller

Nipper you are wrong, even though i specify date difference to be "yes" filelist will deploy the entire list.

here is my sample manifest file after deplyment, here only Test1.txt has been modified.
[html]

[/html]

Unless something changed somewhere - filelist deployments perform NO comparisons between source and target with one exception - if the file is not present on the source side - it will treat it as a deletion request. Thus I do not believe dateDifferent, revert, or any of those options affect the behavior of a filelist deployment (that's why they tend to be faster than other styles of deployments)

nipper

Unless something changed somewhere - filelist deployments perform NO comparisons between source and target with one exception - if the file is not present on the source side - it will treat it as a deletion request. Thus I do not believe dateDifferent, revert, or any of those options affect the behavior of a filelist deployment (that's why they tend to be faster than other styles of deployments)

From the DTD, that does not seem to be the way is *should* work, however with Lilley's testing, that still seems to be the case.

Adam Stoller

From the DTD, that does not seem to be the way is *should* work, however with Lilley's testing, that still seems to be the case.

I'd consider this one of those cases of omission in documentation.

Filelist deployments are intended to be simple and fast, where you explicitly instruct OD to deploy a given list of files and thus there are no comparisons performed:

Perhaps some IWOVian will pick this up and get it entered as a doc-bug or some such.

nipper

Yea once I actually do read the DTD & it is wrong. See if I ever do that again. Smiley Very Happy

Adam Stoller

Yea once I actually do read the DTD & it is wrong. See if I ever do that again.

The DTD isn't actually wrong - it's not a violation of the DTD to include a permissionRules clause in a filelist deployment - it's just that the application doesn't look at it in that case.

Since the filelist is specified in the <source> clause and the other rules are specified in the <target> clause - I don't think you can easily define that kind of conditional dependency via the DTD.

Tanuj

Guys i know this is a very old dscussion. but with these new versions of open deploy is there anyway to use filelist based deployment but still only deploy the file which are new.

Thanks

Tanuj

Adam Stoller

Guys i know this is a very old dscussion. but with these new versions of open deploy is there anyway to use filelist based deployment but still only deploy the file which are new.

Thanks

Tanuj

As far as I know - no. A filelist is presumed to contain the list of all files (or deletions) to be deployed without requiring further processing to determine if they should or should not be deployed.

If you want to build your own pre-processor to OD to take the list and filter out all the non-modified files, thus creating a new list, and then invoking the file list deployment with that new list - go ahead - it shouldn't be that difficult to do.