Hi Jesse, Yes, essentialsTest() didn't get as much progress as I would have expected. Not my decision, the story has been handed over to other contributors. But there is a number of stories related to it, e.g. are pending patches for essentialsTest():
- Core: https://github.com/jenkinsci/jenkins/pull/3438 - It adds PCT, feel free to throw in your use-cases - Remoting: https://github.com/jenkinsci/remoting/pull/265 - It was merged and then reverted by Jeff Thompson, but I plan to get it over the fence at some point with Raul - Stapler: https://github.com/stapler/stapler/pull/138 These stories will be completed by somebody at some point (sorry for being sooo specific), and that's why I would rather prefer to have JEP-309 finalized instead of staying in flux. essentialTest() will also eventually use BOM as consumer in order to automatically determine defaults for PCT and ATH. So far it just produces BOM and publishes it as an artifact. Hopefully it answers the question, Oleg On Mon, Aug 6, 2018 at 6:10 PM, Jesse Glick <[email protected]> wrote: > On Mon, Aug 6, 2018 at 11:25 AM Oleg Nenashev <[email protected]> > wrote: > > We define cross-dependencies between CWP formats and Jenkins > Infrastructure (essentialsTest() on ci.jenkins.io) > > Yes, this is a cross-dependency, since the `pipeline-library` method > calls do not seem to specify a version of CWP. > > Where is this method being used BTW? > > https://github.com/search?ref=simplesearch&type=Code&q=user% > 3Ajenkinsci+essentialstest > > does not turn up any hits. I searched for > > https://github.com/search?q=user%3Ajenkinsci+user% > 3Ajenkins-infra+filename%3Aessentials.yml+filename% > 3Aessentials.yaml&type=Code > > (note the extension mismatch!) and saw that only Jenkins core and the > Git plugin were currently using this. Neither `Jenkinsfile` calls the > library function; they seem to use `runATH` and `runPCT` directly. > Jenkins core runs only ATH, no PCT (even though it would be very > useful to check compatibility against some plugins like `workflow-job` > which could easily be broken by subtle core changes). The Git plugin > runs some ATH tests and also claims to run PCT but only on itself, > which seems to make no sense (it should be running tests of _other_ > plugins which would likely be broken by mistakes in `git-plugin`). Or > rather it _would_ be running ATH & PCT—currently this is all disabled. > > So not a very large sample size here. Are there some plans to clean > this up and get `essentialsTest` widely used? > > -- > 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/pR2ZQMj95Zc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/CANfRfr27AogB1URmHPF8sh%2B4ACS4u0qCG9RVOVnTazKg6edimg% > 40mail.gmail.com. > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBCP7Uma9zOwFePVCefKam_0-Lz04%3D_c3rpn9SWc7oAcA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
