I’ve now finally had the chance to test the new MKS actions and have come across a couple of problems, one of which has meant I’ve had to revert to my fb4 version of the project until I can solve it.
I run my projects via fbcmd with the log sent to a text file (in case this is relevant to the problems).
The first problem is with the Connect action - in the log file it is possible to see the user and password in plain text.
The second (and major) problem is with the Resync action. Basically I can’t seem to get it to work. The log has the following as an error message:
MKS Command: resync --batch --nomerge --filter=changed:all --noIncludeDropped --overwriteChanged --noOverwriteUnchanged --noOverwriteIfPending --recurse
Error executing Action : Failed to execute program. Error : The directory name is invalid
I noticed that there seemed to be no sandbox listed in the command params even though one was specified in the action so I tried again using the extra command line paramters option in the action inspector and had the same error message (although the command did now include the --Sandbox=“sandbox dir\sandox.pj” line.
If I tried these same arguments with the si resync command being run from a dos prompt manually the resync worked correctly.
If needed I have copies of the log file and the project.
Cheers
Paul James
Hi Paul,
With the Resync action, the working directory is set to the location of the sandbox, so their should be no need to add the --sandbox parameter to the command. Make sure that the SandBox Location is set to the root folder of the sandbox.
Regarding the passwords, make sure you are running the latest build of FinalBuilder as this issue has been fixed.
Regards,
Paul.
I’ve now worked out what the problem was with the resync action - I’d included the actual name of the sandbox in the ‘Sandbox Path’ property. If I removed this I then have an error because there are multiple sandboxes in the same directory however I can solve this by using the --Sandbox param to specify which of the sandboxes should be resynced.
I upgraded to the latest version of FB (as found by the check for updates, version 060) however the log file still has the passowrd in plain text. Is there a later version I should check?
Cheers
Paul James
I’ve also hit a problem with the Checkout action.
It seems to support a flag for marking something as work in progress however this seems to be an option not present in the version of MKS we actually use. Is there a way to not have this flag passed to the command? (if I just leave the box unchecked then a ‘noMarkWorkInProgress’ param is passed instead so that isn’t an option).
Cheers
Paul James
Hi Paul,
There is a setting in the MKS options page to disable MKS 2006 command line arguments, this will prevent the Checkout action using the WorkInProgress parameter.
The password issue is actually a bug, sorry I didn’t pick up on it earlier, I’ll put a fix in it for it and let you know when the new test build is available.
Regards,
Paul.
Hi Paul,
Here is the latest test build,
https://www.finalbuilder.com/downloads/finalbuilder/500/FB500_84.exe
Regards,
Paul
I’m still having problems with it even with build 84 - it now doesn’t want to connect at all.
I’ve tried to attached the log file and project I used for testing but that doesn’t seem to have worked so I’ll email them to support at finalbuilder dot com
Cheers
Paul James
I have been able to confirm that the disable MKS 2006 command line arguments option has solved my problem with the Checkout action.
Cheers
Paul James
Hi Paul,
Thanks for the sending the project, you should be able to get the connect action to work simply by re-adding it to the project.
Regards,
Paul.
I must admit I'd tried just about everything _except_ deleting the action and adding it again. Now I've tried that and can confirm its solved the problem.
Cheers
Paul James