Chaitannyaa Gaikwad It was my second job, and after the main team left who managed Jenkins among other things (and who were exceptionally more senior and advanced than I was), I found it incredibly complex to use as a beginner developer versus something like TravisCI or now GitHub Actions. Because of this complexity, I opted for simpler and easier solutions ever since.
First off, in my first few years of development, I wasn't smart as you to take the time to learn Jenkins. But your tutorial has made me want to revisit it again. So I'm sure I'd be learning from you!
If I were to use it again, I'd use it to split my CI from CD solution. So I'd continue with GitHub Actions for CI to build an artifact, like a containerized image or zip. Then I'd use Jenkins for CD, allowing non-engineering to trigger deployments and move releases through a QA->UAT->pre-prod->production pipeline using a nice GUI interface. I know this can be achieved through GitHub Actions (especially their higher-tiered versions), but with cost-savings, Jenkins now looks like a good solution.