VSIP Client needs Check-In on Solution Close

[neal007]

I prefer to check-in everything when the solution closes and I expect the same of the other devs on my team to prevent exclusive lock issues, merge issues, etc. MSSCCI offers this, it is a MUST in my opinion. Please put this on a priority list, I'm curious if others agree that this is a high priority requirement, second to bugs/critical issues.

[rshillington]

I'm not sure how check-in on solution close would solve exclusive lock issues. Furthermore, I don't see how having incomplete code in the respository can be good under any circumstances. I like to know that when I do a get lastest I'm not getting something that's half baked.

Now what I do think would be great is a shelving, ala TFS.

Regards,
Ralph Shillington

[mserfass]

We use unit tests, continuous integration, and automatic scheduled builds. So on our team it is a rule that code that does not build and does not pass unit tests is not checked in. Automatically checking in when a solution closes would make it much easier to have the continuous build process fail. And nobody wants the whole team alerted that their code is bad.

At the same time, more options are usually good. A tool that is adaptable to how a person or their team works is really nice. I vote for adding the auto-checkin feature and have it off by default. Shops that require checkins at the end of every day are not uncommon. I think incomplete and broken code in the repository is a bad thing, but I can understand not wanting code checked out to someone indefinitely. (Has anyone not had the situation of having to change code for another developer on vacation and realizing that it's checked out to him?)

BTW, Vault and Fortress do have settings for turning off exclusive locks. Also, the admin tool also lets you undo someone's checkout.

[Beth]

neal007 and mserfass: I'll add a feature request in for the option in the VSIP client as well.


rshillington: We had an open feature request for shelving. I added your "vote" to that feature.