Compare commits

...

21 commits

Author SHA1 Message Date
Ludger Sicking 3ac50c55fa image auf codeberg ist erreichbar und nun?
Some checks failed
ci/woodpecker/push/ist-image-erreichbar Pipeline failed
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
2024-09-09 15:06:29 +02:00
Ludger Sicking 9019059d92 image auf codeberg vermutlich nicht erreichbar
Some checks failed
ci/woodpecker/push/ist-image-erreichbar Pipeline failed
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
2024-09-09 15:02:43 +02:00
Ludger Sicking 800e634320 registry erreichbar? 2024-09-09 14:58:34 +02:00
Ludger Sicking 4d2f3d8e56 vereinfachen: secrets nur in "plugin"s!!!!
Some checks failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline failed
2024-09-09 08:54:56 +02:00
Ludger Sicking c0c5a4831f vereinfachen: wo ist secret abgreifbar? auch im image? 2024-09-09 08:41:35 +02:00
Ludger Sicking 10214911ea vereinfachen: richtige syntax? 2024-09-09 08:29:44 +02:00
Ludger Sicking 02aa52669d vereinfachen: zwei synatx-e parallel WIDRSPRCH
All checks were successful
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline was successful
2024-09-09 08:28:10 +02:00
Ludger Sicking f26ebc403f vereinfachen: definierte secrets durchreichen 2024-09-09 08:26:05 +02:00
Ludger Sicking 2d5c46e1e1 vereinfachen: einfaches secret geht nicht! 2024-09-09 08:17:06 +02:00
Ludger Sicking 853453d50d vereinfachen: wie funktioniert simples secret?
All checks were successful
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline was successful
2024-09-09 08:07:47 +02:00
Ludger Sicking 1971dc653f vereinfachen: sudo nicht verfügbar
All checks were successful
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline was successful
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
2024-09-09 08:05:30 +02:00
Ludger Sicking cbd7dbfd00 vereinfachen: debian statt alpine
Some checks failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline failed
2024-09-09 08:04:12 +02:00
Ludger Sicking ea06eea8e8 vereinfachen: last schlägt fehl
Some checks failed
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
2024-09-09 08:02:32 +02:00
Ludger Sicking ad3bff50a2 vereinfachen: simples ls
Some checks failed
ci/woodpecker/push/woodpecker-workflow-adavanced-test Pipeline failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
2024-09-09 08:00:19 +02:00
Ludger Sicking 428620a98a Komplexität reduzieren
versuche simples Secret als TestCommand
2024-09-04 20:07:52 +02:00
Ludger Sicking 90bd000227 zweiter "Actions" Versuch 2024-09-04 20:00:37 +02:00
Ludger Sicking d3450bc2ea Ui... Alpine hat wohl keine Bash.
All checks were successful
ci/woodpecker/push/woodpecker-workflow-test Pipeline was successful
2024-09-02 15:52:42 +02:00
Ludger Sicking b4860d3942 in der Tat "cat" und "echo" verhalten sich unterschiedlich ;-)
Some checks failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline failed
2024-09-02 15:51:17 +02:00
Ludger Sicking 23e1ae21d4 so funktionieren multiple lines anscheinend nicht :-(
Some checks failed
ci/woodpecker/push/woodpecker-workflow-test Pipeline failed
2024-09-02 15:46:53 +02:00
Ludger Sicking ba3ddb5d22 Syntax nun richtig? 2024-09-02 15:44:35 +02:00
Ludger Sicking 9914006e57 erster "Actions" Versuch 2024-09-02 15:38:51 +02:00
5 changed files with 88 additions and 0 deletions

View file

@ -0,0 +1,6 @@
on: [push]
jobs:
test:
runs-on: docker
steps:
- run: echo All God (ein kleiner Scherz ;-)

View 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

View 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

View 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

View 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