On Thu 16 Aug 2018 at 15:10 +0200, RonnyPfannschmidt wrote: > Im fine with any other proposal that sorts out the breakage dimensions > to be expected
Is this the problem where junitxml changes slightly in a new jenkins release and fixing it requires an update to the plugin? At this point users will either have to not update jenkins or update the external plugin or update all of pytest if the plugin stays internal. I don't think the release cycle of pytest is so slow there is a major benefit to moving it external for this? Given that IIUC Rusty is proposing the plugin would be able to generate older incompatible versions (e.g. with --junit-version=x) this would work AFAIK. Happy to hear where I'm wrong though. (I'm kind of +1 on Bruno's opinion of keeping it in the core btw, we should enable ppl to easily contribute to junitxml in the core which I believe our current contributing policies do) Cheers, Floris _______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
