mirrors/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2024-06-16 04:10:44 +00:00
Code Issues Projects Releases Wiki Activity
woodpecker/docs/docs/20-usage/71-project-settings.md
Anbraten 289f0c9ad6
Change pipeline config path resolution (#299) 
# Config resolution
- pipeline-config setting empty / not specified (default): `.woodpecker/` => `.woodpecker.yml` => `.drone.yml`
- pipeline-config setting defined by user: try that file / folder and no fallback (if a user sets some special value that is normally done for some reason)

# Changes
- pipeline-config setting will be empty by default
- remove fallback setting for config loading (simplifies config)

---
closes #133

---

* adjust config fetching mechanism

* default path empty

* remove fallback flag from ui and db
2021-09-17 21:40:43 +02:00

1.8 KiB
Raw Blame History

Project settings

As the owner of a project in Woodpecker you can change some project related settings via the Webinterface.

project settings

Pipeline path

The path to the pipeline config file or folder. By default it is left empty which will use the following configuration resolution .woodpecker/*.yml -> .woodpecker.yml -> .drone.yml. If you set a custom path Woodpecker tries to load your configuration or fails if no configuration could be found at the specified location. To use a multi pipeline you have to change it to a folder path ending with a / like .woodpecker/.

Repository hooks

Your Version-Control-System will notify Woodpecker about some events via webhooks. If you want your pipeline to only run on specific webhooks, you can check them by this setting.

Project settings

Protected

Every build initiated by a user (not including the project owner) needs to be approved by the owner before being executed. This can be used if your repository is public to protect the pipeline configuration from running unauthorized changes on third-party pull requests.

Trusted

If you set your project to trusted, a pipeline step and by this the underlying containers gets access to escalated capabilities like mounting volumes.

Project visibility

You can change the visibility of your project by this setting. If a user has access to a project he can see all builds and their logs and artifacts. Settings, Secrets and Registries can only be accessed by owners.

  • Public Every user can see your project without being logged in.
  • Private Only authenticated users of the Woodpecker instance can see this project.
  • Internal Only you and other owners of the repository can see this project.

Timeout

After this timeout a pipeline has to finish or will be treated as timed out.