Steps with the same name
Opened this issue · 1 comments
zc-devs commented
Component
other
Describe the bug
Trying to use steps with the same name, pipeline fails or works wrong.
be aware that steps now can have the same name
Steps to reproduce 1
- Make pipeline
skip_clone: true
steps:
notification:
depends_on:
- build
image: alpine
commands:
- echo 'Alright'
build:
image: alpine
commands:
- echo 'Build'
build:
image: alpine
commands:
- echo 'Test'
package:
image: alpine
commands:
- echo 'Package'
⬆️ pipeline with one build
step works well.
server-same-name-map.log
agent-same-name-map.log
Steps to reproduce 2
- Make pipeline
skip_clone: true
steps:
- name: notification
depends_on:
- build
image: alpine
commands:
- echo 'Alright'
- name: build
image: alpine
commands:
- echo 'Build'
- name: build
image: alpine
commands:
- echo 'Test'
- name: package
image: alpine
commands:
- echo 'Package'
server-same-name-array.log
agent-same-name-array.log
Expected behavior
- pipeline fails with error like
step names must be unique
- or pipeline runs both steps with the same name (
build
)
System Info
Woodpecker `next-75017ac7ca`, Gitea `1.22.3`, Postgres `16`, Kubernetes `v1.30.6+k3s1`
Additional context
#3411 (comment)
#3411 (comment)
Validations
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Checked that the bug isn't fixed in the
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
zc-devs commented