even test results are static in the sense that once the results are determined they do not change anymore. Of course they are not there from the beginning.
My idea here is that the wrapper will send really just the bare minimum to identify the build (I think jenkins url, full name and build number are required at least, optionally duration). We have an explicit start event, that sends additional data and an explicit end event that will send all data that is desired (with the data provider as mentioned in JENKINS-54645).
Data providers could decide whether the data should be included in the start and/or end event. They are configurable (i.e. in the test results include also successful tests).
A special case is the approach with the script. This might be another post processing option. Or we just drop this idea (I've never been a fan of it to be honest, for the wrapper that could be a performance killer).
The notifier will always send all data that was configured.
mwinter69 I'm not sure – I think most of it is static, but some aren't:
I think this would require some refactor to split the actually static data from mutable one