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
On Fri, Jul 5, 2019 at 9:20 AM Devin Nusbaum wrote:
> it might be preferable to convert your test case to scripted and depend only
> on workflow-cps, workflow-job, and workflow-basic-steps in test scope
> (perhaps also a few others such workflow-durable-task-step for the `node`
> step).
Thanks Gavin and Devin. Pipeline: Declarative dependency was required.
On Fri, Jul 5, 2019 at 6:50 PM Devin Nusbaum wrote:
> “pipeline” in a Jenkinsfile comes from Pipeline: Declarative Plugin,
> groupId is org.jenkinsci.plugins, artifactId is pipeline-model-definition.
> That has a lot of
“pipeline” in a Jenkinsfile comes from Pipeline: Declarative Plugin, groupId is
org.jenkinsci.plugins, artifactId is pipeline-model-definition. That has a lot
of dependencies, so depending on your use case, it might be preferable to
convert your test case to scripted and depend only on
You need to depend (I recommend scope of test) on the pipeline plugin that
implements that feature. I think it would be the following but I can't
remember
org.jenkins-ci.plugins.workflow
workflow-step-api
2.19
test
(Or maybe definition-
Hi all,
I am working Branch Source part of GitLab Plugin. There are a different
bugs that needs attention but for now, the basic branch indexing and branch
building for Multibranch Pipeline Jobs works just fine.
I want to test the pipeline jobs with `mvn hpi:run`. But when a branch is
getting
