James, I have a PR open to address the Jenkins job failing here but there is an issue:
https://pagure.io/fm-orchestrator/pull-request/78

So for some reason, I'm able to run the Jenkins script locally with success on this branch, but the build still fails when it's in Pagure. The console output of the build seems to show that Jenkins is not running Docker, it's just trying to pip install from a virtualenv. Any ideas?

I don't think jenkins jobs have access to docker, virtualenv is the recommended way to get stuff installed for the jobs.

@james: hmm ok. If that's the case, do you know why there's a file called jenkins-check-Dockerfile?

Anyways, the reason why the build is failing is that a dependency is missing to be able to install the python dependencies in requirements.txt. Can we install the dependency on the Jenkins builder if we can't use Docker?

Commit message here suggests that it is so that you can run the tests locally in docker in a way that is "roughly how jenkins does it": https://pagure.io/fm-orchestrator/c/d809d34ed7547bfcee2ec76dba3e3feecdd2a5e4

Yeh, the idea being that developers have a lot of random extra things installed than are on jenkins ... and that should be a much cleaner thing (and thus. if it passes it's likely the jenkins build will pass, this was before the auto CI builds).

If we need something else installed that we can't get via. virtualenv, then we'll probably need to open a ticket to get a jenkins admin to install it.