![Git Tip: Find All Changed Files](/content/images/size/w600/2024/06/Screenshot-from-2024-06-20-13-12-47.png)
How to
A collection of 69 posts
![Git Tip: Find All Changed Files](/content/images/size/w600/2024/06/Screenshot-from-2024-06-20-13-12-47.png)
![Approvals New Features - Date Scrubber and Custom DiffTool](/content/images/size/w600/2024/04/image_2024-04-17_112413946.png)
![Approval Testing For LabVIEW 2.0 Released](/content/images/size/w600/2024/02/Screenshot-from-2024-02-29-16-02-18.png)
![A block diagram showing a setup for using GitLab CI to spawn KVM VMs on demand.](/content/images/size/w600/2023/12/KVM-Executor.png)
![Spawning VMs like Docker Containers](/content/images/size/w600/2023/11/bees-7164148_640.jpg)
![Compressing KVM Disks for Win10 VMs](/content/images/size/w600/2023/11/Screenshot-from-2023-11-15-17-41-22.png)
![SSH Server on Windows 10](/content/images/size/w600/2023/11/image-5-1.png)
![Publishing AntiDoc Documentation using GitLab Pages](/content/images/size/w600/2023/07/Screenshot-from-2023-07-31-12-49-52.png)
Publishing AntiDoc Documentation using GitLab Pages
I just discovered GitLab Pages recently. It has been around for a while, so this may not be news to anyone, but I'm sure it's news to at least one of my readers and I've found a somewhat novel use case for it, so I decided to do a blog post about it.
![Git SubModules and GitLab CI](/content/images/size/w600/2023/05/Screenshot-from-2023-05-29-23-06-15-1.png)
![The Absolute Easiest Way to Setup LVCompare and LVMerge](/content/images/size/w600/2023/01/lvdiff-min-1024x576.png)
![A LabVIEW Block Diagram showing the use of the Python Node to call some Python Code. The python code along with the ruselt is](/content/images/size/w600/2022/11/2022-11-16_11-02-52.png)
![Using Git Hooks](/content/images/size/w600/2022/11/image_2022-11-08_141748607.png)
![Latest Version of Git Broke LVCompare Usage](/content/images/size/w600/2022/07/image-1.png)
![Build License Track](/content/images/size/w600/2022/06/Screenshot-from-2022-06-07-17-09-17.png)
![More GitLab Runner Troubleshooting Tips](/content/images/size/w600/wordpress/2022/01/clear-runner-caches-4.png)
More GitLab Runner Troubleshooting Tips
I’ve been writing a lot lately about Continuous Integration and using GitLab Runner. It’s really nice when it works and it works 90% of the time, but issues do pop up occasionally. They can be a pain to troubleshoot. I previously wrote about how to run GitLabRunner as
![Checking for New GitLab Releases](/content/images/size/w600/wordpress/2021/12/GitLab-Autoversion-5.png)
Checking for New GitLab Releases
In my previous posts, I talked about automatic versioning and automatically creating releases. The next step is to create auto-updating code. By auto-updating I don’t mean code that automatically updates behind your user’s back ala Windows 10. You can do that if you want, but I believe the
![Automating Gitlab Releases](/content/images/size/w600/wordpress/2021/12/image_2021-12-06_170052-5.png)
![Automatic Versioning](/content/images/size/w600/wordpress/2021/12/Versioning-Ideal-6.png)
Automatic Versioning
At the GLA Summit recently minted LabVIEW Champion Felipe Pinheiro Silva gave a 7×7 on versioning. It was interesting. Be sure to take a few minutes and watch it when the video is released. I do things slightly differently. I learned my method from another LabVIEW Champion, Stefan Lemmens.
![How I use Test-Driven Development (TDD)](/content/images/size/w600/wordpress/2021/09/Example-Test-5.png)
![Trouble Shooting GitLabCI](/content/images/size/w600/wordpress/2021/08/image_2021-08-30_213638-5.png)
![A case for sets](/content/images/size/w600/wordpress/2021/04/image_2021-04-27_172742-5.png)
A case for sets
Back in LabVIEW 2019, NI introduced both sets and maps. Maps became immediately popular. They should be. They are very useful constructs. However, sets seem to have gotten much less attention. In some ways, they aren’t as glamorous, but they do offer some advantages over arrays. To me, these
![A Better Way To Set Up LVCompare and LVMerge](/content/images/size/w600/wordpress/2021/04/image_2021-04-19_172222-5.png)
A Better Way To Set Up LVCompare and LVMerge
EDIT: Since I originally wrote this post, I have come up with a much easier way. I am leaving this post up for historcial reasons, but do yourself a favor and just go here
I have previously written about setting up LVCompare and LVMerge. I ran into a situation where
![Quick VI Analyzer](/content/images/size/w600/wordpress/2021/04/image_2021-04-16_134222-5.png)
![GitLab CI and Git Bash](/content/images/size/w600/wordpress/2021/03/image_2021-03-22_103740-5.png)
GitLab CI and Git Bash
A while back GitLab CI deprecated the batch executor for Windows runners. That meant that you could no longer directly call batch scripts from a Gitlab Runner. They had switched over to Powershell. There were workarounds. You could still write a batch script and call it from PowerShell using cmd.
![Unit Tests for PPLs](/content/images/size/w600/wordpress/2021/03/image_2021-03-14_221505-5.png)