Re: Opening Plugin Compatibility Tester

Hi, Just to bump the threads. As a part of JEP-200 I needed to run PCT against a number of plugins recommended in the installation wizard. I spent some time studying PCT and finally created a pull-request with the documentation update and Docker image. It should simplify the custom PCT runs.

Re: Opening Plugin Compatibility Tester

Hi Oliver, As Jesse comments: - We are trying to be as clear as possible on that kind of PRs, so that both the problem and the fix can be understood and acknowledged by the maintainer and whoever might evaluate such PR. - It's not easy to directly translate what we are doing

Re: Opening Plugin Compatibility Tester

On Tue, May 9, 2017 at 4:11 AM, Oliver Gondža wrote: > a PR that purports to fix > something you have no evidence of being broken referring to a TLA-named > testsuite you have never heared of and have no easy way to checking for > yourself FWIW I have asked people filing such

Re: Opening Plugin Compatibility Tester

that is strange, I remember copying something from a freestyle job on one of the Jenkins project's masters for the initial draft of our internal PCT job. But I think it was disabled at the time probably due to it being flaky and using up too much resources for the project. Perhaps it got lost in

Opening Plugin Compatibility Tester

Hi, For a period of time I see several people from CB contributing to PCT itself and addressing problem in plugins pointing out PCT related problems. However, last time I checked, I have not found a compelling documentation on how to run it or any public Jenkins job where people can check