Does any of the "Deployment Automation Manager" tools make use of "export.log" file for versioning, package building or deployment to happen successfully?

Question

I don't want to store the "export.log" file, which is created when patch of objects is taken from Appian application and comes packed in the export patch ZIP file, in local repository(Git) as well as in remote repository(BitBucket) because BitBucket do not recommend to store the log files.

I would like to know the impact, if I store the application objects of export patch ignoring the "export.log" file in local repository and remote repository.

Does any of the "Deployment Automation Manager" tools make use of "export.log" file for versioning, package building or deployment to happen successfully?

kondetiv · Answer

"export.log" file nothing to do with version or deployment. "export.log" actually tells you what rules are exported successfully and what rules are not exported with their UUIDs and names. 
 
Suppose if the user is trying export 10 rules but only 8 rules are exported. You never know that patch is having 10 or 8 rules and what rules are exported successfully and what rules are not unless and until opening your log file. 
 
Anyway, whoever is exporting a patch they should make sure that all rules are exported successfully. 
 
Some times keeping a log file is a good idea but sometimes not in this specific case. 
 
Finally, it's your call.

kondetiv · Answer

Nowhere it will be used. As I mentioned earlier whoever is exporting it will be helpful for them. After exporting they can look into the export.log file for what rules are exported and what rules are not exported with the reason why they are not exported. Such a way that they can resolve the issues for unexported rules and export the whole package again.