Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

woodpecker cli parse matrix fail #3673

Closed
3 tasks done
micash545 opened this issue May 2, 2024 · 2 comments
Closed
3 tasks done

woodpecker cli parse matrix fail #3673

micash545 opened this issue May 2, 2024 · 2 comments
Labels
bug Something isn't working cli feedback this needs feedback

Comments

@micash545
Copy link
Contributor

Component

cli

Describe the bug

Woodpecker cli throws parse matrix when its not defined:

❯ ./woodpecker-cli exec ./test.yaml
12:50PM FTL error running cli error="parse matrix fail"
❯ cat --plain ./test.yaml
when:
  - branch: *

steps:
  build:
    image: localregistry/nodejs:latest
    pull: true
    commands:
      - pnpm i --frozen-lockfile
      - pnpm build
  deploy:
    image: localregistry/actions/rsync:latest
    pull: true
    directory: ./build
    settings:
      port:
        from_secret: ssh_port
      privatekey:
        from_secret: ssh_key
      host_key:
        from_secret: ssh_host_key
      src: .
      dest:
        from_secret: ssh_host
    when:
      event: push

System Info

woodpecker-cli version 2.4.1

Additional context

No response

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]
@micash545 micash545 added the bug Something isn't working label May 2, 2024
@qwerty287 qwerty287 added the cli label May 2, 2024
@qwerty287
Copy link
Contributor

I cannot reproduce this on current next with your config - can you try with the next version?
I had to change line 2 however: from - branch: * to - branch: "*", but then it worked as expected.

@qwerty287 qwerty287 added the feedback this needs feedback label May 3, 2024
@qwerty287
Copy link
Contributor

Closing as no response

@qwerty287 qwerty287 closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cli feedback this needs feedback
Projects
None yet
Development

No branches or pull requests

2 participants