Raspberry Pi 4B and Gitlab, part 1

RE: Raspberry Pi 4B and Gitlab, part 1

koudelad — Mon, 30 Sep 2019 06:41:19 GMT

Thank you, [mention:d85999949f974a74a457e05151ea1c2b:e9ed411860ed4f2ba0265705b8793d05] and [mention:d214a0a0f5594ee19515b2a3782e7070:e9ed411860ed4f2ba0265705b8793d05] .

For my hobby projects, I also previously created a zip archive for every version. I used only a few source files and it was somehow manageable.

I also have an example where the device manufacturers can make life much harder:

A few years ago, I started playing with PSoCs and their IDE, the PSoC Creator. There is no built in version control system (VCS) support, so I stuck with zip archives. One part of a PSoC development is creating the component structure in graphical editor. (Here is an example from PSoC ultrasonic range meter ):

[View:/resized-image/__size/490x360/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-f56e081c-e01f-4b3b-8f43-dcb5bf21c82d/3362.contentimage_5F00_204668.png:490:360]

Later, during compilation, tens or hundreds of source and header files are generated. If you want to fully control your source code and have the ability compile the code later without the IDE, you need to have the files in one pack - but there are also other non-source files, which are unnecessary to version as they only clog the repository (because they change every compilation).

One solution was zipping the entire project. The other is use VCS without the connection to the IDE, which is what I recently chose. If you want to know see more, have a look at my post, just see the .gitignore file. Version control in PSoC Creator

When starting with version controlling, it is always a bit painful transition, but it pays off. Gitlab or similar SW / service can help a lot.

I will insert a link in the next part, but a key factor to success is discipline, good tool set and a good branching model. Many companies use this one: https://nvie.com/posts/a-successful-git-branching-model/

I hope I will get to writing a next part soon, but we are doing a small reconstruction and redecoration at home.

RE: Raspberry Pi 4B and Gitlab, part 1

genebren — Sat, 28 Sep 2019 15:37:39 GMT

Great blog! This is definitely something that I should learn more about. Back in my early days of Unix, RCS was such a useful tool. As I moved into the world of development on DOS, all of the early clones of RCS were very flaky and I lost more code than I saved, leaving me very leery of these clones. Since then, I have reverted to saving sources for each version, but I really need to rejoin the present and find a better solution. Thanks for the push in right direction.

RE: Raspberry Pi 4B and Gitlab, part 1

14rhb — Sat, 28 Sep 2019 08:43:57 GMT

A great blog, thank you [mention:00dfb01ff12548938b4b7669fc69e778:e9ed411860ed4f2ba0265705b8793d05] . I hadn't heard of Gitlab before but it makes absolute sense allowing better remote working in teams I guess. I'm looking forward to your follow on blogs.

I've recently started to get into using git and really like the way you can jump back and forth, create branches and highlight all the differences. I used to just keep saving the files as new versions but that started to become awkward when IDE manage the whole project and you aren't always sure where the files are. I also know just enough git to be dangerous to my projects - I've managed to add so much as to make them almost break or have got lost as to what branch/revision I should be in. But like most things - practice and application always help the learning....so onwards [View:/resized-image/__size/16x16/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-f56e081c-e01f-4b3b-8f43-dcb5bf21c82d/contentimage_5F00_1.png:16:16]