[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Dmitry Seryogin commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" think the simplest reproduction of that kind of issue is a Pipeline like this Given you meant modulo 2 rather than 0, yeah, that does reproduce the problem just right - 3rd step is sitting there with 'waiting for run to start' until the step actually completes and the node renders with the green tick. 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.200110.1560887329000.3056.1567145400652%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title
Dmitry Seryogin edited a comment on JENKINS-58085
Re: BlueOcean UI stuck in "Waiting for run to start"
Whenever below pipeline (some steps taken out of earlier stages) that we use to deploy releases into a target environment runs and Delay is not 0, the Wait step completes successfully but the following Deploy stage then gets affected by the bug in question. If Delay is skipped due to the when-condition (be it a re-run or a 0 min delay), the pipeline then works as intended in BlueOcean. *Edit:* The problem surfaces consistently on each and every run against the test envrionments where 5min delay is enforced after having deployed to predelivery (where delay is 0). {code:java}pipeline { agent none parameters { gitParameter name: 'release', type: 'PT_TAG', branchFilter: 'origin/(.*)', tagFilter: 'v*', sortMode: 'DESCENDING_SMART', selectedValue: 'TOP', useRepository: 'repo' quickFilterEnabled: true, listSize: '5', description: 'git tag' choice name: 'environment', choices: getAdminNodes('admin'), description: 'target deployment environment' choice name: 'delay', choices: ['0 min', '1 min', '5 min', '10 min', '15 min'], description: 'delay before starting the deploy phase' choice name: 'delta_run', choices: ['Yes','No'], description: 'install only the delta compared to prior release)' booleanParam name: 'deploy_validation', defaultValue: false, description: 'issue additional sanity checks during deploy phase' } options { buildDiscarder(logRotator(numToKeepStr: '5', daysToKeepStr: '30')) timeout(time: 2, unit: 'HOURS') skipStagesAfterUnstable() timestamps() skipDefaultCheckout true } stages { stage ('SCM') { agent { label 'rel-sbox-pup-a01' } steps {cleanWs notFailBuild: truecheckout([ $class: 'GitSCM', branches: [[ name: "refs/tags/${params.release}" ]], userRemoteConfigs: [[ credentialsId: 'id', url: 'repo' ]]]) } } stage ('Prepare') { agent { label params.environment } steps {script { String node = env.environment.split('\\-')[1].toUpperCase() if ('CHI'.equals(node) || 'RHO'.equals(node)) { env.delay = '5 min' } else { env.delay = '0 min' println 'Not a test environment - commence immediate deployment' } readFile('/dsa/versions.ctl').split("\r?\n").each { String line -> if (line.equals(env.release)) { println env.release + ' is a known version for ' + env.environment + ', skip project notification' env.delay = '0 min' } } currentBuild.displayName = "#${BUILD_NUMBER} - " + node + " - ${params.release}"} } } stage ('Package') { agent { label 'rel-sbox-pup-a01' } steps {sh label: 'Gather Artefacts', script:""" if [ -z ${M2_HOME} ]; then echo "Maven not configured, abort further actions" exit 1 fi mvn -version env_id=`echo ${environment} | cut -d '-' -f2` case \$env_id in prede) mount_point_id="new";; *) mount_point_id=\$env_id esac mount_point=/dsa-\$mount_point_id ${WORKSPACE}/tools/mvn/svc_fetch_delivery.sh \$mount_point""" } } stage ('Preflight') { agent { label params.environment } steps {script { env.DELIVERY_DIR = sh(label: 'Delivery Path', script: """ ver_prefix=`echo ${release} | awk -F'_' '{print \$1 "_" \$2 "_next_"}'` delivery_base="/dsa/infrastructure" if [ ${deploy_validation} = "true" ]; thendelivery_dir=\$delivery_base/delivery/${release} elsedelivery_type="full"if [ ${delta_run} = "Yes" ]; then delivery_type="delta"fi
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title
Dmitry Seryogin edited a comment on JENKINS-58085
Re: BlueOcean UI stuck in "Waiting for run to start"
Whenever below pipeline (some steps taken out of earlier stages) that we use to deploy releases into a target environment runs and Delay is not 0, the Wait step completes successfully but the following Deploy stage then gets affected by the bug in question. If Delay is skipped due to the when-condition (be it a re-run or a 0 min delay), the pipeline then works as intended in BlueOcean. The problem surfaces consistently on each and every run against the test envrionments where 5min delay is enforced after having deployed to predelivery (where delay is 0) . {code :java }pipeline { agent none parameters { gitParameter name: 'release', type: 'PT_TAG', branchFilter: 'origin/(.*)', tagFilter: 'v*', sortMode: 'DESCENDING_SMART', selectedValue: 'TOP', useRepository: 'repo' quickFilterEnabled: true, listSize: '5', description: 'git tag' choice name: 'environment', choices: getAdminNodes('admin'), description: 'target deployment environment' choice name: 'delay', choices: ['0 min', '1 min', '5 min', '10 min', '15 min'], description: 'delay before starting the deploy phase' choice name: 'delta_run', choices: ['Yes','No'], description: 'install only the delta compared to prior release)' booleanParam name: 'deploy_validation', defaultValue: false, description: 'issue additional sanity checks during deploy phase' } options { buildDiscarder(logRotator(numToKeepStr: '5', daysToKeepStr: '30')) timeout(time: 2, unit: 'HOURS') skipStagesAfterUnstable() timestamps() skipDefaultCheckout true } stages { stage ('SCM') { agent { label 'rel-sbox-pup-a01' } steps {cleanWs notFailBuild: truecheckout([ $class: 'GitSCM', branches: [[ name: "refs/tags/${params.release}" ]], userRemoteConfigs: [[ credentialsId: 'id', url: 'repo' ]]]) } } stage ('Prepare') { agent { label params.environment } steps {script { String node = env.environment.split('\\-')[1].toUpperCase() if ('CHI'.equals(node) || 'RHO'.equals(node)) { env.delay = '5 min' } else { env.delay = '0 min' println 'Not a test environment - commence immediate deployment' } readFile('/dsa/versions.ctl').split("\r?\n").each { String line -> if (line.equals(env.release)) { println env.release + ' is a known version for ' + env.environment + ', skip project notification' env.delay = '0 min' } } currentBuild.displayName = "#${BUILD_NUMBER} - " + node + " - ${params.release}"} } } stage ('Package') { agent { label 'rel-sbox-pup-a01' } steps {sh label: 'Gather Artefacts', script:""" if [ -z ${M2_HOME} ]; then echo "Maven not configured, abort further actions" exit 1 fi mvn -version env_id=`echo ${environment} | cut -d '-' -f2` case \$env_id in prede) mount_point_id="new";; *) mount_point_id=\$env_id esac mount_point=/dsa-\$mount_point_id ${WORKSPACE}/tools/mvn/svc_fetch_delivery.sh \$mount_point""" } } stage ('Preflight') { agent { label params.environment } steps {script { env.DELIVERY_DIR = sh(label: 'Delivery Path', script: """ ver_prefix=`echo ${release} | awk -F'_' '{print \$1 "_" \$2 "_next_"}'` delivery_base="/dsa/infrastructure" if [ ${deploy_validation} = "true" ]; thendelivery_dir=\$delivery_base/delivery/${release} elsedelivery_type="full"if [ ${delta_run} = "Yes" ]; then delivery_type="delta"fi
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title
Dmitry Seryogin commented on JENKINS-58085
Re: BlueOcean UI stuck in "Waiting for run to start"
Whenever below pipeline (some steps taken out of earlier stages) that we use to deploy releases into a target environment runs and Delay is not 0, the Wait step completes successfully but the following Deploy stage then gets affected by the bug in question. If Delay is skipped due to the when-condition (be it a re-run or a 0 min delay), the pipeline then works as intended in BlueOcean. The problem surfaces consistently on each and every run against the test envrionments.
pipeline {
agent none
parameters {
gitParameter name: 'release',
type: 'PT_TAG',
branchFilter: 'origin/(.*)',
tagFilter: 'v*',
sortMode: 'DESCENDING_SMART',
selectedValue: 'TOP',
useRepository: 'repo'
quickFilterEnabled: true,
listSize: '5',
description: 'git tag'
choice name: 'environment',
choices: getAdminNodes('admin'),
description: 'target deployment environment'
choice name: 'delay',
choices: ['0 min', '1 min', '5 min', '10 min', '15 min'],
description: 'delay before starting the deploy phase'
choice name: 'delta_run',
choices: ['Yes','No'],
description: 'install only the delta compared to prior release)'
booleanParam name: 'deploy_validation',
defaultValue: false,
description: 'issue additional sanity checks during deploy phase'
}
options {
buildDiscarder(logRotator(numToKeepStr: '5', daysToKeepStr: '30'))
timeout(time: 2, unit: 'HOURS')
skipStagesAfterUnstable()
timestamps()
skipDefaultCheckout true
}
stages {
stage ('SCM') {
agent { label 'rel-sbox-pup-a01' }
steps {
cleanWs notFailBuild: true
checkout([
$class: 'GitSCM',
branches: [[ name: "refs/tags/${params.release}" ]],
userRemoteConfigs: [[
credentialsId: 'id',
url: 'repo'
]]
])
}
}
stage ('Prepare') {
agent { label params.environment }
steps {
script {
String node = env.environment.split('\\-')[1].toUpperCase()
if ('CHI'.equals(node) || 'RHO'.equals(node)) {
env.delay = '5 min'
} else {
env.delay = '0 min'
println 'Not a test environment - commence immediate deployment'
}
readFile('/dsa/versions.ctl').split("\r?\n").each { String line ->
if (line.equals(env.release)) {
println env.release + ' is a known version for ' + env.environment + ', skip project notification'
env.delay = '0 min'
}
}
currentBuild.displayName = "#${BUILD_NUMBER} - " + node + " - ${params.release}"
}
}
}
stage ('Package') {
agent { label 'rel-sbox-pup-a01' }
steps {
sh label: 'Gather Artefacts', script:
"""
if [ -z ${M2_HOME} ]; then
echo "Maven not configured, abort further actions"
exit 1
fi
mvn -version
env_id=`echo ${environment} | cut -d '-' -f2`
case \$env_id in
prede) mount_point_id="new";;
*) mount_point_id=\$env_id
esac
mount_point=/dsa-\$mount_point_id
${WORKSPACE}/tools/mvn/svc_fetch_delivery.sh \$mount_point
"""
}
}
stage ('Preflight') {
agent { label params.environment }
steps {
script {
env.DELIVERY_DIR = sh(label: 'Delivery Path',
script:
"""
ver_prefix=`echo ${release} | awk -F'_' '{print \$1 "_" \$2 "_next_"}'`
delivery_base="/dsa/infrastructure"
if [ ${deploy_validation} = "true" ]; then
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Dmitry Seryogin commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" With jenkins 2.164.1, after updating to 1.17.0 and 1.18 .0 subsequently, we are facing the same issue. We have multiple product versioning and deployment pipelines with when-conditions that alter the stage behaviour. Most pipelines have now been affected byt this problem where stages after when-conditon stages just appear dead with the 'waiting' message. 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.200110.1560887329000.1581.1565682120578%40Atlassian.JIRA.
