CI/CD

Manually releasing a Maven package is a hassle—updating versions, tagging commits, building artifacts, and pushing them to a package repository. What if you could automate all of this with a simple Git push?

With GitHub Actions, you can! In this guide, we’ll walk through setting up a workflow that automatically builds, versions, creates releases in GitHub—no manual steps required.

By the end, you’ll have a fully automated release pipeline that:
✅ Uses GitHub Actions to trigger releases
✅ Handles versioning and tagging seamlessly

All software developers have to deal with it. Version control software. Today I decided to play a bit with installing my own dedicated SVN (subversion) server. This, hopefully brief, step plan will help you do the same.

Downloading all needed software

Before you can continue with the tutorial you will have to get the following things:

• A ‘virtual’ computer to install you dedicated SVN server on,
  I used VMWare to emulate a server, but you could also use an old computer that you have as a spare.
• Download Debian from http://www.debian.org/devel/debian-installer/,
  The reason for picking Debian is easy. It’s supposed to be a stable and powerful Linux OS. (You can pick the netinst CD image)

That’s all you will need. But be aware that we will be downloading various other packages (software applications) later on. So make sure you have your network prepared.