I use ReAkh to trigger builds across two Jenkins environments. Each one has around a dozen Git parameters, different branch naming rules, and separate version numbers to keep track of. Before, I'd always have to stop and double-check whether a branch needed the origin/ prefix, make sure I wasn't reusing a version number, and verify I was in the right environment.
Now I usually just tell ReAkh which branches I want to build. It handles the Jenkins login flow, CSRF token, parameter formatting, and build request automatically. If something fails because of a temporary network issue, it normally retries on its own, which saves me from watching every request.
One thing I didn't expect is that it keeps track of the workflow over time. For example, once we figured out that one Jenkins instance requires the origin/ prefix while the other doesn't, I haven't needed to explain that again. We've also run into occasional 504 errors from Gitee, and it generally retries without me asking. After using it for a couple of weeks and running around 30 builds, the repetitive parts of the process have mostly disappeared.