[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Stuart Rowe edited a comment on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I've been looking into this as well. What I've found so far: - The downstream runs have an associated [BuildUpstreamNodeAction|https://github.com/jenkinsci/pipeline-build-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildUpstreamNodeAction.java] contributed by the build step. - The BuildUpstreamNodeAction action has an upstreamNodeId pointing back to the build step that triggered the downstream run. - This [DownstreamJobListener|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/DownstreamJobListener.java] adds a [NodeDownstreamBuildAction|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/NodeDownstreamBuildAction.java] to the node pointed to by the upstreamNodeId . - This upstreamNodeId doesn't match the id of the node typically selected when viewing the Blue Ocean pipeline graph (that node is typically a stage or parallel branch node) - There's code in [PipelineNodeGraphVisitor.java|https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/rest/impl/pipeline/PipelineNodeGraphVisitor.java] that accumulates actions from nodes within a branch or stage and then adds them to the node for that branch or stage. I believe this is the source of the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Stuart Rowe commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I've been looking into this as well. What I've found so far: The downstream runs have an associated BuildUpstreamNodeAction contributed by the build step. The BuildUpstreamNodeAction action has an upstreamNodeId pointing back to the build step that triggered the downstream run. This upstreamNodeId doesn't match the id of the node typically selected when viewing the Blue Ocean pipeline graph (that node is typically a stage or parallel branch node) There's code in PipelineNodeGraphVisitor.java that accumulates actions from nodes within a branch or stage and then adds them to the node for that branch or stage. I believe this is the source of the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.174511.1474269026000.30.1582739821725%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Luis Roalter commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Sometimes it works. but not always. For some reasons the NodeDownstreamBuildAction is missing when using the api /blue/rest/organizations/jenkins/pipelines/ When going closer into /blue/rest/organizations/jenkins/pipelines//runs/x/nodes/y/ the information is missing in this endpoint too. Funny fact, I've debugged it with the Script console by replaying the code from https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-api-impl/src/main/java/io/jenkins/blueocean/listeners/DownstreamJobListener.java. This works and all the triggered builds are there. But for me it's too complex to dig into the blue-ocean rest and debug there. Any suggestion from anyone how to debug it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.174511.1474269026000.7295.1582736161375%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Ryan Stewart commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I have raised a bug for this JENKINS-60995 as it is a regression of existing functionality Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.174511.1474269026000.2277.1580992381631%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing: {code:java}def getBlueOceanLink(obj, jobName) { def buildNumber if(obj instanceof Exception) {obj.toString().split(" ").each { if(it.contains("#")) {buildNumber = it.substring(1) }} } else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {buildNumber = obj.getNumber() } else {return "Can not determine Blue Ocean link!!!" } return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"}// Wrapper:def linkBuild(job, parameters) {def buildInfotry {buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)} catch (Exception e) {println getBlueOceanLink(e, job)throw e}println getBlueOceanLink(buildInfo, job)}// Usage:stage ("My stage") { linkBuild("My job", [ string(name: "my param", value: some_value) ])}{code} If anybody has come up with something better I would love to hear it!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing: {code:java}def getBlueOceanLink(obj, jobName) { def buildNumber if(obj instanceof Exception) {obj.toString().split(" ").each { if(it.contains("#")) {buildNumber = it.substring(1) }} } else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {buildNumber = obj.getNumber() } else {return "Can not determine Blue Ocean link!!!" } return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"}// Wrapper:def linkBuild(job, parameters) {def buildInfotry {buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)} catch (Exception e) {println getBlueOceanLink(e, job)throw e}println getBlueOceanLink(buildInfo, job)}// Usage:stage ("My stage") { linkBuild("My job", [ string(name: "my param", value: some_value) ])}{code} If anybody has come up with something better I would love to hear it!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing: {code:java}def getBlueOceanLink(obj, jobName) { def buildNumber if(obj instanceof Exception) {obj.toString().split(" ").each { if(it.contains("#")) {buildNumber = it.substring(1) }} } else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {buildNumber = obj.getNumber() } else {return "Can not determine Blue Ocean link!!!" } return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"}// Wrapper:def linkBuild(job, parameters) {def buildInfotry {buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)} catch (Exception e) {println getBlueOceanLink(e, job)throw e}println getBlueOceanLink(buildInfo, job)}// Usage:stage ("My stage") { linkBuild("My job", [ string(name: "my param", value: some_value) ])}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing:
def getBlueOceanLink(obj, jobName) {
def buildNumber
if(obj instanceof Exception) {
obj.toString().split(" ").each {
if(it.contains("#")) {
buildNumber = it.substring(1)
}
}
} else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {
buildNumber = obj.getNumber()
} else {
return "Can not determine Blue Ocean link!!!"
}
return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"
}
// Wrapper:
def linkBuild(job, parameters) {
def buildInfo
try {
buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)
} catch (Exception e) {
println getBlueOceanLink(e, job)
throw e
}
println getBlueOceanLink(buildInfo, job)
}
// Usage:
stage ("My stage") {
linkBuild("My job", [
string(name: "my param", value: some_value)
])
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title yanli wu commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step It is not work with Blue Ocean 1.19.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.174511.1474269026000.7256.1569666781152%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title yanli wu updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: yanli wu Attachment: image-2019-09-28-18-31-11-339.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.174511.1474269026000.7194.1569666721896%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Joakim Nyman commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I just installed 1.18.1 in hope of getting the "Starting building:" to be clickable but it is not. What is the status here? 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.174511.1474269026000.9402.1566805201730%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald assigned an issue to Unassigned Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Assignee: Josh McDonald 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.174511.1474269026000.9356.1565131864911%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Ross M commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step do we know what version this feature works. because it was working before 1.7.* 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.174511.1474269026000.9152.1565121541487%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Tim Huang edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
I have more information on the matter - I was triggering downstream jobs within a `parallel` step (not sure if this has anything to do with it ) . In an earlier sequential stage, if I trigger another build job, it causes the ones in the parallel steps (that didn't show up before) to show up in the "Triggered Jobs" section. Below is my groovy script. In the first sequential stage there is a downstream no-op job I made that, when triggered, seems to make the "Triggered Jobs" section show up for the other two downstream jobs that are triggered in the parallel stages further down. Without the no-op job, the "Triggered Jobs" section won't show up for the other two. The formatting of this code won't paste right (missing newlines here and there), so apologies.{noformat}pipeline { agent none options { // Ideally, PRs build in less than 5 timeout(time: 15, unit: 'MINUTES') } environment { CI = 'true' AWS_ACCESS_KEY_ID = credentials('aws-access-key-id-test') AWS_SECRET_ACCESS_KEY = credentials('aws-secret-access-key-test') } stages { stage('Abort previous builds on PR') { steps {// Not sure how this works, but… https://stackoverflow.com/a/52811034milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID) - 1milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID)// NOTE: Triggering this no-op job makes all Triggered Builds show up!!!build 'Utilities/TriggeringThisInStepsMakesTriggeredBuildsShowUp' } } stage('PR tests') { failFast false parallel {stage('Linting & formatting') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Format & Syntax (backend)',description: 'Checking code quality…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^backend"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Skipped (no changes).') } catch (e) {echo "Changes found, running tests."ansiColor('xterm') { // Check for it-block .only() calls which skip all other // tests in a suite. These should NEVER be version-checked. sh "! git grep '\\'" sh 'rm -rf ./frontend' sh 'yarn' sh 'yarn eslint ./backend' sh 'yarn prettier -c "./backend/**/*.js"' pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Squeaky clean! You win today.')} } } } post { failure { script {pullRequest.createStatus(status: 'failure', context: 'Format & Syntax (backend)', description: 'Wow, did you even look at how malformed your code is?', targetUrl: env.RUN_DISPLAY_URL) } } }}stage('Frontend tests') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Unit tests (frontend)',description: 'Making sure you didn\'t break anything…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^frontend"'sh '! git diff --name-only ^HEAD origin/trunk | grep "^shared-utilities"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context: 'Unit tests (frontend)', description: 'Skipped
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Tim Huang edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
I have more information on the matter - I was triggering downstream jobs within a `parallel` step (not sure if this has anything to do with it). In an earlier sequential stage, if I trigger another downstream build job, it causes itself and the ones in the parallel steps (that didn't show up before) to show up in the their respective "Triggered Jobs" section sections . Below is my groovy script. In the first sequential stage there is a downstream no-op job I made that, when triggered, seems to make the "Triggered Jobs" section show up for the other two downstream jobs that are triggered in the parallel stages further down. Without the no-op job, the "Triggered Jobs" section won't show up for the other two. The formatting of this code won't paste right (missing newlines here and there), so apologies.{noformat}pipeline { agent none options { // Ideally, PRs build in less than 5 timeout(time: 15, unit: 'MINUTES') } environment { CI = 'true' AWS_ACCESS_KEY_ID = credentials('aws-access-key-id-test') AWS_SECRET_ACCESS_KEY = credentials('aws-secret-access-key-test') } stages { stage('Abort previous builds on PR') { steps {// Not sure how this works, but… https://stackoverflow.com/a/52811034milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID) - 1milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID)// NOTE: Triggering this no-op job makes all Triggered Builds show up!!!build 'Utilities/TriggeringThisInStepsMakesTriggeredBuildsShowUp' } } stage('PR tests') { failFast false parallel {stage('Linting & formatting') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Format & Syntax (backend)',description: 'Checking code quality…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^backend"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Skipped (no changes).') } catch (e) {echo "Changes found, running tests."ansiColor('xterm') { // Check for it-block .only() calls which skip all other // tests in a suite. These should NEVER be version-checked. sh "! git grep '\\'" sh 'rm -rf ./frontend' sh 'yarn' sh 'yarn eslint ./backend' sh 'yarn prettier -c "./backend/**/*.js"' pullRequest.createStatus(status: 'success', context: 'Format & Syntax (backend)', description: 'Squeaky clean! You win today.')} } } } post { failure { script {pullRequest.createStatus(status: 'failure', context: 'Format & Syntax (backend)', description: 'Wow, did you even look at how malformed your code is?', targetUrl: env.RUN_DISPLAY_URL) } } }}stage('Frontend tests') { agent { node { label 'Node' } } steps { script { pullRequest.createStatus(status: 'pending',context: 'Unit tests (frontend)',description: 'Making sure you didn\'t break anything…',targetUrl: env.RUN_DISPLAY_URL) try {sh '! git diff --name-only ^HEAD origin/trunk | grep "^frontend"'sh '! git diff --name-only ^HEAD origin/trunk | grep "^shared-utilities"'echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success', context:
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Tim Huang updated JENKINS-38339 Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Tim Huang Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.9555.1563067023475%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Tim Huang commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
I have more information on the matter - I was triggering downstream jobs within a `parallel` step (not sure if this has anything to do with it. In an earlier sequential stage, if I trigger another build job, it causes the ones in the parallel steps (that didn't show up before) to show up in the "Triggered Jobs" section. Below is my groovy script. In the first sequential stage there is a downstream no-op job I made that, when triggered, seems to make the "Triggered Jobs" section show up for the other two downstream jobs that are triggered in the parallel stages further down. Without the no-op job, the "Triggered Jobs" section won't show up for the other two. The formatting of this code won't paste right (missing newlines here and there), so apologies.
pipeline {
agent none options {
// Ideally, PRs build in less than 5
timeout(time: 15, unit: 'MINUTES')
} environment {
CI = 'true'
AWS_ACCESS_KEY_ID = credentials('aws-access-key-id-test')
AWS_SECRET_ACCESS_KEY = credentials('aws-secret-access-key-test')
} stages {
stage('Abort previous builds on PR') {
steps {
// Not sure how this works, but… https://stackoverflow.com/a/52811034
milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID) - 1
milestone label: '', ordinal: Integer.parseInt(env.BUILD_ID)
// NOTE: Triggering this no-op job makes all Triggered Builds show up!!!
build 'Utilities/TriggeringThisInStepsMakesTriggeredBuildsShowUp'
}
} stage('PR tests') {
failFast false
parallel {
stage('Linting & formatting') {
agent {
node {
label 'Node'
}
} steps {
script {
pullRequest.createStatus(status: 'pending',
context: 'Format & Syntax (backend)',
description: 'Checking code quality…',
targetUrl: env.RUN_DISPLAY_URL) try {
sh '! git diff --name-only ^HEAD origin/trunk | grep "^backend"'
echo "No changes found, skipping tests."pullRequest.createStatus(status: 'success',
context: 'Format & Syntax (backend)',
description: 'Skipped (no changes).')
} catch (e) {
echo "Changes found, running tests."ansiColor('xterm') {
// Check for it-block .only() calls which skip all other
// tests in a suite. These should NEVER be version-checked.
sh "! git grep '\\'" sh 'rm -rf ./frontend'
sh 'yarn'
sh 'yarn eslint ./backend'
sh 'yarn prettier -c "./backend/**/*.js"' pullRequest.createStatus(status: 'success',
context: 'Format & Syntax (backend)',
description: 'Squeaky clean! You win today.')
}
}
}
}
post {
failure {
script {
pullRequest.createStatus(status: 'failure',
context: 'Format & Syntax (backend)',
description: 'Wow, did you even look at how malformed your code is?',
targetUrl: env.RUN_DISPLAY_URL)
}
}
}
}stage('Frontend tests') {
agent {
node {
label 'Node'
}
} steps {
script {
pullRequest.createStatus(status: 'pending',
context: 'Unit tests (frontend)',
description: 'Making sure you didn\'t break anything…',
targetUrl: env.RUN_DISPLAY_URL) try {
sh '! git diff --name-only ^HEAD origin/trunk | grep "^frontend"'
sh '!
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Tim Huang commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Hello, I am on Blue Ocean 1.17.0, and I do not see a link to my downstream jobs. Was there a regression? 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.174511.1474269026000.9437.1563059401118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Tim Huang updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Tim Huang Attachment: Captura de Pantalla 2019-07-13 a la(s) 4.08.07 p. m..png Attachment: Captura de Pantalla 2019-07-13 a la(s) 4.08.18 p. m..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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.9378.1563059341660%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Gavin Mogan updated JENKINS-38339 Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Gavin Mogan Status: Fixed but Unreleased Resolved Released As: 1.14.0 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald updated JENKINS-38339 Fixed in fc3e3a9f5cd13f535d88a173499bb929478f5b1f Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Status: Reopened Fixed but Unreleased Resolution: 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Pull request to fix the regression (and extra tests) is here: https://github.com/jenkinsci/blueocean-plugin/pull/1933 - give it a few days as most of the reviewers are away from the office right now. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald updated JENKINS-38339 Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Resolution: Fixed 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Denis Zakharov commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step It was rollbacked in BO 1.13.2. Can someone reopen 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Denis Zakharov commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Josh McDonald thank you. When can we get build with this fix? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald updated JENKINS-38339 Fixed in master @ 3a9b64269d037ce25b17b3e088e29cfde43fe098 Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Status: Reopened Fixed but Unreleased Resolution: 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Fix PR here: https://github.com/jenkinsci/blueocean-plugin/pull/1918 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Still trying to figure this one out, but it's definitely a bug, and only seems to affect declarative pipelines, which makes for a nice test case of the same pipeline in both declarative and original pipeline versions. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Yair Ogen commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step For me adding an empty non-build step - doesn't solve the issue. I see links but only after the job was completed (either success or failure) 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Hari Ananthan commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
Thanks a lot Josh. Here is a testcase and some pictures to illustrate the bug in case the description wasn't clear. P1_1 and P1_2 show links, but P2 doesn't. I am getting around now by simply adding a dummy "stage" before P2 in that branch of the parallel stage. pipeline { agent any stages { stage('Parallel Stage') { parallel { stage('P1') { stages { stage('P1_1') { steps { build job: 'child', parameters: [[$class: 'StringParameterValue', name: 'STAGE', value: 'P1_1']] } } stage('P1_2') { steps { build job: 'child', parameters: [[$class: 'StringParameterValue', name: 'STAGE', value: 'P1_2']] } } } } stage('P2') { steps \{ build job: 'child', parameters: [[$class: 'StringParameterValue', name: 'STAGE', value: 'P2']] } } } } } }
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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Hari Ananthan updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Hari Ananthan Attachment: P1_1.JPG Attachment: P1_2.JPG Attachment: P2.JPG 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald reopened an issue I'll look into this a bit today. Might be more difficult than it seems tho. Fairly warned, be ye, says I. I'll keep you guys posted. Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Resolution: Fixed Status: Resolved 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Hari Ananthan edited a comment on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Build Link for jobs launched inside parallel stages would be most appreciated! Without this, we are kinda stuck having to open so many windows to track what's going on. Especially since many of our stages are propagate : false and/or wait: false. EDIT : Actually the exact bug is that Links don't show up if a parallel stage has *only one build.*If parallel stage has 2 or more builds in series, then the links show up. For non-parallel stages, the URL shows up, but only after the child build is finished. So another request - create the URL link while the job is running. Some of our jobs take many minutes or hours and so having a live link would be really really useful.Thank you! 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Hari Ananthan commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Build Link for jobs launched inside parallel stages would be most appreciated! Without this, we are kinda stuck having to open so many windows to track what's going on. Especially since many of our stages are propagate : false and/or wait: false. For non-parallel stages, the URL shows up, but only after the child build is finished. So another request - create the URL link while the job is running. Some of our jobs take many minutes or hours and so having a live link would be really really useful. Thank you! 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Yair Ogen commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Denis Zakharov I tried this. Doesn't work. I get the links only after the triggered builds finish. During the parallel run, I only see the build name and the number in the console but no link in blue ocean ui. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Denis Zakharov edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
Try to use parallel sequential stages syntax. There are only one problem if we have N nested stages we get job links only in first N-1. You We should add last stage in row w/o running build in it.{code:java}pipeline{agent anystages{stage('Nested parallel'){parallel{stage("parallel 1"){stages{ stage("Nested 1 with child in it"){ steps{ script{ build "TestJob" } } } stage('Nested 2 with child in it'){ steps{ script{ build "TestJob" } } } stage('Nested 3 w/o childs'){ steps{ echo "E-mail" } }}}stage("parallel 2"){stages{ stage("Nested 1 with child in it"){ steps{ script{ build "TestJob" } } } stage('Nested 2 with child in it'){ steps{ script{ build "TestJob" } } } stage('Nested 3 w/o childs'){ steps{ echo "E-mail" } }}}}}}}{code}
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
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Denis Zakharov edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
Try to use parallel sequential stages syntax. There are only one problem if you we have N nested stages we get job links only in first N-1. You should add last stage in row w/o running build in it.{code:java}pipeline{agent anystages{stage('Nested parallel'){parallel{stage("parallel 1"){stages{ stage("Nested 1 with child in it"){ steps{ script{ build "TestJob" } } } stage('Nested 2 with child in it'){ steps{ script{ build "TestJob" } } } stage('Nested 3 w/o childs'){ steps{ echo "E-mail" } }}}stage("parallel 2"){stages{ stage("Nested 1 with child in it"){ steps{ script{ build "TestJob" } } } stage('Nested 2 with child in it'){ steps{ script{ build "TestJob" } } } stage('Nested 3 w/o childs'){ steps{ echo "E-mail" } }}}}}}}{code}
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
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Denis Zakharov commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
Try to use parallel sequential stages syntax. There are only one problem if you have N nested stages we get job links only in first N-1. You should add last stage in row w/o running build in it.
pipeline{
agent any
stages{
stage('Nested parallel'){
parallel{
stage("parallel 1"){
stages{
stage("Nested 1 with child in it"){
steps{
script{
build "TestJob"
}
}
}
stage('Nested 2 with child in it'){
steps{
script{
build "TestJob"
}
}
}
stage('Nested 3 w/o childs'){
steps{
echo "E-mail"
}
}
}
}
stage("parallel 2"){
stages{
stage("Nested 1 with child in it"){
steps{
script{
build "TestJob"
}
}
}
stage('Nested 2 with child in it'){
steps{
script{
build "TestJob"
}
}
}
stage('Nested 3 w/o childs'){
steps{
echo "E-mail"
}
}
}
}
}
}
}
}
Add Comment
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Steven Foster commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I have just updated blue ocean from 1.5 (where this UI feature was originally introduced, and working fine) to 1.10.1 and no longer have links to downstream jobs in my parallel steps. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Denis Zakharov commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Behavior and appearance in single and in parallel stages have difference. There are no link on child job if it was executed from parallel block. Can someone change bug status? 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Yair Ogen commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Vincent Latombe can you update status? As Mike above I don't see links for triggered jobs in parallel step, only after the triggered job is done. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Mike Bolesta commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I'm also seeing this issue when the triggered build is inside a parallel stage. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Andrei Muresianu commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
It is still a problem in December 2018.
stage('Test Stack') {
parallel {
stage('Functional Tests') {
steps {
build job: 'TEST-functional'
}
}
stage('View Tests') {
steps {
build job: 'TEST-view'
}
}
}
post {
failure {
echo 'Some of the functional/view tests failed. Tearing down the stack.'
build job: 'TEST-teardown'
}
}
}
None of TEST-functional, TEST-view, TEST-teardown are visible in BlueOcean (it looks like even the echo message got lost) However, the console output references all of the jobs - no issues there.
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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Andrei Muresianu updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Andrei Muresianu Attachment: image-2018-12-05-01-11-03-261.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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Jan Kacik commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step It is not working for parallel stages in declarative pipeline. 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Jan Bernlöhr commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
How can we enabled this feature? We are using BlueOcean 1.82 with declaraitve pipelines and do not see links.
stage('launch builds') {
parallel {
stage('stereo/offline') {
steps {
build job: 'rebuild',
parameters:[
string(name: 'CONFIG_TO_BUILD', value: 'stereo/offline')
],
propagate: true,
wait: true
}
}
stage('second_config') {
steps {
build job: 'rebuild',
parameters:[
string(name: 'CONFIG_TO_BUILD', value: 'second_config')
],
propagate: true,
wait: true
}
}
}
}
The invoked job 'rebuild' is also a declarative pipeline.
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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Jan Bernlöhr updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Jan Bernlöhr Attachment: image-2018-09-10-11-54-51-888.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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Steven Foster commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Is there a way to aggregate the triggered builds within a parallel stage? I'm launching 12 or so builds as a parallel stage (the whole build is basically just a dummy/launchpad for other builds) and clicking each individual stage to get the downstream link is very slightly bothersome Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Craig Rodrigues commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I tested this fix out in 1.5 beta-2. It works well! I found one minor problem in the UI, where it is difficult to identify which stage is selected in the UI. Keith Zantow wrote up this ticket, because I was having temporary problems with my JIRA login acces: JENKINS-50408 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step It should be fine. It definitely won't work for classic upstream jobs tho. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Michael Neale commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Steven Visagie good questoin, an experiment (if you have the ability to build it) would be worthwhile, but I expect it would work the same, as it doesn't necessarily care what is in the "build" step for things it triggers (ie what type it is) so ideally it would just work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald updated JENKINS-38339 Merged @ 203324c8913426d9a9fd6a7cfe82f40c157eacec Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald updated JENKINS-38339 Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step UI changes PR: https://github.com/jenkinsci/blueocean-plugin/pull/1675 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Vivek Pandey Sprint: Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.4 - beta 3, Blue Ocean 1.5 - beta 1 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Steven Visagie commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step We're extremely interested in having this functionality available. Will the proposed link work with both downstream pipelines and Jenkins classic jobs? We use a combination of both in our use case. If the downstream is a pipeline, will it navigate to the running pipeline in Blue Ocean? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title James Dumay commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Tomasz Śniatowski we certainly plan for it to be a link of some kind. We will upload a design on this issue when we get to this one so you can give us feedback Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Tomasz Śniatowski commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step We're trying to avoid UI issues when there are sub-steps in a parallel pipeline stage (JENKINS-38442) by triggering sub-builds instead – but as the UI has no links to these sub-builds the experience is not great either way. Any chance triggered build info could be a link? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: James Dumay Summary: Unable to browse to externally UI for downstream jobs launched builds [missing log decoration] with 'build' step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
