woodpecker: Triger Manuall Pipeline errors out

Component

server, agent, web-ui

Describe the bug

I’m using docker swarm with the latest tag for the woodpecker-server image, and the latest-alpine tag for the woodpecker-agent image. using a .woodpecker file does seem to allow woodpecker to notice it as a workflow. The exact stack file I’m using worked roughly 2.5 weeks ago. Upon running the pipeline, nothing happens, and checking the dev console gives the message Missing required param "pipelineId" The containers for both the server and agent print no logs when this happens.

Steps to reproduce

  1. Create a Docker Swarm stack using the provided stack file.
  2. Set it up to access a bitbucket workspace
  3. add a .woodpecker folder with some manual workflows to a repo
  4. run a pipeline on that repo on whichever branch you added the .woodpecker folder
  5. check the dev console for Missing required param "pipelineId" error

Expected behavior

Successfully find workflows and execute them

System Info

{"source":"https://github.com/woodpecker-ci/woodpecker","version":"2.7.3"}

Here's the stack file:

services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest
    ports:
      - 8001:8000
    volumes:
      - woodpecker-server-data:/var/lib/woodpecker/
    env_file: woodpecker.env
    networks:
      - wpkr
    deploy:
      placement:
        constraints: [node.role == manager]
      replicas: 1
      update_config:
        parallelism: 2
        delay: 10s
      restart_policy:
        condition: on-failure
  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:latest-alpine
    command: agent
    depends_on:
      - woodpecker-server
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - woodpecker-agent-config:/etc/woodpecker
    env_file: woodpecker.env
    networks:
      - wpkr
    deploy:
      placement:
        constraints: [node.role == manager]
      replicas: 1
      update_config:
        parallelism: 2
        delay: 10s
      restart_policy:
        condition: any
volumes:
  woodpecker-server-data:
    driver: "local"
  woodpecker-agent-config:
    driver: "local"
networks:
  wpkr:
    external: true
    attachable: true

Additional context

No response

Validations

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 20 (9 by maintainers)

Most upvoted comments

@6543 changing the javascript log to something like ‘No workflows found for branch xyz’ would be helpful. Also, from a UI standpoint, nothing happens at all when this occurs, and the user has to open their browser consol to see that something has gone wrong.

nevermind…

This turned out to be a configuration issue on my end. I had all my pipelines listening for the wrong branch. However, more logging would have been useful for fixing this.

@6543 please read my comments. I was able to reproduce this on ci.woodpecker-ci.org, but not locally.

Interesting, I can reproduce this on ci.woodpecker-ci.org, but not in my local setup. Maybe @anbraten or @6543 can you check the logs? Just try to trigger a manual pipeline - that didn’t work for me.