[JIRA] (JENKINS-55616) hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
Title: Message Title
Elie Kassis edited a comment on JENKINS-55616
Re: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
[~abayer], we are facing an issue after upgrading jenkins and several plugins.All executePostBuild are failing with below error. +Potential guilty plugin+ pipeline-model-definition -> Guilty issue: JENKINS-56402*Pipeline: Model API* ==> current version 1.3.8 ==> old version 1.3.4.1 Can you please assist ? {code:java}hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() is applicable for argument types: (org.jenkinsci.plugins.pipeline.modeldefinition.model.Root) values: [org.jenkinsci.plugins.pipeline.modeldefinition.model.Root(org.jenkinsci.plugins.pipeline.modeldefinition.model.Agent(org.jenkinsci.plugins.workflow.cps.CpsClosure2@4e4c0304), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stages([org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Prepare Debug Job, null, null, null, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@193f4d75), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Push Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@889e600, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@142cbef4), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Retry Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@1fbed651, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@15f20b8e), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Profile, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@8b9d24e, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@6689d642), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Parsing, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@40674bbf, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@11bed30b), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Archiving, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@57800d78, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@5ca25f43), null, [], null, false, null, null)]), org.jenkinsci.plugins.pipeline.modeldefinition.model.MappedClosure([failure:org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@577ff6e2),
[JIRA] (JENKINS-55616) hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
Title: Message Title Elie Kassis commented on JENKINS-55616 Re: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage() we are facing an issue after upgrading jenkins and several plugins. All executePostBuild are failing with below error. Can you please assist ? hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() is applicable for argument types: (org.jenkinsci.plugins.pipeline.modeldefinition.model.Root) values: [org.jenkinsci.plugins.pipeline.modeldefinition.model.Root(org.jenkinsci.plugins.pipeline.modeldefinition.model.Agent(org.jenkinsci.plugins.workflow.cps.CpsClosure2@4e4c0304), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stages([org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Prepare Debug Job, null, null, null, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@193f4d75), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Push Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@889e600, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@142cbef4), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Retry Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@1fbed651, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@15f20b8e), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Profile, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@8b9d24e, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@6689d642), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Parsing, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@40674bbf, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@11bed30b), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Archiving, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@57800d78, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@5ca25f43), null, [], null, false, null, null)]), org.jenkinsci.plugins.pipeline.modeldefinition.model.MappedClosure([failure:org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@577ff6e2),
[JIRA] (JENKINS-55616) hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-55616 hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage() Change By: Elie Kassis Priority: Minor Blocker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196787.1547637213000.23190.1559890920471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing Olivier Lamy can you please tell us if this issue will be handled? since it is needed urgently to be able to monitor jobs during processing phase. 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-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53735 Parallel sequential stages not showing Triggered Builds while Processing Change By: Elie Kassis Priority: Critical Blocker 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis commented on JENKINS-53900 Re: Stage graph in Blue Ocean not showing all stages for large workflows thank you Josh McDonald! Can you please help me with JENKINS-53735 since noone is replying ? 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-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing Olivier Lamy Can you please just tell us when is it expected to tackle this issue ? 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-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing hi Olivier Lamy, are you planning to fix this issue? 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis commented on JENKINS-53900 Re: Stage graph in Blue Ocean not showing all stages for large workflows Josh McDonald the pipeline is already attached, please use 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis edited a comment on JENKINS-53900
Re: Stage graph in Blue Ocean not showing all stages for large workflows
[~sophistifunk], you can check the attached pipeline code on which we are facing the issue.Noting that in the example you provided there the no sequential stages inside the parallel nodes.*{color:#0747a6}In addition your code that launch parallel stages is totally different then the one we are using . Can you please tell us how using your way to have sequential stages inside parallel nodes?{color}*
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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis commented on JENKINS-53900 Re: Stage graph in Blue Ocean not showing all stages for large workflows Josh McDonald, you can check the attached pipeline code on which we are facing the issue. Noting that in the example you provided there the no sequential stages inside the parallel one. 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53900 Stage graph in Blue Ocean not showing all stages for large workflows Change By: Elie Kassis Attachment: pipeline_example.groovy 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53900
Stage graph in Blue Ocean not showing all stages for large workflows
Change By:
Elie Kassis
Stage graph in Blue Ocean not showing all stages for large workflows. As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. you can find the code as per the attached. !image-2018-10-04-13-00-11-064.png|width=581,height=138! {code:java}pipeline { agent any stages { stage('Prepare Workflow') { steps {script { //get Reference println("Getting References")} } } stage('Generate Debug Job') { steps {script { println("Generate Debug Job")} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel {stage('TE1') { stages { stage('PUSH TE1') { steps {script { println("PUSH TE1")} } } stage('Archive Logs') { steps {script { println("Archive TE1 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE1 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE1 vs REF")} } } }}stage('TE2') { stages { stage('PUSH TE2') { steps {script { println("PUSH TE2")} } } stage('Archive Logs') { steps {script { println("Archive TE2 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE2 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE2 vs REF")} } } }}stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { steps {script { println("PUSH HEAD DEBUG")} } } stage('DEPLOY CLIENT HEAD') { steps {script { println("Deploying Client HEAD")} } } }}stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { steps {script { println("PUSH REF DEBUG")} } } stage('DEPLOY CLIENT REF') { steps {script { println("Deploying Client REF")} } } }} } } stage('CrossChecking') { steps {script { println("CrossChecking")} } } stage('SetReferences') { steps {script { println("Set References")} } } stage('Head vs Head-1') { steps {script { println("Head vs Head-1")} } } stage('Send MAIL and Insert JIRA') { parallel {stage('Sending Mail') { stages { stage('Send MAIL') { steps {script { println("Sending Mail")} } } }}stage('Inserting Jira') { stages { stage('Insert JIRA') { steps {script { println
[JIRA] (JENKINS-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53900
Stage graph in Blue Ocean not showing all stages for large workflows
Change By:
Elie Kassis
Stage graph in Blue Ocean not showing all stages for large workflows. As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. !image-2018-10-04-13-00-11-064.png|width=581,height=138! {code:java}pipeline { agent any stages { stage('Prepare Workflow') { steps {script { //get Reference println("Getting References")} } } stage('Generate Debug Job') { steps {script { println("Generate Debug Job")} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel { stage('TE1') { stages { stage('PUSH TE1') { steps {script { println("PUSH TE1")} } } stage('Archive Logs') { steps {script { println("Archive TE1 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE1 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE1 vs REF")} } } }}stage('TE2') { stages { stage('PUSH TE2') { steps {script { println("PUSH TE2")} } } stage('Archive Logs') { steps {script { println("Archive TE2 Logs")} } } stage('Insert Metrics') { steps {script { println("Insert TE2 Metrics in DB")} } } stage('Compare Metrics') { steps {script { println("Compare Metrics TE2 vs REF")} } } }}stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { steps {script { println("PUSH HEAD DEBUG")} } } stage('DEPLOY CLIENT HEAD') { steps {script { println("Deploying Client HEAD")} } } }}stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { steps {script { println("PUSH REF DEBUG")} } } stage('DEPLOY CLIENT REF') { steps {script { println("Deploying Client REF")} } } }} } } stage('CrossChecking') { steps {script { println("CrossChecking")} } } stage('SetReferences') { steps {script { println("Set References")} } } stage('Head vs Head-1') { steps {script { println("Head vs Head-1")} } } stage('Send MAIL and Insert JIRA') { parallel {stage('Sending Mail') { stages { stage('Send MAIL') { steps {script { println("Sending Mail")} } } }}stage('Inserting Jira') { stages { stage('Insert JIRA') { steps {script { println "Inserting
[JIRA] (JENKINS-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53900
Stage graph in Blue Ocean not showing all stages for large workflows
Change By:
Elie Kassis
Stage graph in Blue Ocean not showing all stages for large workflows. As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. !image-2018-10-04-13-00-11-064.png|width=581,height=138! {code:java}pipeline { options { timeout(time: 4, unit: 'HOURS') ansiColor('xterm') } // agent any agent { node { label 'pacpte_dell1114srv' } } stages { stage('Prepare Workflow') { steps {script { timestamps { //get Reference println("Getting References") }} } } stage('Generate Debug Job') { steps {script { timestamps { println("Generate Debug Job") }} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel { stage('TE1') { stages { stage('PUSH TE1') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE1") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE1 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE1 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE1 vs REF") }} } } } } stage('TE2') { stages { stage('PUSH TE2') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE2") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE2 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE2 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE2 vs REF") }} } } } } stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps { println("PUSH HEAD DEBUG") }} } } stage('DEPLOY CLIENT HEAD') { steps {script { timestamps { println("Deploying Client HEAD") }} } } } } stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') }
[JIRA] (JENKINS-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53900
Stage graph in Blue Ocean not showing all stages for large workflows
Change By:
Elie Kassis
Stage graph in Blue Ocean not showing all stages for large workflows.As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. !image-2018-10-04-13-00-11-064.png|width=581,height=138! {code:java}pipeline { options { timeout(time: 4, unit: 'HOURS') ansiColor('xterm') } //agent any agent { node { label 'pacpte_dell1114srv' } } stages { stage('Prepare Workflow') { steps {script { timestamps { //get Reference println("Getting References") }} } } stage('Generate Debug Job') { steps {script { timestamps { println("Generate Debug Job") }} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel {stage('TE1') { stages { stage('PUSH TE1') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE1") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE1 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE1 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE1 vs REF") }} } } }}stage('TE2') { stages { stage('PUSH TE2') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE2") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE2 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE2 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE2 vs REF") }} } } }}stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps { println("PUSH HEAD DEBUG") }} } } stage('DEPLOY CLIENT HEAD') { steps {script { timestamps { println("Deploying Client HEAD") }} } } }}stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps { println("PUSH REF
[JIRA] (JENKINS-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis commented on JENKINS-53900 Re: Stage graph in Blue Ocean not showing all stages for large workflows Vivek Pandey I added the pipeline code in the description. 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-53803) Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53803
Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE
Change By:
Elie Kassis
After upgrading to the last blueocean plugin (1.8.3), the Parallel sequential stages are showing wrong status when one of the stages is UNSTABLE. As shown in the attached picture, the DONE stages are colored in +*Grey*+. {code:java}pipeline { options { timeout(time: 4, unit: 'HOURS') ansiColor('xterm') } //agent any agent { node { label 'pacpte_dell1114srv' } } stages { stage('Prepare Workflow') { steps {script { timestamps { //get Reference println("Getting References") }} } } stage('Generate Debug Job') { steps {script { timestamps { println("Generate Debug Job") }} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel {stage('TE1') { stages { stage('PUSH TE1') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE1") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE1 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE1 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE1 vs REF") }} } } }}stage('TE2') { stages { stage('PUSH TE2') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE2") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE2 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE2 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE2 vs REF") }} } } }}stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps { println("PUSH HEAD DEBUG") }} } } stage('DEPLOY CLIENT HEAD') { steps {script { timestamps { println("Deploying Client HEAD") }} } } }}stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps {
[JIRA] (JENKINS-53803) Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE
Title: Message Title
Elie Kassis updated an issue
Jenkins / JENKINS-53803
Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE
Change By:
Elie Kassis
After upgrading to the last blueocean plugin (1.8.3), the Parallel sequential stages are showing wrong status when one of the stages is UNSTABLE. As shown in the attached picture, the DONE stages are colored in +*Grey*+. {code:java}pipeline { options { timeout(time: 4, unit: 'HOURS') ansiColor('xterm') } //agent any agent { node { label 'pacpte_dell1114srv' } } stages { stage('Prepare Workflow') { steps {script { timestamps { //get Reference println("Getting References") }} } } stage('Generate Debug Job') { steps {script { timestamps { println("Generate Debug Job") }} } } stage('Pushing 2 Tests and 2 Debug jobs') { //failFast true parallel {stage('TE1') { stages { stage('PUSH TE1') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE1") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE1 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE1 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE1 vs REF") }} } } }}stage('TE2') { stages { stage('PUSH TE2') { options {retry(2)timeout(time: 3, unit: 'HOURS') } steps {script { timestamps { println("PUSH TE2") }} } } stage('Archive Logs') { steps {script { timestamps { println("Archive TE2 Logs") }} } } stage('Insert Metrics') { steps {script { timestamps { println("Insert TE2 Metrics in DB") }} } } stage('Compare Metrics') { steps {script { timestamps { println("Compare Metrics TE2 vs REF") }} } } }}stage('HEAD DEBUG') { stages { stage('PUSH HEAD DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps { println("PUSH HEAD DEBUG") }} } } stage('DEPLOY CLIENT HEAD') { steps {script { timestamps { println("Deploying Client HEAD") }} } } }}stage('REF DEBUG') { stages { stage('PUSH REF DEBUG') { options {retry(2)timeout(time: 2, unit: 'HOURS') } steps {script { timestamps {
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53735 Parallel sequential stages not showing Triggered Builds while Processing Change By: Elie Kassis Priority: Major Critical 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Elie Kassis created an issue Jenkins / JENKINS-53900 Stage graph in Blue Ocean not showing all stages for large workflows Issue Type: Bug Assignee: Unassigned Attachments: image-2018-10-04-13-00-11-064.png Components: blueocean-plugin Created: 2018-10-04 10:02 Environment: Jenkins: 2.138.1 Blue Ocean: 1.8.3 OS: RHEL7.2 Browser: Google Chrome Labels: blueocean Priority: Critical Reporter: Elie Kassis Stage graph in Blue Ocean not showing all stages for large workflows. As shown in below pipeline the last 2 parallel stages are missing in Blue Ocean noting that they were executed. Add
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Elie Kassis commented on JENKINS-53735 Re: Parallel sequential stages not showing Triggered Builds while Processing Olivier Lamy when do you expect to have a fix for this bug ? 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-53803) Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE
Title: Message Title Elie Kassis assigned an issue to Elie Kassis Jenkins / JENKINS-53803 Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE Change By: Elie Kassis Assignee: Elie Kassis 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-53803) Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE
Title: Message Title Elie Kassis assigned an issue to Unassigned Jenkins / JENKINS-53803 Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE Change By: Elie Kassis Assignee: Elie Kassis 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-53803) Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE
Title: Message Title Elie Kassis created an issue Jenkins / JENKINS-53803 Parallel sequential stages in Blue Ocean showing wrong status when one of the stages is UNSTABLE Issue Type: Bug Assignee: Unassigned Attachments: image-2018-09-27-00-15-19-453.png Components: blueocean-plugin Created: 2018-09-26 21:17 Environment: Jenkins: 2.138.1 Blue Ocean: 1.8.3 OS: RHEL7.2 Browser: Google Chrome Labels: blueocean Priority: Major Reporter: Elie Kassis After upgrading to the last blueocean plugin (1.8.3), the Parallel sequential stages are showing wrong status when one of the stages is UNSTABLE. As shown in the attached picture, the DONE stages are colored in Grey.
[JIRA] (JENKINS-53129) Parallel sequential stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status Sorry Olivier Lamy, a new Jira issue opened: JENKINS-53735 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-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title
Elie Kassis created an issue
Jenkins / JENKINS-53735
Parallel sequential stages not showing Triggered Builds while Processing
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2018-09-24-08-16-11-202.png
Components:
blueocean-plugin
Created:
2018-09-24 05:18
Environment:
Jenkins: 2.138.1 Blue Ocean: 1.8.3 OS: RHEL7.2 Browser: Google Chrome
Labels:
blueocean
Priority:
Major
Reporter:
Elie Kassis
The Triggered Builds Section in Blue Ocean, is not appearing when having processing parallel sequential stages. The Triggered Build section is only appearing when the stage is done or for normal sequential stages. You can find below a sample of the code pushing jobs.
stage('Pushing 2 Tests and 2 Debug jobs') {
//failFast true
when {
_expression_ {
Push2TEs == 'true'
}
}
parallel { stage('TE1') {
stages {
stage('PUSH TE1') {
options {
retry(2)
timeout(time: 3, unit: 'HOURS')
}
steps {
script {
timestamps {
println("${STAGE_BEGIN} PUSH TE1")
def TE1build = build job: "TESTING/${TEST_LABEL1}/PAC_PTE/0010.TESTING-Headline",
[JIRA] (JENKINS-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds Olivier Lamy, a new bug detected, when the first stage in a sequential parallel pipeline is done, the Processing stages got wrong status and show only 1 stage processing even thought there are 4 stages processing. 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-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds Change By: Elie Kassis Attachment: image-2018-09-23-20-42-44-112.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-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds Olivier Lamy, you can find below for sequential Processing stages, Blue Ocean is showing the Triggered Builds section. 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-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds Change By: Elie Kassis Attachment: image-2018-09-23-19-13-12-757.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-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
I trigger jobs from inside the stage as shown below code sample.Noting that the {color:#de350b}*Triggered Builds*{color} section was working properly previously before you started allowing in Blue Ocean to display sequential stages inside a parallel one. +It is very important and crucial to see the Triggered Builds within a stage while PROCESSING and not just when the stage is DONE.+ {code:java}stage('Pushing 2 Tests and 2 Debug jobs') {//failFast truewhen { _expression_ { Push2TEs == 'true' }}parallel { stage('TE1') { stages { stage('PUSH TE1') {options { retry(2) timeout(time: 3, unit: 'HOURS')}steps { script { timestamps { println("${STAGE_BEGIN} PUSH TE1") def TE1build = build job: "TESTING/${TEST_LABEL1}/PAC_PTE/0010.TESTING-Headline",parameters: [ [$class: 'StringParameterValue', name: 'MX_VERSION', value: MX_VERSION], [$class: 'StringParameterValue', name: 'MX_CHANGELIST', value: MX_CHANGELIST], [$class: 'BooleanParameterValue', name: 'Execute_benchmark', value: true], [$class: 'BooleanParameterValue', name: 'Generate_traceability_reports', value: true], [$class: 'StringParameterValue', name: 'SETUPS', value: 'Custom'], [$class: 'StringParameterValue', name: 'Custom_Script_Before', value: '/nfs_qa_pac/pac-pte/jenkins/getEnvProperties.sh'], [$class: 'StringParameterValue', name: 'Custom_Script_After', value: '/nfs_qa_pac/pac-pte/jenkins/restoreEnv.sh']],propagate: false LogJobStatus("${TEST_LABEL1}", TE1build.result) currentBuild.result = TE1build.result } }} } stage('Archive Logs') {steps { script { timestamps { println("${STAGE_BEGIN} Archive ${TEST_LABEL1} Logs") //sleep time: 1, unit: 'MINUTES' def archiveLogsTE1 = build job: 'Archiving',parameters: [ [$class: 'StringParameterValue', name: 'BENCH_MARK_NAME', value: TE1_BENCH_MARK_NAME], [$class: 'StringParameterValue', name: 'VERSION', value: MX_VERSION], [$class: 'StringParameterValue', name: 'CHANGELIST', value: MX_CHANGELIST], [$class: 'StringParameterValue', name: 'APP_DIR', value: TE1_APP_DIR], [$class: 'StringParameterValue', name: 'RESULTS_DIR', value: TE1_LOG_DIR], [$class: 'StringParameterValue', name: 'KPI_DIR', value: TE1_WORKSPACE], [$class: 'StringParameterValue', name: 'TPK', value: TPK], [$class: 'StringParameterValue', name: 'JOB_ID', value: JOB_ID], [$class: 'StringParameterValue', name: 'TEST_ID', value: TEST_LABEL1], [$class: 'StringParameterValue', name: 'NODE', value: TE1_NODE]],propagate: false currentBuild.result = archiveLogsTE1.result LogJobStatus("Archive ${TEST_LABEL1} Logs", archiveLogsTE1.result) println("${STAGE_END} Archive ${TEST_LABEL1} Logs") } }} } } } stage('TE2') { stages { stage('PUSH TE2') {options { retry(2) timeout(time: 3, unit: 'HOURS')}steps { script { timestamps { println("${STAGE_BEGIN} PUSH TE2") def TE2build = build job: "TESTING/${TEST_LABEL2}/PAC_PTE/0010.TESTING-Headline",parameters: [
[JIRA] (JENKINS-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title
Elie Kassis commented on JENKINS-53129
Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
I trigger jobs from inside the stage as shown below code sample. Noting that the Triggered Builds section was working properly previously before you started allowing in Blue Ocean to display sequential stages inside a parallel one.
stage('Pushing 2 Tests and 2 Debug jobs') {
//failFast true
when {
_expression_ {
Push2TEs == 'true'
}
}
parallel { stage('TE1') {
stages {
stage('PUSH TE1') {
options {
retry(2)
timeout(time: 3, unit: 'HOURS')
}
steps {
script {
timestamps {
println("${STAGE_BEGIN} PUSH TE1")
def TE1build = build job: "TESTING/${TEST_LABEL1}/PAC_PTE/0010.TESTING-Headline",
parameters: [
[$class: 'StringParameterValue', name: 'MX_VERSION', value: MX_VERSION],
[$class: 'StringParameterValue', name: 'MX_CHANGELIST', value: MX_CHANGELIST],
[$class: 'BooleanParameterValue', name: 'Execute_benchmark', value: true],
[$class: 'BooleanParameterValue', name: 'Generate_traceability_reports', value: true],
[$class: 'StringParameterValue', name: 'SETUPS', value: 'Custom'],
[$class: 'StringParameterValue', name: 'Custom_Script_Before', value: '/nfs_qa_pac/pac-pte/jenkins/getEnvProperties.sh'],
[$class: 'StringParameterValue', name: 'Custom_Script_After', value: '/nfs_qa_pac/pac-pte/jenkins/restoreEnv.sh']
],
propagate: false
LogJobStatus("${TEST_LABEL1}", TE1build.result)
currentBuild.result = TE1build.result
}
}
}
}
stage('Archive Logs') {
steps {
script {
timestamps {
println("${STAGE_BEGIN} Archive ${TEST_LABEL1} Logs")
//sleep time: 1, unit: 'MINUTES'
def archiveLogsTE1 = build job: 'Archiving',
parameters: [
[$class: 'StringParameterValue', name: 'BENCH_MARK_NAME', value: TE1_BENCH_MARK_NAME],
[$class: 'StringParameterValue', name: 'VERSION', value: MX_VERSION],
[$class: 'StringParameterValue', name: 'CHANGELIST', value: MX_CHANGELIST],
[$class: 'StringParameterValue', name: 'APP_DIR', value: TE1_APP_DIR],
[$class: 'StringParameterValue', name: 'RESULTS_DIR', value: TE1_LOG_DIR],
[$class: 'StringParameterValue', name: 'KPI_DIR', value: TE1_WORKSPACE],
[$class: 'StringParameterValue', name: 'TPK', value: TPK],
[$class: 'StringParameterValue', name: 'JOB_ID', value: JOB_ID],
[$class: 'StringParameterValue', name: 'TEST_ID', value: TEST_LABEL1],
[$class: 'StringParameterValue', name: 'NODE', value: TE1_NODE]
],
propagate: false
currentBuild.result = archiveLogsTE1.result
LogJobStatus("Archive ${TEST_LABEL1} Logs", archiveLogsTE1.result) println("${STAGE_END} Archive ${TEST_LABEL1} Logs")
}
}
}
}
}
} stage('TE2') {
stages {
stage('PUSH TE2') {
options {
retry(2)
timeout(time: 3, unit: 'HOURS')
}
steps {
script {
timestamps {
println("${STAGE_BEGIN} PUSH TE2")
def TE2build = build
[JIRA] (JENKINS-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds Change By: Elie Kassis Summary: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis updated JENKINS-53129 Jenkins / JENKINS-53129 Parallel stages in Blue Ocean showing wrong status Change By: Elie Kassis Status: Fixed but Unreleased Reopened 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3)(Jenkins 2.138.1), but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage. The Triggered Build section is only appearing when the stage is done.In addition when having several parallel stages processing at the same time, only 1 of the stages is having the blue circle with the blue dot blinking inside.Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3)(Jenkins 2.138.1), but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage. The Triggered Build section is only appearing when the stage is done.In addition when having several parallel stages processing at the same time, only 1 of the stages is having the blue circle with the blue dot blinking inside. Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3) (Jenkins 2.138.1) , but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage.Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3) , but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage.Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Olivier Lamy the status issue was resolved with your last fix, but the Triggered Builds Section is not appearing when having processing stage. Can you please check? 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel stages in Blue Ocean showing wrong status Change By: Elie Kassis Attachment: image-2018-09-22-13-17-53-432.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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Thank you Olivier Lamy. When it is expected to have the plugin patch ready in Jenkins ? 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis edited a comment on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status [~olamy] yes related to JENKINS-53311 but with additional problem in my Jira related to "Triggered Builds" Field.In addition my Jira issue was reported before JENKINS-53311 and contains more examples 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Olivier Lamy yes related to JENKINS-53311 but with additional problem in my Jira related to "Triggered Builds" Field. In addition my Jira issue was reported before JENKINS-53311 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Nicolae Pascu Vivek Pandey is there any estimation when this issue will be fixed? 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Vivek Pandey, another case where 2 parallel stages are processing but shown in Blue Ocean in Grey (Pending). 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel stages in Blue Ocean showing wrong status Change By: Elie Kassis Attachment: image-2018-08-23-01-15-45-479.png 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Vivek Pandey, Nicolae Pascu, please let me know if you need more details. 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Vivek Pandey, in addition currently the Processing stages are not visible on Blue Ocean. They only appear once they are done. 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel stages in Blue Ocean showing wrong status Change By: Elie Kassis Attachment: image-2018-08-22-16-11-36-340.png 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel stages in Blue Ocean showing wrong status Change By: Elie Kassis Summary: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean ) showing wrong status 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
[~vivek] As seen in my previous comment, when clicking on the upper stage it is giving me the details of the Parent stage ( * {color:#de350b}_Pushing 2 Tests | / TE1_{color} * ) instead of the child (*_PUSH TE1_*) and when selecting the bottom stage it is giving me the details of the right stage ({color:#00875a}*_PUSH TE2_*{color}) but with {color:#de350b} +*wrong status*+ {color} .
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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
[~vivek] As seen in my previous comment, the issue is that in Blue Ocean, when clicking on the upper stage it is giving me the details of the Parent stage ({color:#de350b}_Pushing 2 Tests_ Tests | TE1_ {color}) instead of the child (*_PUSH TE1_*) and when selecting the bottom stage it is giving me the details of the right stage ({color:#00875a}*_PUSH TE2_*{color}) but with +*wrong status*+.
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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis edited a comment on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry [~vivek], but this is not the case on my side my 2 stages are processing exactly the same jobs that takes 2 hours each, we are not talking about instantly status appearance . As shown in below screenshots, the processing stage that is showing wrong Passed status (PUSH TE2), is showing the triggered builds properly. As for the stage showing processing status (PUSH TE1), the Triggered Builds section does not exist.!image-2018-08-20-19-51-36-113.png|width=410,height=269!!image-2018-08-20-19-53-40-887.png|width=501,height=247! 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Vivek Pandey, as a summary the expected behavior is to show processing stages as Processing and to be able to access the Triggered Builds upon clicking on the stage. 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis edited a comment on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry [~vivek], but this is not the case on my side. As shown in below screenshots, the processing stage that is showing wrong Passed status (PUSH TE2) , is showing the triggered builds properly. As for the stage showing processing status (PUSH TE1) , the Triggered Builds section does not exist.!image-2018-08-20-19-51-36-113.png|width=410,height=269!!image-2018-08-20-19-53-40-887.png|width=501,height=247! 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis edited a comment on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry [~vivek], but this is not the case on my side. As shown in below screenshot screenshots , the processing stage that is showing wrong status, is showing the triggered builds properly ; as . As for the stage showing processing status, the Triggered Builds are empty section does not exist .!image-2018-08-20-19-51-36-113.png|width=410,height=269!!image-2018-08-20-19-53-40-887.png|width=501,height=247! 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Vivek Pandey As seen in my previous comment, the issue is that in Blue Ocean, when clicking on the upper stage it is giving me the details of the Parent stage (Pushing 2 Tests) instead of the child (PUSH TE1) and when selecting the bottom stage it is giving me the details of the right stage (PUSH TE2) but with wrong status. 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry Vivek Pandey, but this not the case on my side. As shown in below screenshot, the processing stage that is showing wrong status, is showing the triggered builds properly; as for the stage showing processing the Triggered Builds are empty. 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Change By: Elie Kassis Attachment: image-2018-08-20-19-53-40-887.png 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Change By: Elie Kassis Attachment: image-2018-08-20-19-51-36-113.png 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-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Vivek Pandey Yes indeed, when you click on the stage shown as Processing, the steps are not shown. As for the other processing stage shown wrongly as Passed, its steps are shown and can be selected. 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.
