[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay resolved as Not A Defect Pre-bismuth issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay assigned an issue to Michael Neale Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Assignee: Vivek Pandey Michael Neale 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay commented on JENKINS-38947 Re: A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Michael Neale is this one still relevant? 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Sprint: pannonian 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Sprint: tasman 2 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Sprint: tasman 2 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Sprint: arctic 2 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Sprint: arctic 2 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Sprint: arctic 2 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: James Dumay Sprint: indian arctic 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: Michael Neale Priority: Critical Major 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale commented on JENKINS-38947 Re: A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Vivek Pandey I think this should be looked at once bismuth is in. This is a problem I think with the api ... needs investigation. 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: Michael Neale Sprint: indian 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Change By:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The job: https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/master/415/pipeline !Screen Shot 2016-10-13 at 1.07.28 pm.png|thumbnail! (this should be showing a simple list of steps, no stages, and many more steps than that). The Jenkinsfile to see this: {noformat}#!groovy// only 20 buildsproperties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))])node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside {withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try {sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30"sh "node ./bin/checkdeps.js"sh "node ./bin/checkshrinkwrap.js"step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi'])triggerATH(); } catch(err) {currentBuild.result = "FAILURE" } finally {sendhipchat()deleteDir() }} } }}def triggerATH() {// Assemble and archive the HPI plugins that the ATH should use.// The ATH build can copy this artifact and use it, saving the time it// would otherwise spend building and assembling again.sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins'archiveArtifacts artifacts: 'blueocean/target/ath-plugins.tar.gz'// Trigger the ATH, but don't wait for it.try {echo "Will attempt to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'."build(job: "ATH-Jenkinsfile/${env.BRANCH_NAME}",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)} catch (e1) {echo "Failed to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'. Will try running the ATH 'master' branch."build(job: "ATH-Jenkinsfile/master",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Change By:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The job: https://ci.blueocean.io/blue/organizations/jenkins/blueocean/detail/master/415/pipeline !Screen Shot 2016-10-13 at 1.07.28 pm.png|thumbnail! The Jenkinsfile to see this: {noformat}#!groovy// only 20 buildsproperties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))])node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside {withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try {sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30"sh "node ./bin/checkdeps.js"sh "node ./bin/checkshrinkwrap.js"step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi'])triggerATH(); } catch(err) {currentBuild.result = "FAILURE" } finally {sendhipchat()deleteDir() }} } }}def triggerATH() {// Assemble and archive the HPI plugins that the ATH should use.// The ATH build can copy this artifact and use it, saving the time it// would otherwise spend building and assembling again.sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins'archiveArtifacts artifacts: 'blueocean/target/ath-plugins.tar.gz'// Trigger the ATH, but don't wait for it.try {echo "Will attempt to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'."build(job: "ATH-Jenkinsfile/${env.BRANCH_NAME}",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)} catch (e1) {echo "Failed to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'. Will try running the ATH 'master' branch."build(job: "ATH-Jenkinsfile/master",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)}}def sendhipchat() {res = currentBu
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38947 A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage Change By: Michael Neale Attachment: Screen Shot 2016-10-13 at 1.07.28 pm.png 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.
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Change By:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The Jenkinsfile to see this: ``` {noformat} #!groovy// only 20 buildsproperties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))])node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside {withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try {sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30"sh "node ./bin/checkdeps.js"sh "node ./bin/checkshrinkwrap.js"step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi'])triggerATH(); } catch(err) {currentBuild.result = "FAILURE" } finally {sendhipchat()deleteDir() }} } }}def triggerATH() {// Assemble and archive the HPI plugins that the ATH should use.// The ATH build can copy this artifact and use it, saving the time it// would otherwise spend building and assembling again.sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins'archiveArtifacts artifacts: 'blueocean/target/ath-plugins.tar.gz'// Trigger the ATH, but don't wait for it.try {echo "Will attempt to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'."build(job: "ATH-Jenkinsfile/${env.BRANCH_NAME}",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)} catch (e1) {echo "Failed to run the ATH with the same branch name i.e. '${env.BRANCH_NAME}'. Will try running the ATH 'master' branch."build(job: "ATH-Jenkinsfile/master",parameters: [string(name: 'BLUEOCEAN_BRANCH_NAME', value: "${env.BRANCH_NAME}"), string(name: 'BUILD_NUM', value: "${env.BUILD_NUMBER}")],wait: false)}}def sendhipchat() {res = currentBuild.resultif(currentBuild.result == null) { res = "SUCCESS"}message = "${env.JOB_NAME} #${env.BUILD_NUMBER}, status: ${res} (Open)"
[JIRA] (JENKINS-38947) A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-38947
A pipeline with no stages that calls an external build does not show steps, but shows a "fake" stage
Issue Type:
Bug
Assignee:
Vivek Pandey
Components:
blueocean-plugin
Created:
2016/Oct/13 2:12 AM
Priority:
Critical
Reporter:
Michael Neale
This is hard to explain so I will put an image attached. Basically, the current Jenkinsfile for blueocean has no stages, but it does call the ATH job towards the end. In the stage view things are correct (classic) as there are no stages. However, in blue ocean a "fake stage" which appears to be the dispatching of this external shows up as a stage in the stage graph. All steps as part of the build are also hidden. It is most odd. The Jenkinsfile to see this: ``` #!groovy // only 20 builds properties([buildDiscarder(logRotator(artifactNumToKeepStr: '20', numToKeepStr: '20'))]) node { deleteDir() checkout scm configFileProvider([configFile(fileId: 'blueocean-maven-settings', targetLocation: 'settings.xml')]) { docker.image('cloudbees/java-build-tools').inside { withEnv(['GIT_COMMITTER_EMAIL=m...@hatescake.com','GIT_COMMITTER_NAME=Hates','GIT_AUTHOR_NAME=Cake','GIT_AUTHOR_EMAIL=ha...@cake.com']) { try { sh "mvn clean install -B -DcleanNode -Dmaven.test.failure.ignore -s settings.xml -Dmaven.artifact.threads=30" sh "node ./bin/checkdeps.js" sh "node ./bin/checkshrinkwrap.js" step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) step([$class: 'ArtifactArchiver', artifacts: '*/target/*.hpi']) triggerATH(); } catch(err) { currentBuild.result = "FAILURE" } finally { sendhipchat() deleteDir() } } } } } def triggerATH() { // Assemble and archive the HPI plugins that the ATH should use. // The ATH build can copy this artifact and use it, saving the time it // would otherwise spend building and assembling again. sh 'cd blueocean && mvn hpi:assemble-dependencies && tar -czvf target/ath-plugins.tar.gz target/plugins' archiveA
