[JIRA] (JENKINS-25548) StageStep should reject duplicate stage names

[email protected] (JIRA) Tue, 01 Nov 2016 07:32:16 -0700

Title: Message Title

Jesse Glick commented on

Right. I think at most a brief warning should be issued to the log in cases where a stage uses the same name as an earlier stage at the same nesting level. Thus in Timothy Clarke’s case, no warning would be issued for

 
                                                                for (env in ['linux', 'win']) {
  stage(env) {
    node(env) {
      stage('Building') {
        // …
      }
      stage('Testing') {
        // …
      }
    }
  }
}
 
                                                            

Here win » Building would not be considered a duplicate of linux » Building, since a sufficiently discriminating UI, such as the Pipeline Steps table, would show the structure. (Currently the Stage View plugin shows all stages undifferentiated at top level, and last I checked Blue Ocean is still working out a policy.)

Add Comment

This message was sent by Atlassian JIRA

--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-25548) StageStep should reject duplicate stage names

Reply via email to