I've included the relevant shell script being used as well as the plugin settings. The JUnit plugin seems to be able to respond well to this shell script, but the same code doesn't seem to work for the html plugin. Unfortunately since the html plugin supports more robust data, I'm stuck with using it.
In the script, the file gets created in docker. I then copy the file to a new folder in what I'm guessing is the Jenkins workspace. From what I've seen so far it looks like the plugin expects a folder to exist and automatically uses the `Report Title` setting to do this. If no title is given, then it seems to use the file name as that new folder.
# copy report files from container to jenkins
CONTAINER_ID=$(docker ps -a --filter ancestor=$APP:$TAG -q | head -1)
docker cp "$CONTAINER_ID:/opt/repos/locus-web-dry-lab/pytest-report.xml" .
.mkdir -p './htmlreport' && \
docker cp "$CONTAINER_ID:/opt/repos/locus-web-dry-lab/pytest-report.html" "./htmlreport/pytest-report.html"