Trusted option is missing for the repository

[rajasekhar-gundala]

Component

server, web-ui

Describe the bug

The "Trusted" option is missing under Project settings for the repository. I can see only "Allow Pull Requests" and "Protected".

System Info

I am using Caddy Server in front of Woodpecker and Gitea.

Docker Compose

version: "3.7"

services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:latest
    volumes:
      - /localvolume:/var/lib/woodpecker/
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=https://woodpecker.example.com
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_CLIENT=client id
      - WOODPECKER_GITEA_SECRET=secret
      - WOODPECKER_GITEA_URL=https://gitea.example.com
      - WOODPECKER_AGENT_SECRET=agent secret
    networks:
      - caddy
    ports:
      - "8000:8000"
    deploy:
      placement:
        constraints: [node.role == worker]
      replicas: 1
      update_config:
        parallelism: 2
        delay: 10s
      restart_policy:
        condition: on-failure

  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:latest
    command: agent
    depends_on:
      - woodpecker-server
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WOODPECKER_SERVER=woodpecker-server:9000
      - WOODPECKER_AGENT_SECRET=agent secret
      - WOODPECKER_MAX_PROCS=10
    networks:
      - caddy
    deploy:
      placement:
        constraints: [node.role == worker]
      replicas: 1
      update_config:
        parallelism: 2
        delay: 10s
      restart_policy:
        condition: on-failure
volumes:
  localvolume:
    driver: "local"
networks:
  caddy:
    external: true

Caddyfile

{
    email you@example.com
    cert_issuer acme
    # Production acme directory
    acme_ca https://acme-v02.api.letsencrypt.org/directory
    # Staging acme directory
    #acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
    servers {
        protocol {
            experimental_http3
            allow_h2c
            strict_sni_host
        }
        max_header_size 16384
    }
}

woodpecker.example.com {
    root * /var/lib/woodpecker
    encode gzip zstd
    reverse_proxy woodpecker-server:8000
}

Additional context

No response

Validations

• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Check that this is a concrete bug. For Q&A join our Discord Chat Server.

[wxiaoguang]

You should set a user as admin in woodpecker server.

https://woodpecker-ci.org/docs/administration/server-config#administrators

Only admin can set the trusted repo.

Indeed, I believe it's a UI or document problem, most people do not know this trick (it is not obvious and can not be found easliy, no guide on UI)

[anbraten]

I will try to add some hints to the docs at the places it describes the trusted option (https://woodpecker-ci.org/docs/usage/project-settings#trusted).

@rajaseg Where did you found the trusted option? Was it at the place I linked above?

[wxiaoguang]

Also maybe there are some logs about trusted concept? IIRC if I use the volumes in a non-trusted repo, some error logs are printed

[rajasekhar-gundala]

You should set a user as admin in woodpecker server.

https://woodpecker-ci.org/docs/administration/server-config#administrators

Only admin can set the trusted repo.

Indeed, I believe it's a UI or document problem, most people do not know this trick (it is not obvious and can not be found easliy, no guide on UI)

@wxiaoguang Thank you very much for the tip. I added the environment variable - WOODPECKER_ADMIN=admin to the docker-compose and re-deployed the stack. Now I can see the option "Trusted" under the Project settings of the repository.

[rajasekhar-gundala]

I will try to add some hints to the docs at the places it describes the trusted option (https://woodpecker-ci.org/docs/usage/project-settings#trusted).

@rajaseg Where did you found the trusted option? Was it at the place I linked above?

@anbraten Yes, that's the link where we need to hint users how to enable it.

[6543]

we could "grey out" it as "disabled" so it's visible ... and show a hint on mouse over that only admins can use this option ?

[rajasekhar-gundala]

I am trying to build and publish Docker image using Dockerfile. I have a repository in Gitea. I am getting a "The step has been cancelled" error for the clone step. Please find the screenshot below.

Here is my pipeline

pipeline:
  publish:
    image: plugins/docker
    group: docker
    secrets: [ docker_username, docker_password ]
    settings:
      repo: dockerregistry/reponame
      dockerfile: Dockerfile
      tag: latest
    when:
      branch: master
      event: push

Am I missing or doing anything wrong?

[anbraten]

we could "grey out" it as "disabled" so it's visible ... and show a hint on mouse over that only admins can use this option ?

I think we should keep things simple and add the hint to the docs as that was the place this question initially came from. Normally a user would not notice that something is missing at all, if he is not reading the docs before.