Yes, we could use PCT for Jenkins Configuration-as-Code tests. But, if we want to run JCasC integration tests as a part of the core pipeline, we would need to integrate PCT directly into Jenkins Core pipeline. I had a pull request for that ( https://github.com/jenkinsci/jenkins/pull/3438), but it was stalled. Maybe we could revisit it.
BR, Oleg On Tuesday, June 4, 2019 at 11:24:53 PM UTC+2, Jon Brohauge wrote: > > If it makes sense to use the plugin-compat-test, we should go with this. I > wasn't aware of its existence. > > On Tue, 4 Jun 2019, 22.18 Slide, <slid...@gmail.com <javascript:>> wrote: > >> I agree with Jesse. The suite as is is so large already. The >> plugin-compat-test was made for purposes similar to this I believe, so why >> not use the tools that are available? >> >> On Tue, Jun 4, 2019 at 11:29 AM Jesse Glick <jgl...@cloudbees.com >> <javascript:>> wrote: >> >>> On Tue, Jun 4, 2019 at 1:23 PM Joseph P <jose...@gmail.com <javascript:>> >>> wrote: >>> > we would avoid regressions that are related to configuration-as-code >>> >>> I think that should be handled differently, for example by something >>> like JENKINS-45047, or `plugin-compat-tester`, or >>> `buildPlugin.recommendedConfigurations()`, or Dependabot. There are >>> plenty of critical plugins which are prone to breaking due to changes >>> in core, and we cannot possibly stuff the core test suite full of all >>> of them. (In fact I would prefer to be _removing_ some plugins from >>> the `test` POM.) Instead, plugins define tests and a `jenkins.version` >>> known to pass them, and we use various tooling to ensure that these >>> tests are also run against newer dependency versions so that >>> regressions are caught in a timely manner. >>> >>> -- >>> 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 jenkin...@googlegroups.com <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0ALHHvTcOeRRrmLV10B%3DaeODTGWsOcQ2yCWu4BKoT5dw%40mail.gmail.com >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> Website: http://earl-of-code.com >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/cgbYEB3c_Vc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> jenkin...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVduMQyrmKzkjyktOCHw8EhbzzOhMO6tAotZVSvO5cp8dw%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVduMQyrmKzkjyktOCHw8EhbzzOhMO6tAotZVSvO5cp8dw%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/e4667cde-7719-47a2-9c66-4daf12c98eda%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
