Hi Aaron,
- Why do I sometimes get duplicate artifacts? They are not duplicated on
> disk. In the console log, I just see a single invocation of
> artifactsPublisher but sometimes, it reports the same artifact several
> times.
Can you share the Jenkinsfile and the logs of your build? Usually artifact
are displayed several time because "mvn package" or more than "package"
("install" or "deploy") is called several times in the build (e.g.
invoking "mvn test" then "mvn deploy")
> - Why isn't C listed as "Downstream Job" of B?
Can you please share screenshots of the "/maven" tab of both job "B" and
"C"?
By default, downstream pipeline triggers only work when a pipeline
is"success" or "unstable" and when the "mvn" goal is "deploy". This means
that by default, "mvn package" or "mvn install" would not trigger a
downstram pipeline.
> - How can I collect more information to debug this?
Please see new FAQ entry
https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowcanItroubleshootproblemsoftriggerofdownstreampipelines
On Monday, March 18, 2019 at 3:15:26 PM UTC, Aaron Digulla wrote:
>
> I have three projects in my example, A, B and C.
>
> A is built on another Jenkins PROD. It's deployed to Nexus.
>
> B depends on A. It's built on Jenkins TEST.
>
> C depends on B. It's also built on Jenkins TEST.
>
> All three projects have a SNAPSHOT version.
>
> The web page .../job/*/maven of B shows me:
>
> - All artifacts of B twice (*.jar, *.jar, *-sources.jar, *-sources.jar,
> *-test-sources.jar, *-test-sources.jar, *.pom, *.pom, *-tests.jar,
> *-tests.jar)
> - No "Upstream Builds"
> - No "Downstream Jobs"
> - A is listed as dependency
>
> I'd expect each artifact of B once and C as downstream job. Not sure about
> dependencies but seeing A here would be nice even though it's built on
> another Jenkins.
>
> The web page .../job/*/maven of C shows me:
>
> - Just some duplicate artifacts. This is a multi-module build. I'm seeing
> the root POM twice, everything else just once.
> - No "Upstream Builds"
> - No "Downstream Jobs"
> - A and B are listed as dependencies.
>
> As far as I can tell, the two jobs use the same Jenkins Pipeline. They are
> both of type "Multibranch Pipeline".
>
> B gets deployed to Nexus when I build the "master" and release branches
> but not for feature branches. C only gets deployed to Nexus when it's a
> release branch.
>
> I'm admin on Jenkins TEST, so I'm pretty sure it's not a ITEM.Read
> permission issue.
>
> There is no config option "Build whenever a SNAPSHOT dependency is built"
> for the jobs B or C. I can see the option when I click "View Configuration"
> in .../job/*/master/configure
>
> Questions:
>
> - Why do I sometimes get duplicate artifacts? They are not duplicated on
> disk. In the console log, I just see a single invocation of
> artifactsPublisher but sometimes, it reports the same artifact several
> times.
> - Why isn't C listed as "Downstream Job" of B?
> - How can I collect more information to debug this?
>
> Regards,
>
> --
> Aaron Digulla
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/b83b080e-eac7-417b-acdc-74319c4aa9a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
