April 14, 2020 at 9:04 am
Hi all, doing a bit of a check to see if we have ticked all boxes before moving from TFS to BitBucket.
We use VS 2013 (due to legacy SQL server instances)
Our senior developer wants us to be able to have a full single check out at the project level rather than the solution level. I am not really sure it is possible.
As I understand it, we would each have to check out a branch of the repo in our local drive and then we would merge those branches back into the main repo when the work is completed.
This method wouldn't stop the same project being altered by 2 different devs at the same time so I am not sure if I have missed the point here.
Any advice gratefully received.
Dave
April 14, 2020 at 12:50 pm
Firstly, I think it would be slightly more accurate to say that you are moving to using Git as your VCS, with BitBucket as your cloud-based code-management solution.
Is the dev in question suggesting that projects become 'locked' as part of this 'full single checkout'? This sounds more like VSS than Git to me.
There is not a great deal of point in doing this. Solution files rarely change – they are essentially a list of the projects in the solution and not much else.
The projects and project files themselves are a different matter. You need to be very careful if there are two or more developers working on the same project:
Making (1) work is not a technical issue. The development team needs to be managed and coordinate such that it does not happen.
(2) is fine, as long as the developers have the requisite skills.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
April 15, 2020 at 8:07 pm
Hi Phil,
thanks as always for your constructive reply.
Yes we are moving from TFS to Git with bitbucket. I have today found a way to at least lock files using this set up.
It requires the Git LFS Client and if you aren't comfortable with command line work, then something like SourceTree as a GUI on top of it. I am acutely aware that Git/Bitbucket don't natively allow single checkouts and they are designed around Branching and Merging but our business is really trying to get all dev teams off TFS. Our Senior Dev thinks single checkout is the way we should go and wants to really investigate Git/Bitbucket does what we need before she signs off on us using it.
I found an issue with the setup i explained above though. When you lock a file using Git LFS there is no issue but when you unlock it after committing your changes, it sets the file to read only in windows file explorer and you have to manually change it. I am wondering if that is a bug or for some strange reason by design. Any ideas?
Cheers,
Dave
April 15, 2020 at 9:38 pm
Seems like you are trying to bend Git to work in ways it was not conceived for. Maybe it's not the right choice in your organisation.
Just so I understand what is driving this, can you explain the perceived benefits of working the way you have described?
Note that there is no technical reason why you should not phase your migration to Git (eg, one solution at a time). In fact, that may be a better way forward, so that the more VCS-savvy among you can become acquainted with the new way of working so that they are confidently able to help the others recover from the inevitable problems that will arise when they start using it.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply