One thing I wish was embraced more, and not just by users but also platforms such as GitLab is re-usable actions, or workflows if you will. As they help spend less time away from your primary project. Also, containers. ...
Using distrobox containers for development makes it super easy to separate one or more development setups from the host system. I got used to setting up a container with a different image while still having my user and tools setup as I’m used to. It’s one thing to spin up a container to test out a difference between SUSE Linux Enterprise and Tumbleweed, or see how Ubuntu behaves in a certain case. Having your shell setup as you’re used to reduces disruption in a different environment, and you already have access to the repos you work with, too. ...
As an avid container user and occasional distro hopper Distrobox has my interest peaked. ...
Download audio The mess that is a development setup You might be running something like openSUSE Tumbleweed, Leap or MicroOS for your day to day development. Traditionally the workflow involves installing all sorts of tools you might need, enabling fun development repos like devel-perl or app-specific repos and tweaking the system configuration to your liking. Sooner or later you will learn about the existence of --allow-vendor-change and how priorities work....
Download audio I want to develop openQA openQA is a framework to run system-level tests that is used for openSUSE, Fedora and others in a way that uses a serial console or mouse and keyboard input to interact with tests. No support from the software toolkit used is required to make this work. For the purposes of this article I’m going to assume you have a basic idea about openQA....