While writing my previous post, I hit a frustrating issue. After saving a large chunk of the draft, it appeared that hugo wasn’t rendering the new additions. I verified on several computers, including fresh installs. None of them would generate the updated post, despite the source files containing the changes. Ugh.
Earlier this year, I noticed that my desktop seemingly did not connect to my
monitor. I used the computer mostly as a server, remoting in via
didn’t think much of it. I assumed it was either a mis-plugged cable or a
configuration issue. A few months later, I started to game a bit more and
wanted to use my desktop as a gaming machine again. That is when I realized…
it was an actual issue. Long story short, my desktop now has an rx580 instead
of it’s old rx560.
A month ago, I drafted a progression of examples with notes, to teach a co-worker the basics of writing and using ansible roles and playbooks. After reading through them, I realized it wouldn’t take much to turn them into an actual Ansible quickstart post. So here we are.
Several weeks ago I attend TSQA 2020, a conference presented every two years by the Triangle Software Quality Association (TSQA). Despite being hosted by my local software testing group, the speakers and attendees were from all over the country. While only a single-day conference, it was packed full with solid advice and ideas I left with. Here are a few.
Okay, quick post! Previously, I wrote about how I automated my website
tests using Jenkins. When I wrote that post,
I had the tests run on
any node. I wanted to have the tests
run inside a fedora docker container, but ran into issues configuring it.
With the problem now long fixed, I decided I would write a quick update post about
switching the pipeline to use container nodes.
In my previous two posts, I created a test framework for my website, and automated it using Jenkins. But we can do better. One of the most annoying things when maintaining (or even reading) something on the internet, are broken links. While I cannot control the availability of content outside the website, I can choose to remove links if they are broken. So, in this post, we will add tests to ensure that links in our posts are working. Well, at least the markdown ones.
In the last post, I setup some simple
testing for my website builds to that ensure that pages were being served
correctly. However, I can’t trust myself to always manually run the tests
before merging a branch into
master. Luckily, I have
Jenkins to take care of all the “responsible” tasks. In
this post, we will take the test framework created in the previous post… and
As this website grows, there is an increasing amount of complexity. More posts,
more images, and more links. I’ve gotten better at breaking work up into
separate branches (instead of pushing everything straight to
even that isn’t enough to ensure everything works as expected when publishing
something new. Then, I thought of something obvious… I could setup some
simple testing… for my website.
After buying a 16” MacBook Pro the other month, I’ve been using a Thunderbolt 3 hub to connect it to my periphery devices. Luckily, in addition to the macbook, I am able to use the hub with my my work laptop when working from home. Normally, it works fine. However, last week I reformatted the work laptop with the KDE Plasma spin of Fedora Workstation 31… and my TB3 hub stopped playing nicely with it. Here’s why.
In my previous post, I mentioned that I had purchased a new 2019 16” Macbook Pro by the end of my macOS challenge. I have had the laptop for over a month now, but I made sure to take notes on some of my initial thoughts during the first few days. Here are those thoughts.