Jenkin job at https://dispatcher.drupalci.org/job/phpstan/ is failing

As per @Mixologic a week or so ago, that is not easy to fix due to Debian changes around how PHP versions are used. He is working on an entirely new solution that at the time he said would be available in a month. So that would be in 3 weeks at this point I think. I would love if that would work and we could track how contributed modules are doing and where people can help best.

Also needs moving to the Drupal infrastructure queue, not sure where exactly.

I may have mentioned this in slack at one point, but the plan is to remake this job so that it can run inside of a docker container so that when we have k8s up and running we can run the job there.

But.. we do not have to wait until k8s is up and running. We can get the job up and running inside of docker _first_. The current debian jessie ami has docker running on it, so we should be able to start up a docker container and run the job within the container, instead of running in on the host OS.

This isnt something that is dependent upon the drupal infrastructure to do, and would be pretty great if @tedbow or anybody else could have a look at running the scripts inside a container. Then the job that runs on the outdated AMI itself can be something as simple as
"docker run containername" and copy out the results to the jenkins workspace.

This finally ran on its own, unattended last weekend.

For reference, the actual fixed job is at a new location https://dispatcher.drupalci.org/job/project_analysis/