[JIRA] (JENKINS-50507) withMaven must not trigger its own project
Title: Message Title dan tran created an issue Jenkins / JENKINS-50507 withMaven must not trigger its own project Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-04-01 22:19 Environment: linux windows Priority: Critical Reporter: dan tran My pipeline has 2 OS specific stages: Linux and Windows, where the windows stage requires an artifact built by Linux stage via withMaven. This causes withMaven to trigger its very own pipeline Detail discusion at https://groups.google.com/forum/#!topic/jenkinsci-users/h1rY3TLr4rs Add Comment
[JIRA] (JENKINS-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-50507 withMaven must not trigger its own project Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc commented on JENKINS-50507 Re: withMaven must not trigger its own project Is this a regression? Is WithMaven triggering the same branch or a different branch? > My pipeline has 2 OS specific stages: > Linux and Windows, where the windows stage requires an artifact built by Linux stage via withMaven. > This causes withMaven to trigger its very own pipeline I am surprised that calling twice withMaven in the same pipeline could cause this problem. I don't exclude the problem to be elsewhere. See code fragment below and "// Don't trigger myself". https://github.com/jenkinsci/pipeline-maven-plugin/blob/d68ce7bba62f6881ca1ada84ee1cf8d5a851f7a8/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DownstreamPipelineTriggerRunListener.java#L62 ListdownstreamPipelines = GlobalPipelineMavenConfig.getDao().listDownstreamJobs(upstreamPipeline.getFullName(), upstreamBuild.getNumber()); // Don't trigger myself downstreamPipelines.remove(upstreamPipeline.getFullName()); ... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50507) withMaven must not trigger its own project
Title: Message Title dan tran commented on JENKINS-50507 Re: withMaven must not trigger its own project dont know if this is regression, since this is first time i was able to get triggering working Yes, it triggers same branch. did you do the same for upstream? below is the content of our triggering. Not sure if this helps Artifacts generated by this build. Hyperlink added when the artifact has been deployed to a Maven repository. Upstream Builds * exxx » eXXX » exxx » master #135 exxx » eXXX » exxx-ui-ng » master #33 Builds that generate artifacts that are dependencies of this build. This list is filtered by permissions, you must have the ITEM.Read permission on the job to see it. Note that these builds have not necessarily triggered this job: a trigger "Build whenever a SNAPSHOT dependency is built" must be configured on this job. Downstream Jobs * exxx » eXXX » exxx » master exxx » eXXX» exxx » master Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran edited a comment on JENKINS-50507 Re: withMaven must not trigger its own project dont know if this is regression, since this is first time i was able to get triggering working Yes, it triggers same branch. did you do the same for upstream? below is the content of our triggering. Not sure if this helps_Artifacts generated by this build. Hyperlink added when the artifact has been deployed to a Maven repository._Upstream Builds * exxx[ » eXXX » exxx » master #135|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/135/] * [exxx » eXXX » exxx-ui-ng » master #33|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm-ui-ng/job/master/33/]_Builds that generate artifacts that are dependencies of this build._ _This list is filtered by permissions, you must have the ITEM.Read permission on the job to see it._ _Note that these builds have not necessarily triggered this job: a trigger "Build whenever a SNAPSHOT dependency is built" must be configured on this job._Downstream Jobs * [exxx » eXXX » exxx » master|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/] * [exxx » eXXX» exxx » master|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran edited a comment on JENKINS-50507 Re: withMaven must not trigger its own project dont know if this is regression, since this is first time i was able to get triggering working Yes, it triggers same branch. did you do the same for upstream? below is the content of our triggering. Not sure if this helps_Artifacts generated by this build. Hyperlink added when the artifact has been deployed to a Maven repository._Upstream Builds * exxx[ » eXXX » exxx » master #135|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/135/] * [exxx » eXXX » exxx-ui-ng » master #33|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm-ui-ng/job/master/33/]_Builds that generate artifacts that are dependencies of this build._ _This list is filtered by permissions, you must have the ITEM.Read permission on the job to see it._ _Note that these builds have not necessarily triggered this job: a trigger "Build whenever a SNAPSHOT dependency is built" must be configured on this job._Downstream Jobs * [exxx » eXXX » exxx » master|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/] * [exxx » eXXX» exxx » master|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran edited a comment on JENKINS-50507 Re: withMaven must not trigger its own project dont know if this is regression, since this is first time i was able to get triggering working Yes, it triggers same branch. did you do the same for upstream? below is the content of our triggering. Not sure if this helps_Artifacts generated by this build. Hyperlink added when the artifact has been deployed to a Maven repository._Upstream Builds * exxx [ » >> eXXX » >> exxx » >> master #135 |https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/135/] * [ exxx » >> eXXX » >> exxx-ui -ng » >> master # 33|https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm-ui-ng/job/master/33/] 13 _Builds that generate artifacts that are dependencies of this build._ _This list is filtered by permissions, you must have the ITEM.Read permission on the job to see it._ _Note that these builds have not necessarily triggered this job: a trigger "Build whenever a SNAPSHOT dependency is built" must be configured on this job._Downstream Jobs * [ exxx » >> eXXX » >> exxx » >> master |https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/] * [ exxx » >> eXXX » >> exxx » >> master |https://dpadswci.lss.emc.com/job/ecdm/job/ecdm-projects/job/ecdm/job/master/] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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...@googlegrou
[JIRA] (JENKINS-50507) withMaven must not trigger its own project
Title: Message Title dan tran commented on JENKINS-50507 Re: withMaven must not trigger its own project I am still trying to troubleshoot this issue. Is it safe for me to wipe out the H2 database restart Jenkins to see if this helps? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran edited a comment on JENKINS-50507 Re: withMaven must not trigger its own project I am still trying to troubleshoot this issue. Is it safe for me to wipe out the H2 database at /var/jenkins_home/jenkins-jobs/jenkins-jobs, and restart Jenkins to see if this helps? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-50507 withMaven must not trigger its own project Change By: Cyrille Le Clerc Attachment: JENKINS-50507.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc commented on JENKINS-50507 Re: withMaven must not trigger its own project Visualisation glitch reproduced with https://github.com/cyrille-leclerc/JENKINS-50507.git BUT the I don't get the trigger problem. The visualization glitch being that the pipeline JENKINS-50507/master is displayed as an upstream pipeline of JENKINS-50507/master and as a downstream job as well when it should NOT because we don't trigger "myself".> Is it safe for me to wipe out the H2 database at /var/jenkins_home/jenkins-jobs/jenkins-jobs, and restart Jenkins to see if this helps? It is safe but I don't think it will change anything. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran commented on JENKINS-50507 Re: withMaven must not trigger its own project will see the fix for the visualization glitch soon? less things to be confused Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc commented on JENKINS-50507 Re: withMaven must not trigger its own project > will see the fix for the visualisation glitch soon? less things to be confused I hope so, it's not very complex to solve. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50507 Re: withMaven must not trigger its own project Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/be091060674771772d073245f24805a01d52c4c9 Log: JENKINS-50507 If a pipeline consumes the artifacts it produces, then don't display the pipeline in the list of upstream builds or downstream pipelines. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50507 Re: withMaven must not trigger its own project Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/7381b37cec69011574e33db01c17e237884fde7b Log: JENKINS-50507 Fix javadocs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50507 Re: withMaven must not trigger its own project Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/3634b6796e4fe951cb31561180b5386fb867f3e3 Log: Merge pull request #145 from jenkinsci/JENKINS-50507 JENKINS-50507 If a pipeline consumes the artifacts it produces, the… Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/13799d43290f...3634b6796e4f Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc commented on JENKINS-50507 Re: withMaven must not trigger its own project Visualisation glitch is fixed in 3.5.4-beta-1, TODO add URL once published Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-50507 Re: withMaven must not trigger its own project Visualisation glitch is fixed in 3.5.4-beta-1, TODO add URL once published https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.5.4-beta-1/pipeline-maven-3.5.4-beta-1.hpi[~dantran] can you please test?Can you verify if you actually get the job trigger of if it was "just" this visualisation glitch? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title dan tran commented on JENKINS-50507 Re: withMaven must not trigger its own project it works * The Upstreams build content is correct * The downtream job shows it same project one once. Used to be 2. And teh build does not rebuild itself again. Awesome Thanks again Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
