We have deployed an application in our test environment and in our production environment with a few thousand files. For most of the files (Java class files, voice binaries, etc.), a simple CRC comparison is enough, and I know how to make that work.
However, there are some text files that have normal differences because of varying environmental configurations. For instance, I want to compare all the *.properties and *.jsp files in the two environments and (since I know some MUST be different) see the actual text differences between the files. The time stamps and sizes and CRCs of the files are irrelevant because I need to see the ACTUAL TEXT differences between the left and right files. If the left and right files are the same, a line in the output file saying that they are the same is sufficient -- or nothing for all.
For example, if the LogPaths.properties file in the system test environment has a line that reads "\logs\test\flatfile.txt" and the LogPaths.properties in the production environment has a line that reads "\logs\prod\flatfile.txt", I know that this is a valid difference. When I see it in the output file, I will disregard it. But if other text differences for these two files show in the output file, I have a discrepancy I need to repair.
I want to completely automate this process. The list of differences should go into to a text file, interleaved. I absolutely do NOT want to do this by running the GUI because that takes too much time. Also, the output file is something I can include in my online release notes to show the exact differences between test and production environments.
However, there are some text files that have normal differences because of varying environmental configurations. For instance, I want to compare all the *.properties and *.jsp files in the two environments and (since I know some MUST be different) see the actual text differences between the files. The time stamps and sizes and CRCs of the files are irrelevant because I need to see the ACTUAL TEXT differences between the left and right files. If the left and right files are the same, a line in the output file saying that they are the same is sufficient -- or nothing for all.
For example, if the LogPaths.properties file in the system test environment has a line that reads "\logs\test\flatfile.txt" and the LogPaths.properties in the production environment has a line that reads "\logs\prod\flatfile.txt", I know that this is a valid difference. When I see it in the output file, I will disregard it. But if other text differences for these two files show in the output file, I have a discrepancy I need to repair.
I want to completely automate this process. The list of differences should go into to a text file, interleaved. I absolutely do NOT want to do this by running the GUI because that takes too much time. Also, the output file is something I can include in my online release notes to show the exact differences between test and production environments.
Comment