Since the JJB deployment job runs directly on the Jenkins master, we've been creating and using an RPM package for JJB. This made it hard to switch JJB versions.
Once we implement OVIRT-1465, we gain sufficient isolation via mock to allow ourselves to install JJB via pip.
We can set things up so that pip installs a specific JJB version, that way we can gate JJB version updates and have then checked by check-patch. We can even expand the upstream polling system to track JJB versions for us and create update patches.