![]() ![]() However, it's worth asking yourself why almost every experienced developer does this. This might feel disruptive to your workflow. Yet another thing to think about! After all, who wants to think more? Imagine having to constantly interact with source control by constantly typing little notes about the work you just did. If you're a solo developer who is used to clicking the "Save All" button on the project every few minutes, transitioning to a more thoughtful workflow where you are mentally keeping track of what you have actually changed and only committing those files is going to suck - to put it bluntly. There is likely to be more initial pain with Git. The major pain is just in the beginning while you're learning. Once you learn what you're doing, almost never. Eventually they learn it and the frustration subsides.ĥ. Git has plenty of horror stories written about it when people are confused in the beginning. Mercurial is a distributed version control system and seems easier to understand than Git, but that might be because I have used it more. It's difficult to give up the ability to easily create branches once you have it. Also, last time I tried to create a branch on Subversion, I vowed I would never try it again. However, your computer will require constant connection with the central repository. You mentioned wanting to use source control "within" LabVIEW and I think you can setup LabVIEW to work with SVN although I'm not doing it that way. Subversion might be the simplest for you considering it sounds like you don't want to be using SCC in the first place. I would prefer Git just so I was always using the one that everyone else in the world is using.Ĥ. I have no option but to love any or all of them because the alternative (no source control) would make my life a lot more difficult.ģ. Mercurial (with TortoiseHg), Subversion, Git (with Sourcetree)Ģ. But at some point someone may need to lock the whole project to update some large part of the code, and that is when going around and being like "Hey Brian can you unlock this I need it" would happen.ġ. When a developer is working on a subset of code, and no one else should be touching it, this works just fine. You can break the lock, but then you may have two version of the file and then need to figure out how to merge them. This means only one developer at a time can be editing a file. A single developer shouldn't need to worry about it (unless you are on multiple computers). ![]() One is Lock/Commit, and the other is Merge. Oh and there are two paradigms when it comes to SCC. Here is Nancy talking about some of its features. Here is the first package I found made by JKI that does some of this. There are LabVIEW toolkits that add quick drop, or tools menu, and project integration, but none of them worked with our work flow enough. The client side I just use the explorer integration that comes with Tortoise SVN. Jim had an old blog post years ago that I can't seem to find. I'm not sure what can be used to make a local repo. The free version does a great job, but the paid version has domain integration among other enterprise features. For multideveloper work we use VisualSVN Server. Just how often does your source control software screw up and cause you major pain? Pro's and Con's of the source control you are using?ĥ. Are you forced to use this source control because it's the method used in your company, but you would rather use something elseĤ. What type of source control software you are using?ģ. Since most of the posts I read today are from years back, I'm hoping things have really improved in the last couple years and you guys are happy as a lark with your source control environment.ġ. So I'm looking for source control that works flawlessly within LabVIEW and is easy to use, I'm Using latest versions of LabVIEW. But the project requires a more structured source control environment. I'm still the single labVIEW developer on a project. Or at least there are issues with just about every option. Seems nobody really likes source control after all. ![]() But thought I'd just read some posts, determine what everyone else likes and be done!!!!! That didn't work out for me ether. I've been programming LabVIEW for over 20 years in a single one technician lab and never really needed any stinking source control. So I spent much of the afternoon looking over postings here on Source Control Software and LabVIEW. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |