Hi,
What is the best strategies to add a FB project under source control.
With the built-in option or via the source control tools.
I also want to know what is undersource control with the option, how it is working, do the logging file is under source control? when a scheduling build is running does the check out and check in are done automatically?
thank you
Alexis
Hi Alexis,
The built-in source control integration does not check in the log file, and we do not recommend that log files are checked in. Log files are large binary databases, which are not handled well by version control systems. Also, the log file has to be read-write before a project can be opened.
If you want an incremental build log to be kept inside Source Control, I recommend that you use the Export Log action to export an XML log, and then check it in to source control, both as part of the build process itself. If you put this into a Finally block then it will run no matter whether the build succeeds or fails.
You can find options for automatic checkout and checkin of projects (and other auxillary files) under Tools -> Options -> FinalBuilder -> Source Control Options. By default, all Source Control integration is disabled when running a scheduled build. This is because SCC plugins will sometimes pop up modal dialogs, and there is nothing we can do to suppress them. There is an option to enable source control when running unattended, if you know that it will not display modal dialogs.
Hope this helps.
Regards,
Angus
I join my clearcase config.
I tried to have a project under source control with files .fbv and .fbd but after each build the .fbv is not changed.. i didn't check for the .fbd but maybe its the same thing. It will changed only if the .fbv file is checked out so when the scheduler run it doesn`t do all the job. I should put actions to check out file.. and check in
Is there an other alternative?
Other question, when using a project under source control there are options for projects under source control... which have "check out on open" and "check in on close". For the check out on open.. it works well but on check in on close.. if the file has not changed i get an error, and this error is normal... in clearcase when you check in a file that is identical with the previous one, you get an error, except if you check the option "Check in even if identical to previous version"
Is there a work around?
Hi Alexis,
I’ll attempt to fix “check in on close” so that it doesn’t give you an error. Each SCC plugin is just a little bit different in how it works!
I’m a bit confused about the other issue you raised, but here’s a stab at a workaround:You can check the “Keep non-project files checked out when checking in” box, which means that these files are always kept checked out, even though they are incrementally checked in to source control.
Hth.
- Angus
Hi Alexis,
One more question - do you know if you still receive an error from ClearCase if you try to check in a group of files, some of which were modified but some were not?
Regards,
Angus
Yes i understand that each SCC are different.
Yes with clearcase when i do a check in of a group of file, i get errors for the files that did’nt changed and the others are checked in.