You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Material modifications on pipelines error with Group with name 'delivery_engineering' already exists
Environment
Basic environment details
Go Version: 20.1.0
JAVA Version: 13.0.1
OS: Linux 2.6.32-696.18.7.el6.x86_64
Steps to Reproduce
Existing pipeline within a pipeline group (e.g. group name example)
Select to clone pipeline. In popup box provide a new pipeline name, and specify the same group name, but different casing, e.g. Example)
The pipeline is cloned, and a new group is also created
Try editing the new pipeline material (Or any other material on any pipeline) and save. Save will fail with the message Group with name 'example' already exists
Duplicated pipeline group can be removed to resolve the issue.
It seems like perhaps pipeline groups are case insensitive in some contexts, but in others are case sensitive
The text was updated successfully, but these errors were encountered:
* Perform case-insensitive pipeline group name equals check.
* When a user specifies a pipeline group name, while creating
a new pipeline and the same group name with different case
already exists, do not create a new group. Create the new
pipeline in the existing pipeline group.
* Perform case-insensitive pipeline group name equals check.
* When a user specifies a pipeline group name, while creating
a new pipeline and the same group name with different case
already exists, do not create a new group. Create the new
pipeline in the existing pipeline group.
Issue Type
Summary
Material modifications on pipelines error with
Group with name 'delivery_engineering' already exists
Environment
Basic environment details
20.1.0
13.0.1
Linux 2.6.32-696.18.7.el6.x86_64
Steps to Reproduce
example
)Example
)Group with name 'example' already exists
Duplicated pipeline group can be removed to resolve the issue.
It seems like perhaps pipeline groups are case insensitive in some contexts, but in others are case sensitive
The text was updated successfully, but these errors were encountered: