DevFW-CICD/website-and-documentation
23
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

added seqeuence diagram
Some checks failed
Hugo Site Tests / test (push) Failing after 1s
Details
ci / build (push) Successful in 53s
Details

Browse source
This commit is contained in:
Manuel Ganter 2025-12-03 11:54:26 +01:00
parent c345d3b3b5
commit 92a1f4c1c5
No known key found for this signature in database
5 changed files with 70 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

23
content/en/docs/components/forgejo/actions/runner-orchestration.md
View file

@ -102,30 +102,9 @@ sequenceDiagram
```
### Sequence Diagrams
[Add sequence diagrams showing key interaction flows with other components]
The diagram below shows how a trigger of an action results in deployment of a runner on edge-connect.
```mermaid
sequenceDiagram
rect rgb(255,200,200)
Forgejo->>GARM: (Webhook) A new job is pending
GARM->>GARM Provider Edge Connect: Create new runner
GARM Provider Edge Connect->>Edge Connect: Create App
GARM Provider Edge Connect->>Edge Connect: Create AppInstance
Edge Connect->>Runner: Deploys
end
Runner->>GARM: Retrieve runner registration token
GARM->>Forgejo: Retrieve runner registration token
Forgejo-->>GARM: Token
GARM-->>Runner: Token
Runner->>Forgejo: Register runner
Runner->>Forgejo: Fetch job
Runner->>Runner: Work on job
Runner->>Forgejo: Send result
```
{{<likec4-view view="forgejoGarmInteraction" browser="false" dynamic-variant="sequence" project="architecture" title="Interaction between Forgejo, Garm and Edge Connect">}}
### Deployment Architecture