I guess I figured that it would be the responsibility of the plugin to figure out what the job name should be given the repo, branch and commit.

Reason being that if you have travis building your PRs then there is no jobname - the appropriate plugin would need to query github's api for the status of the given commit and return that.

But if we want to enforce conventions then in the case where it's querying a single jenkins job it does make sense for this to take some extra conventions fields. But perhaps that can be encapsulated in **kwargs and added to the configuration of the appropriate plugin.