[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-53129) Parallel sequential stages in Blue Ocean showing wrong status
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-53129 Parallel sequential stages in Blue Ocean showing wrong status Change By: Olivier Lamy 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 sequential stages in Blue Ocean showing wrong status
Title: Message Title Olivier Lamy closed an issue as Fixed please open an other issue regarding the "Triggered Builds" Jenkins / JENKINS-53129 Parallel sequential stages in Blue Ocean showing wrong status Change By: Olivier Lamy Status: Reopened Closed 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 Olivier Lamy commented on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds Elie Kassis please stop hijacking this issue. You reopen it and changing the description. This is totally wrong! it's a thread in a mailing list. So please open a new issue with correct 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-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 Olivier Lamy edited a comment on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds *Triggered Builds but* how do you trigger the job jobs ? 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 Olivier Lamy commented on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds how do you trigger the job? 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 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.
