Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: blueocean-plugin
-
Labels:None
-
Similar Issues:
-
Epic Link:
-
Sprint:indian, arctic, tasman
Description
I saw something strange while testing blue ocean on b10
Here's the pipeline:
node {
checkout scm
stage ('Build1') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build2') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build3') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build4') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build5') {
sh 'ping -c 10 www.apple.com'
}
}
This is what the initial build looks like:
Ideally we should have a regression test for this problem.
Attachments
Activity
I tried and this seems too timing sensitive to be able to pick up with the ATH
Nice one Michael Neale. Not sure why my example didn't work... scratches head
I can't consistently reproduce this - can anyone else?
EDIT: got it, needs to have something happen before a stage opens :
node {
sh 'ping -c 10 www.apple.com'
stage ('Build1') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build2') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build3') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build4') {
sh 'ping -c 10 www.apple.com'
}
stage ('Build5') {
sh 'ping -c 10 www.apple.com'
}
}
checkout scm will also do that - is timing sensitive.
Thanks Thorsten Scherler, I think perhaps Tom FENNELLY might be able to tackle this later this week?
Vivek is out for thanksgiving - Tom FENNELLY able to take a look?
Michael Neale yeah you are right I was able to reproduce it only once before. I will try your scripts now.