Adding a comment to not forget that this thread is not done
On Friday, March 22, 2019 at 10:01:47 AM UTC+1, Aaron Digulla wrote:
>
>
>
> On Thursday, March 21, 2019 at 4:20:54 PM UTC+1, Cyrille Le Clerc wrote:
>>
>>
>> >> Please see new FAQ entry
>>
On Thursday, March 21, 2019 at 4:20:54 PM UTC+1, Cyrille Le Clerc wrote:
>
>
> >> Please see new FAQ entry
> https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowcanItroubleshootproblemsoftriggerofdownstreampipelines
>
> I have improved the FAQ entry based on
>> Please see new FAQ entry
https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowcanItroubleshootproblemsoftriggerofdownstreampipelines
I have improved the FAQ entry based on your feedback, can you please have a
look?
> I had to add a "Pipeline Graph
Hi Cyrille,
I could fix one of my problems in the mean time: To get the downstream
build working, I had to do the following:
In "Manage Jenkins" / "Global Tool Configuration", I had to add a "Pipeline
Graph Publisher" with the dropdown "Add Publisher Options". In there, I
could switch the
Hi Cyrille,
Thanks for the quick answer. My first reply somehow got swallowed.
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
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
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:
-
