Compare commits
21 commits
main
...
feature/wo
Author | SHA1 | Date | |
---|---|---|---|
Ludger Sicking | 3ac50c55fa | ||
Ludger Sicking | 9019059d92 | ||
Ludger Sicking | 800e634320 | ||
Ludger Sicking | 4d2f3d8e56 | ||
Ludger Sicking | c0c5a4831f | ||
Ludger Sicking | 10214911ea | ||
Ludger Sicking | 02aa52669d | ||
Ludger Sicking | f26ebc403f | ||
Ludger Sicking | 2d5c46e1e1 | ||
Ludger Sicking | 853453d50d | ||
Ludger Sicking | 1971dc653f | ||
Ludger Sicking | cbd7dbfd00 | ||
Ludger Sicking | ea06eea8e8 | ||
Ludger Sicking | ad3bff50a2 | ||
Ludger Sicking | 428620a98a | ||
Ludger Sicking | 90bd000227 | ||
Ludger Sicking | d3450bc2ea | ||
Ludger Sicking | b4860d3942 | ||
Ludger Sicking | 23e1ae21d4 | ||
Ludger Sicking | ba3ddb5d22 | ||
Ludger Sicking | 9914006e57 |
6
.forgejo/workflows/demo.yaml
Normal file
6
.forgejo/workflows/demo.yaml
Normal file
|
@ -0,0 +1,6 @@
|
|||
on: [push]
|
||||
jobs:
|
||||
test:
|
||||
runs-on: docker
|
||||
steps:
|
||||
- run: echo All God (ein kleiner Scherz ;-)
|
12
.woodpecker/ist-image-erreichbar.yaml
Normal file
12
.woodpecker/ist-image-erreichbar.yaml
Normal file
|
@ -0,0 +1,12 @@
|
|||
when:
|
||||
- event: push
|
||||
branch: [no-real-branch, feature/working-*]
|
||||
#https://woodpecker-ci.org/docs/usage/workflow-syntax#when---conditional-execution
|
||||
|
||||
steps:
|
||||
- name: wie-weit-komme-ich-im-image_resp_plugin
|
||||
image: codeberg.org/xfix/plugin-codeberg-pages-deploy:1
|
||||
settings:
|
||||
folder: Blog
|
||||
ssh_key:
|
||||
from_secret: clioption
|
25
.woodpecker/woodpecker-workflow-adavanced-test.yaml
Normal file
25
.woodpecker/woodpecker-workflow-adavanced-test.yaml
Normal file
|
@ -0,0 +1,25 @@
|
|||
when:
|
||||
- event: push
|
||||
branch: [no-real-branch, feature/working-*]
|
||||
#https://woodpecker-ci.org/docs/usage/workflow-syntax#when---conditional-execution
|
||||
|
||||
steps:
|
||||
- name: wir-testen-die-umgebung
|
||||
image: debian
|
||||
commands:
|
||||
- ls ~
|
||||
- pwd
|
||||
- ls -la /
|
||||
- touch /was-duerfen-wir
|
||||
- who
|
||||
- uname -a
|
||||
- id
|
||||
- groups
|
||||
#- sudo last ## im alpine image gegenchecken, was dort verfügbar
|
||||
#- sudo ls /var
|
||||
- last
|
||||
## secrets existieren nur in images / "plugin"s / build-steps
|
||||
- name: image-test
|
||||
image: codeberg.org/xfix/plugin-codeberg-pages-deploy
|
||||
commands:
|
||||
- docker images
|
20
.woodpecker/woodpecker-workflow-test.yaml
Normal file
20
.woodpecker/woodpecker-workflow-test.yaml
Normal file
|
@ -0,0 +1,20 @@
|
|||
# https://woodpecker-ci.org/docs/usage/intro
|
||||
when:
|
||||
- event: push
|
||||
branch: feature/working-forgejo-actions
|
||||
#gehen wildcards fuer branch filtering?
|
||||
|
||||
steps:
|
||||
- name: build
|
||||
#image: debian # alpine // docker pull docker.io/library/alpine
|
||||
image: ubuntu:22.04
|
||||
commands:
|
||||
- echo "This is the build step"
|
||||
#wie kann man Bash Shebang nutzen?
|
||||
- echo "echo Woodoo Woodoopecker" > executable
|
||||
#chmod u+x executable
|
||||
- name: a-test-step
|
||||
image: alpine #golang:1.16
|
||||
commands:
|
||||
- echo "Testing ..."
|
||||
- /bin/sh ./executable
|
25
Technisches/actions-einrichten.md
Normal file
25
Technisches/actions-einrichten.md
Normal file
|
@ -0,0 +1,25 @@
|
|||
# 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
|
Loading…
Reference in a new issue