[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran I have aggregated all the maven artifacts into one single upstream cause to support a relationship on many artifacts. https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53392 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered Can you try with the latest master branch to get https://github.com/jenkinsci/pipeline-maven-plugin/commit/a94794456c1a6bb6342729f41569418e1e4cbf31 You will have a log message "[withMaven] triggerDownstreamPipelines completed in xxx ms" if the duration is greater than 5 seconds or if you enable logs on org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener . Can you please also generate few thread dump during the processing? With jstack or with Jenkins URL /threadDump Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered actually, the upstream log eventually shows the downstream triggers, but it took about 40min :( after the completion. Will do more test to find the pattern Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered the delay is real Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered don't see anything obvious at both build actually, the upstream log eventually shows the downstream triggers , jenkins but it took about 40min :( logs after the completion . will need some time Will do more test to find a consistent the pattern Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered don't see anything obvious at both build log, jenkins logs. will need some time to find a consistent pattern Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered > sorry, the trigger is intermittent. I forced another upstream build and here is the end of upstream log Are there any messages in the logs of the build or in Jenkins logs? I would expect a stacktrace in the logs > I have about 300 Ack, it's way beyond what I anticipated for this feature. I am not aware of technical limitation, the UI is definitively not thought for such number. I'll discuss with colleagues of the multi Cause design. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered sorry, the trigger is intermittent. I forced another upstream build and here is the upload ending end of upstream log [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelinesdont even see Finished: SUCCESS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose? in my case, * upstream - large source tree build on Linux with clean deploy * downstream - pom.xml has a dependency on top level upstream's parent project build on windows. It then dynamically checks out upstream source tree and run maven clean install. This has a large log entry of at upstream log since this downstream builds the same set of dependencies at upstream * downstream -2, same as downstream 1 running on Linux, but only runs a subset of maven modules with integration test enabled via a Maven profile profil both downstream jobs shows lots of upstream trigger entries for many maven gav Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered yes, i see the same screen shot you posted . I have about 300 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered yes, i see the same screen shot you posted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered sorry, the trigger is intermittent. I forced another upstream build and here is the upload ending log [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelinesdont event even see Finished: SUCCESS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered sorry, the trigger is intermittent. I forced another upstream build and here is the upload ending log [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelines dont event see Finished: SUCCESS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered Fixed in 3.5.12-beta-2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc started work on JENKINS-53148 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc updated JENKINS-53148 Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran thanks for the good news. Regarding the rendering problem, can you confirm that your problem is similar to the attached screenshot? How many dependencies do you have listed as cause? 5? 10? 50? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: Cyrille Le Clerc Attachment: pipeline-maven-plugin-1-cause-per-dependency.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose? in my case, * upstream - large source tree build on Linux with clean deploy * downstream - pom.xml has a dependency on top level upstream's parent project build on windows. It then dynamically checkout checks out upstream source tree and run maven clean install to ensure . This has a large log entry of at upstream log since this downstream builds the same set of dependencies at upstream * downstream -2, same as downstream 1 running on Linux, but only runs a subset of maven modules with integration test enabled via a Maven profile both downstream jobs shows lots of upstream trigger entries for many maven gav Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose? in my case, * upstream - large source tree build on Linux with clean deploy * downstream - pom.xml has a dependency on top level upstream's parent project build on windows. It then dynamically checkout upstream source tree and run maven clean install to ensure * downstream -2, same as downstream 1 running on Linux, but only runs a subset of maven modules with integration test enabled via a Maven profile both downstream jobs shows lots of upstream trigger entries for many maven gav Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now show shows entries of the next job jobs , with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of second item, it is just too verbose Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it works, * the upstream log now shows entries of the next jobs, with a long list of maven dependencies * the downstream job shows all entries each has Started by upstream project x # generating Maven artifact com.xCan we reduce the content of the second item, it is just too verbose ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered it works, the upstream log now show entries of the next job, with a long list of maven dependencies Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-53148 Re: downstream job nolonger triggered I [~dantran] can reproduce you please try https://github . I am working on it com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.5.12-beta-2 ?The reasons why downstream pipelines are triggered or are not triggered are clearly explained in the build logs and are visible as build causeshttps://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.5.12-beta-2/pipeline-maven-3.5.12-beta-2.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered I can reproduce. I am working on it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered it works, but this is what i see [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelines [withMaven] Scheduling downstream pipeline folder-x » project-x » repo-1 » master#275 due to dependency on groupId:artifactId:type:3.0.0-1-SNAPSHOT(3.0.0-1-SNAPSHOT) ... [withMaven] Scheduling downstream pipeline folder-x » project-x » repo-2 » master#976 due to dependency on groupId:artifactId:type:3.0.0-1-SNAPSHOT(3.0.0-1-20180902.102143-2087) ... [withMaven] Scheduling downstream pipeline folder-x » project-x » repo-3 » master#1177 due to dependency on groupId:artifactId:type:3.0.0-1-SNAPSHOT(3.0.0-1-20180902.102219-2086) ... Finished: SUCCESS ie, only one maven GAV shows up ending with '...' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-53148
Re: downstream job nolonger triggered
[~dantran] can you please try with the branch https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53380You will have this de-duplication. Message of downstream pipeline scheduling with multiple causes (i.e. dependencies) will look like{noformat}[withMaven] Scheduling downstream pipeline my-downstream-pipeline#62 due to dependency on \ com.example:my-jar:jar:0.7-SNAPSHOT(0.7-20180902.093122-80), \ com.example:my-other-jar:jar:0.7-SNAPSHOT(0.7-20180902.093137-80)...{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran can you please try with the branch https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-53380 You will have this de-duplication. Message of downstream pipeline scheduling with multiple causes (i.e. dependencies) will look like [withMaven] Scheduling downstream pipeline my-downstream-pipeline#62 due to dependency on com.example:my-jar:jar:0.7-SNAPSHOT(0.7-20180902.093122-80), com.example:my-other-jar:jar:0.7-SNAPSHOT(0.7-20180902.093137-80)... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered my upstream job now has this type of log [withMaven] Scheduling downstream pipeline folder-x» project-x» repo-x » master#273 due to dependency on groupId:artifactid:type:version the list matches with upstream's Maven report's downstream job Perhaps you can detect this condition and trigger downstream job once? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered I started another build with the latest source this plugin latest source . So what are you looking for from the log? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered I started another build with the latest source this plugin. So what are you looking for from the log? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-53148 Re: downstream job nolonger triggered [~dantran] can you try to reproduce with the improved message https://github.com/jenkinsci/pipeline-maven-plugin/commit/c65ec72a02a15ab5a1171d435fdb7af887207e18. You just have to build master branch. I suspect that you see multi triggers of some downstream pipelines because these downstream pipelines depend on multiple artifacts generated by your upstream pipeline.I will ASAP improve the trigger of downstream pipelines to replace multi-trigger of downstream pipelines when they depend on multiple dependencies by mono trigger with multi-causes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran can you try to reproduce with the improved message https://github.com/jenkinsci/pipeline-maven-plugin/commit/c65ec72a02a15ab5a1171d435fdb7af887207e18 I suspect that you see multi triggers of some downstream pipelines because these downstream pipelines depend on multiple artifacts generated by your upstream pipeline. I will ASAP improve the trigger of downstream pipelines to replace multi-trigger of downstream pipelines when they depend on multiple dependencies by mono trigger with multi-causes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered it seems to me, the multiple trigger entries coming from all transitive dependencies found at the upstream's Maven report. The first one triggers a first downstream job, and then the rest follow up with another jobSo my private build , with the change at https://issues.jenkins-ci.org/browse/JENKINS-51953, solves my original issue, but introduce a new one a little less severe must fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered it seems to me, the multiple trigger entries coming from all transitive dependencies found at the upstream's Maven report. The first one triggers a first downstream job, and then the rest follow up with another job So my private build solves my original issue, but introduce a new one a little less severe must fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered i locally built latest and deployed to my production. Triggering now works but each downstream job runs twice with the second one repeated in log. and take a long time for triggering log to finishHere is my ending log with sensitive info remove removed [Bitbucket] Notifying commit build result[Bitbucket] Build result notified[withMaven] pipelineGraphPublisher - triggerDownstreamPipelines[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#959... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1161...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-3 » master#261...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960...[withMaven] Scheduling
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered i locally built latest and deployed to my production. Triggering now works but each downstream job runs twice with the second one repeated in log. and take a long time for triggering log to finish Here is my ending log with sensitive info remove [Bitbucket] Notifying commit build result [Bitbucket] Build result notified [withMaven] pipelineGraphPublisher - triggerDownstreamPipelines [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#959... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1161... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-3 » master#261... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-2 » master#1162... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 » master#960... [withMaven] Scheduling downstream folder-x » project-x » repo-1 »
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered very promising, look forward with a test build of this plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered dan tran I am preparing at the moment an improvement of this message: https://issues.jenkins-ci.org/browse/JENKINS-53378 https://github.com/jenkinsci/pipeline-maven-plugin/pull/159 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered no log. I push the second level job and want to to see a bunch of jobs to be triggered at third level jobs. The only message I see: onCompleted() what kind of dependency that would produce "Not triggering [x » y » z » master] because it has dependencies in the downstream project list" ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered I am not able to scale down to reproduce the issue. Ended up to install latest pipeline-maven-plugin and enable org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener to finer at production build to trouble shoot troubleshoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered I am not able to scale down to reproduce the issue. Ended up to install latest pipeline-maven-plugin and enable org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener to finer to trouble shoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered my build consists of 3 layers. * Multiple Maven pipelines in layer 1 trigger layer 2. ( maven clean deploy). This works * Layer 2 is one single Maven pipeline with a fairly large source tree to produce an OVA. It also build builds and maven deploy deploys integration test code, but not running the tests * Layer 3 has a number of small Git repos which clone the large source tree of layer 2 on the fly and build a portion of the tree for integration test purpose ( via maven clean install ). ie we run slow integration test suites in parallel at layer 3 Layer 2 has this message: [withMaven] Not triggering [x » y » z » master] because it has dependencies in the downstream project list My guess here is withMaven thinks layer 3 has dependencies of itself already built at Layer 2I think I will be able to simulate this scenario with smaller pipelines, just need time :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered Thanks Dan, the "finer" log level granularity should display in the log if the algorithm thinks there is an infinite loop. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered my build consists of 3 layers. * Multiple Maven pipelines in layer 1 trigger layer 2. ( maven clean deploy). This works * Layer 2 is one single Maven pipeline with a fairly large source tree to produce an OVA. It also build and maven deploy integration test code, but not running the tests * Layer 3 has a number of small Git repos which clone the large source tree of layer 2 on the fly and build a portion of the tree for integration test purpose ( via maven clean install ). ie we run slow integration test suites in parallel at layer 3My guess here is withMaven thinks layer 3 has dependencies of itself already built at Layer 2I think I will be able to simulate this scenario with smaller pipelines, just need time :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered my build consists of 3 layers. * Multiple Maven pipelines in layer 1 trigger layer 2. ( maven clean deploy) . This works * Layer 2 is one single Maven pipeline with a fairly large source tree to produce an OVA. * Layer 3 has a number of small Git repos which clone the large source tree of layer 2 on the fly and build a portion of the tree for integration test purpose ( via maven clean install ). ie we run slow integration test suites in parallel under at layer 3My guess here is withMaven thinks layer 3 has dependencies of itself already built at Layer 2I think I will be able to simulate this scenario with smaller project pipelines , just need time :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran edited a comment on JENKINS-53148 Re: downstream job nolonger triggered my build consists of 3 layers. * Multiple Maven pipelines in layer 1 trigger layer 2. ( maven clean deploy) * Layer 2 is one single Maven pipeline with a fairly large source tree to produce an OVA. * Layer 3 has a number of small Git repos which clone the large source tree of layer 2 on the fly and build a portion of the tree for integration test purpose ( via maven clean install ). ie we run slow integration test suites in parallel under layer 3My guess here is withMaven thinks layer 3 has dependencies of itself already built at Layer 2I think I will be able to simulate this scenario with smaller project, just need time :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered my build consists of 3 layers. * Multiple Maven pipelines in layer 1 trigger layer 2. ( maven clean deploy) * Layer 2 is one single Maven pipeline with a fairly large source tree to produce an OVA. * Layer 3 has a number of small Git repos which clone the large source tree of layer 2 on the fly and build a portion of the tree for integration test purpose ( via maven clean install ). ie we run slow integration test suites in parallel under layer 3 My guess here is withMaven has dependencies of itself already built at Layer 2 I think I will be able to simulate this scenario with smaller project, just need time Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title Cyrille Le Clerc commented on JENKINS-53148 Re: downstream job nolonger triggered Can you enable more logs on the logger "org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener", it will add more messages in the build logs. Can you please provide more details? Style of your Maven projects Relationship between the pipelines and maven projects messages in the logs (particularly logs of the upstream build that is not triggering the desired downstream pipeline) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran updated an issue Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: dan tran This is regression properly due to JENKINS-51680 where my downstream job depends on a maven module/artifact of the upstream snapshot Revert back 3.5.9 to get auto trigger working again Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran created an issue Jenkins / JENKINS-53148 downstream job nolonger triggered Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-08-20 21:12 Priority: Minor Reporter: dan tran This is regression properly due to JENKINS-51680 where my downstream job depends on a maven module/artifact of the upstream snapshot Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
