| Jean-Christophe Morin The problem with my code is that I was mainly targeting declarative pipelines when the warning plugin was used as a post step. It mostly works but, the violations in the lists have a full pathname and I couldn't find a good way of stripping this off as the post step at the point I implemented has no way of getting the workspace. Another problem is I started writing it in a functional way, which probably has to come out. I though maybe a better way would be to have a standalone plugin which can reprocess the build/job/<job>/branches/<branch>/builds/<num>/xxx_<outstanding|fixed|new>-issues.xml files I haven't progressed this yet other than a bare bones plugin but again the entries have a full path as per the workspace where it was created. There is another jenkins github plugin which can write to PRs from the pipeline (maybe there's a similar BitBucker one?) https://github.com/jenkinsci/pipeline-github-plugin#reviewcomment Feel free to lift anything out but I really do need to start again |
