[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Adam Carroll commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax Thanks Jesse Glick and An Tran for digging into this more! I personally am not concerned whether or not this is a bug or improvement, as long as it is fixed . It does sound a lot like a bug to me, but I do understand the argument for it being an improvement. Whatever the best path to resolution is will be fine with me. Based on the tickets An Tran linked above, it looks like others desire this functionality as well. 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-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title
Adam Carroll created an issue
Jenkins / JENKINS-55438
Allow sequential stages inside parallel in Scripted syntax
Issue Type:
Improvement
Assignee:
Andrew Bayer
Attachments:
exampleParallelSequential.PNG, exampleParallelSequentialIncorrect.PNG
Components:
pipeline, pipeline-model-definition-plugin
Created:
2019-01-07 22:06
Labels:
pipeline script scripted parallel sequential
Priority:
Minor
Reporter:
Adam Carroll
Similar to JENKINS-46809, I would like the Blue Ocean GUI to properly visualize multiple stages in sequence that are all parallel of each other. Below is an example image of what this looks like using declarative syntax (working): Here is the declarative example code I wrote to generate the example image:
pipeline {
agent { label 'master' }
stages {
stage('Build and Test') {
parallel {
stage("Build and Test Linux") {
stages {
stage("Build (Linux)") {
agent any
steps {
echo "Inside for loop 1"
}
}
stage("Test (Linux)") {
agent any
steps {
echo "Inside for loop 2"
}
}
}
}
stage("Build and Test Windows") {
stages {
stage("Build (Windows)") {
agent any
steps {
echo "Insid
[JIRA] (JENKINS-52209) [Cancelling nested steps due to timeout] aborts a job prematurely
Title: Message Title Adam Carroll commented on JENKINS-52209 Re: [Cancelling nested steps due to timeout] aborts a job prematurely I had this happen to me as well, the last 6 function calls of the OP match my last 6. It appears that deleteRecursive times out, as I have a number of agents that I was looping over to clean up and one of them got the java.lang.InterruptedException after exactly 5 minutes and 0 seconds of runtime. There is no timeout wrapper around this stage (other timeouts in the pipeline are 10 minutes anyway). This is in a cleanup stage using a multibranch pipeline (I unfortunately cannot share my Jenkinsfile). 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-53048) Parallel sequential stages not rendering correctly
Title: Message Title
Adam Carroll commented on JENKINS-53048
Re: Parallel sequential stages not rendering correctly
I recently updated to use the newest version of BlueOcean (1.9) and this behavior does not work for a scripted pipeline, only declarative. My sequential nodes end up squashed into one stage. Is it expected to work for scripted? My basic scripted pipeline structure looks like this: stage("Build and test") { parallel linux: { node("nodeA") { ... } node("nodeB") { .. } }, windows: { .
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.
