After using most CI/CD tools I can tell you that for your tech stack there is no reason to use Jenkins. It sucks, typical Java software that looks like shit, ha

After using most CI/CD tools I can tell you that for your tech stack there is no reason to use Jenkins. It sucks, typical Java software that looks like shit, has a buggy interface but somehow runs well enough to be "Enterprise ready". Go with Drone, you will thank me later. I would implement the CI pipeline first, write tests afterwards and make sure to integrate with Mattermost/Slack, which will make you aware if something is broken. I am currently on a Gogs, Drone, Mattermost stack and am loving it. Everything was super easy to setup and runs just perfectly fine for months now without me doing anything other than the initial setup. Jenkins was a pain in the ass and it was the best decision for me to get rid of it. The beauty of Go is also that it isn't using any resources, this is why I run Gogs (runs perfectly fine with 512MB RAM) instead of GitLab (you need 8GB+ RAM).