You can't rely on a developer to manually check it in because they can check in the load module and the source module from a directory other than where they checked it out from.
Regards,
Paul Perry
Paul,
The number one way is when the source code is built is it correct. Did it build correctly and is it functioning as designed and according to the requirement specifications.
For me personally I actually train my developers to check in code from wherever they want to. However, I warn them, it has to be able to be built, if not I will tell them to fix it. A few times of doing this and not meeting schedules if applicable should take care of any cowboy coders out there.
Regards,
Joe
Joe - Thanks for your reply. Yes it has been properly built and executes according to specs. However, we do not use Builds nor Make files.
In your example, it seems as though you are relying on the developer to check in the source that created the executable, that is also my situation. However and as you mentioned, I to allow my developers to check out their code to whatever location they need, but, that doesn't mean when they check the source back in, that it comes from the directory where it was check out to.
Example. We had an upgrade and the developer checked out the production copy of the source code and renamed it within his directory.
When he created the load module, he created it under the production name, which is fine, and checked that back into PVCS, but never checked in his source.
Problem I have is, I'm out of sync between source and load.
Paul
Paul,
Unfortunately there are no tools on the market to make developers behave correctly and do the right things. Your only option here is to shame the developer into doing the right thing. That's an unfortunate step you may be forced to take, but it may be your only option, unless you volunteer to check in the code for him. This, however, can result in the issue being repeated because good ole Paul will always check in my code for me now.
I would personally take another route before exposing them to upper management, I would go ask them if they forgot to do something with the code on that last build that went to production. If this problem is not fixed soon it could get ugly, especially if someone checks out Prod thinking his code is in there.
I am assuming that the load is a derivative of the source code.
Regards,
Joe
I've seen this sort of thing solved by using a non-development build team ('CM team') for 'official' products.
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.