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 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/CANfRfr27AogB1URmHPF8sh%2B4ACS4u0qCG9RVOVnTazKg6edimg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
