On Thu, Aug 4, 2016 at 12:46 PM Manuel Jesús Recena Soto <rec...@gmail.com> wrote:
> Hello Oliver, > > I like the idea. > > General speaking, ATH and PCT are very important and we should look after > its healthy. > > IMHO, PCT results are a nice place to figure out bad symptoms on some > plugins. > > Can you describe the types of symptoms you envision detecting with PCT? I am interested in running the plugin tests with a different jenkins.version value, after compiling with an unmodified jenkins.version value. That seems like an interesting test alternative that might surface interesting differences in the test harnesses or the core code. I'm not really interested in having some external automation tell me that the current code does not compile with the latest Jenkins core. JENKINS-36646 seems like the same condition I see, failure to compile with the newer Jenkins version because code changes are required before the plugin can depend on the newer version. I update the Jenkins core dependency rarely and with great care. A bug report like JENKINS-36646 is a distraction rather than a help, since I will see the compilation failure as soon as I prepare the change for the plugin to support the new Jenkins core version. For example, the git plugin 3.0.0-beta already has the necessary change to compile with more recent Jenkins core, but the automation probably won't know that it needs to evaluate a beta version on a different branch than master. Mark Waite > Please, find here two issues as result of PCT: JENKINS-36646 > <https://issues.jenkins-ci.org/browse/JENKINS-36646> and JENKINS-36623 > <https://issues.jenkins-ci.org/browse/JENKINS-36623> > > What we maybe need is make more usable and accessible this information. > > Regards, > > > 2016-08-03 15:31 GMT+02:00 Oliver Gondža <ogon...@gmail.com>: > >> Hi, >> >> I created an issue[1] to verify if all recommended plugins has passing >> unittest when run against latest core. I would like to use that as a GA >> criteria for releases, LTS ones at least. >> >> I see people are still updating plugin-compat-tester so I guess it is not >> dead, though I did not manage to find any recent documentation or running >> CI job. Can it be used to implement that? Is somebody working on this? >> >> [1] https://issues.jenkins-ci.org/browse/JENKINS-37145 >> -- >> oliver >> >> -- >> 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 jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/08d33372-c328-71d5-a2c6-870976e3b688%40gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Manuel Recena Soto > * manuelrecena.com [/blog] > * linkedin.com/in/recena > > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CABa-UocUg78nQkNas9iyKK0JLKZvv%3DuT9eDoZLn1f0YYfsTPSA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CABa-UocUg78nQkNas9iyKK0JLKZvv%3DuT9eDoZLn1f0YYfsTPSA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFWnPvcmjCXE3ikhe9cFUSjNbnoLzuBq9AQU49gwB7zYw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
