Our QA folks assure me that this wasn't the case a while ago and that the files in the ISO image would have the date/time of the actual source files. Not sure when this happened, it's certainly been this way for a year or more.
Any idea if this is a bug? I'd rather not have to run mkisofs myself to get this done, having the built in action is much simpler.
The Create ISO image action hasn’t changed since FB7 was released. FB7 does use a different api than FB6, it uses the IMAPI 2.0 api, which by default doesn’t provide any options for preserving the modification time of files when you add them to the image. I have found a way to do this and should have a new build available later today.
The build includes a new option to preserve file creation/modification datetimes :
http://downloads.finalbuilder.com/downloads/finalbuilder/700/FB700_2093.exe
Thanks for the quick response!
I presume this will be in the next patch release? Or would you consider the build you did releasable?
Just don’t want to put ‘beta’ software in our production environment.
The only changes in the build I posted are the change for the ISO action, and beta support for TFS2012 integration. We’ll most likely be releasing an official update either later today or monday, just waiting on feedback on the TFS2012 support. If you are not using TFS then the build should be quite safe (it’s now being used on our build server to build itself).
Thanks again for the quick turnaround. I can wait for the official build, things like this move a bit slow around here.
I downloaded and installed the above build, and it works fine locally. I then installed that build on our FB server machine, confirmed that it’s the only copy there. However ISO’s built from the same FB script I use locally (again, confirmed by checking what’s on the server) isn’t properly setting the file dates.
Anything else I need to do for FBServer?
I think I figured out the problem, it’s using the created timestamp which is being set to current by the SVN export (checkout does the same, at least from tortoisesvn). My initial testing used files that had a created timestamp = modified
I don’t believe svn support keeping the original file times. There is a setting (http://stackoverflow.com/questions/2171939/how-can-i-keep-the-original-file-timestamp-on-subversion ) that can be used to get the commit times, which might be good enough.
SVN preserves the modified time, however the created time is correctly set to the time the file is created. So you end up with created as the current date and the modified preserved from the originally checked in file modified timestamp.
The problem is the ISO creation is using the file creation timestamp, which I think is incorrect.
I think I may have found the problem, it looks like it is setting the modified time to utc and the created time to local. Running some tests now. It also seems like the IMAPI2 api we use ignore the modified time and just sets both the modified and created time to the same value (created time).
Please try this build :
http://downloads.finalbuilder.com/downloads/finalbuilder/700/FB700_2190.exe
It looks like the created and modified timestamps on the resulting ISO image match the modified timestamp of the source file(s). The works for us!
Thanks!
I presume the recent 2183 build does not include this fix?
No it doesn’t have the fix.
How come 2183 build doesn’t detect the update when you open it?
2190 was a hotfix build to fix a particular issue, check for updates only checks for the latest release build.