Migrating from Jenkins to Github/Gitea Actions
I wanted to title this post Tea and Tears and Github Actions This experience was truly traumatic. Let me first clarify my environment and what I was trying to do, then let me break down what I learned and how you can (hopefully) do it too. I am using Gitea . I have been a big fan of Gogs for years, and recently migrated to Gitea, a fork of Gogs that includes artifact management and CI/CD via a Github Actions compatible interface. I have lots of different types of CI/CD builds. I am a polyglot of coding languages, working in many different styles and patterns. I currently use Nexus for artifact management, and Jenkins for builds. A simple Build I did not start with it, but the first build I got working on Gitea was hardly a build at all. I have a static site built with Hugo for a charity. Let's start with my Jenkins version of code: def remote = [:] remote.name = '**name**' remote.host = '**ip**' remote.user = '**username**' remote.allowAnyHo
