On Mon, Jun 8, 2015 at 5:33 AM, Rösch, Christian <[email protected]> wrote: > The xvnc-plugin creates an post build action (if the option is true) which > kills the xvnc and appends it to the list of post build actions. The action > also removes itself from the list after being executed to avoid persistency > of our pseudo action.
Modifying project configuration from a build, even temporarily, is a bad idea. > Could the problem be solved in a better way? You can use the Xvnc build wrapper (1.22+) from a Workflow and precisely control when the shutdown occurs. Sonar plugin compatibility is probably still missing, but that is another matter. Using a RunListener is also a hack IMO. If a solution is needed for freestyle or Maven projects, it should be to run the tests as a build step; for a publisher to run tests makes little sense. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3A_S1Q-dtamGkAQdVLnu1St1CBLmQdZVPeKC_Ury7Gew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
