General questions about doing a daily build with MKS

I was very excited to see that FB 5 included MKS support because our shop is in the process of switching from PVCS to MKS.

However, I am a little bit (OK, a lot) confused on how I shold convert my builds to use MKS instead of PVCS and was wondering if someone could steer me on the correct path.

In my PVCS builds, I would label my current PVCS revision, then run a GET command to get the latest version into a working directory and then compile my programs from that working directory.  When using MKS, should I issue a checkpoint?  Will that have the same effect as a label & then a GET?  What are the best practices here?  Also, our company has decided NOT to turn on the change package feature, so I know I can't use that.

Also, on the MKS actions I don't see any place to specify the project name.  Our MKS project structure is setup with multiple subprojects and I only want to build one of the subprojects, but don't see where I specify the subproject name.  Or am I just missing it?

As you can tell, I am very inexperienced with MKS and have really not been given any training, so I am using the trial and error method and it's slow going.

Thanks for your help.

Hi Paul,

> Also, on the MKS actions I don’t see any place to specify the project name

Most of the MKS actions will use the Sandbox path to determine which project to use when calling the MKS command.

Regards,
Paul Samways.

Paul,

Thank you so much for your assistance.  I appreciate it.

 

Could someone point me to some examples of a FB project for MKS?  Not having any training and very little support on MKS I'm flailing about and need some basic guidance.

 

Thanks