Why trigger something remotely (using Jenkins) and then just forget about it?
I wouldn't describe Jenkins jobs as "fire and forget."  They are designed to run automatically without the need for human interaction, however, that doesn't mean the result of a job is not visible.  Quite the opposite- detailed logs of all activity are available for jobs ranging from command-line tools to custom deployment jobs.

The testing results from Jenkins jobs are routinely displayed on large-screen TVs all over the Development floor of many companies I've seen.  There are whole plugins devoted to making this type of information available to developers, Ops, and management in a dashboard format.