[JIRA] (JENKINS-42734) Adding a parallel branch with no name results in a slightly bad Jenkinsfile

[mne...@cloudbees.com (JIRA)]

Title: Message Title

Michael Neale created an issue   Jenkins / JENKINS-42734 Adding a parallel branch with no name results in a slightly bad Jenkinsfile Issue Type: Bug Assignee: Keith Zantow Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Mar/14 1:33 AM Priority: Major Reporter: Michael Neale If you add a parallel branch of execution in the editor, add some steps, and save - it will save correctly, however it isn't a very good Jenkinsfile.    Loading it up once it has completed a run will result in an error to visualise. The Jenkinsfile will end up looking like:    Note that the branch name is empty string - this seems to upset declarative. I am not sure it executes that branch.  stage('Static Analysis') { steps { parallel( "Static Analysis": { sh 'mvn findbugs:findbugs' }, "": { echo 'rewrewqrewq' } ) } } } In any case, a branch should be required to be named, so I think this should be a validation error right? OR the editor should name that branch it creates.    To reproduce: take an existing stage with at least one step, add a parallel branch, add steps to it (but do not name it)  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.