reform VS terraform-provider-jenkins

I wrote a simple tool that my company let me OpenSource called reform (Seamless Plug). I have a dir called configs that has a subdir for each env {dev, stage, prod, global} in it. I also keep a dedicated git branch per env {dev, stage, prod, global} so i can do R&D in dev. Once I verify it works right I merge to stage.

Personally I manage and create my jobs manually in jenkins, but terraform does have a Jenkins provider https://github.com/taiidani/terraform-provider-jenkins to allow you to create your jobs via IAC (Infrastructure as Code) if you want to be 100% IAC. This has been a very successful solution for out team. I must give a disclaimer though, while we have jobs to build & deploy all of our apps from src, we generally rely on CircleCi for it. We keep the jenkins build jobs up to date and only use them when CircleCi is down (Which has been much less the last year). In addition to that we (the devops team) use jenkins to run all of our repetitive tasks like a fancy cron service. Things such as reset dev databases, backup or github repo to a second location, run password rotations, recycle services etc.