I've just run into a similar problem and followed the instructions in https://jenkins.io/doc/developer/testing/ which suggest to use the workflow-aggregator dependency. Unfortunately that does not really solve the problem with the latest parent-plugin POM as the maven-enforcer-plugin throws several upper bound dependencies errors.
I think it might make sense to update those instructions or better yet fix the workflow-aggregator dependency as that would make testing the pipeline functionality a lot easier. For now there seems to be a lot of trial/error necessary to get a working combination of plugins to test the pipeline functionality. Thoughts? -- 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/ea7455e5-9c92-4fd6-8e43-68f345e6f965%40googlegroups.com.
