26 lines
1.4 KiB
Markdown
26 lines
1.4 KiB
Markdown
# Actions unter [Woodpecker](https://woody.git.rpi-virtuell.de/) einrichten
|
|
|
|
## workflows, runner, ...
|
|
|
|
- [Forgejo Actions user guide](https://forgejo.org/docs/next/user/actions/)
|
|
- Actions aktivieren (pro Repo)
|
|
- Settings => Repo Units => Overview => "Enable integrated CI... with.. Actions"
|
|
- in .forgejo/workflows YAML Dateien, die Action "definieren" - ähnlich [GitHub Actions](https://docs.github.com/en/actions)
|
|
- .forgejo/workflows/demo.yaml
|
|
- wo/wie/was ist der "runner"???
|
|
|
|
- Workflow in Woodpecker
|
|
- [Getting Started](https://woodpecker-ci.org/docs/usage/intro)
|
|
- "enable" Repo
|
|
- Workflow als YAML in Verzeichnis .woodpecker
|
|
- Bsp.: .woodpecker/woodpecker-workflow-test.yaml
|
|
|
|
- Vermutung
|
|
- Actions in Woodpecker sind vgl. mit "danger zone" in Forgejo, haben nichts gemein!!!
|
|
- Actions in Forgejo ~~== Workflow in Woodpecker
|
|
- Actions in Forgejo sind Instanzen für "forgejo runner"
|
|
- Woodpecker ist davon unabhängig
|
|
- Actions können deaktiviert werden
|
|
- https://forgejo.org/docs/latest/admin/actions/: "Forgejo Actions provides continuous integration driven from the files found in the .forgejo/workflows directory of a repository. Note that Forgejo does not run the jobs, it relies on the Forgejo runner to do so. It needs to be installed separately."
|
|
- ~~[Forgejo Actions user guide](https://forgejo.org/docs/next/user/actions/)~~ irrelevant
|