Conversation
Signed-off-by: Danil Klimuk <[email protected]>
|
|
||
| To provide the QubesOS users not only the packages with TrenchBoot patches but | ||
| the pckages with both TrenchBoot and QubesOS patches a set of automatic rebase | ||
| worklfows has been implemented for the three of the components mentioned above: |
There was a problem hiding this comment.
| worklfows has been implemented for the three of the components mentioned above: | |
| workflows has been implemented for the three of the components mentioned above: |
pre-commit failure
| > component. Hence, there is no need for a rebase CI/CDs for this component. | ||
|
|
||
| To provide the QubesOS users not only the packages with TrenchBoot patches but | ||
| the pckages with both TrenchBoot and QubesOS patches a set of automatic rebase |
There was a problem hiding this comment.
| the pckages with both TrenchBoot and QubesOS patches a set of automatic rebase | |
| the packages with both TrenchBoot and QubesOS patches a set of automatic rebase |
| pkg_wf --> gh_artifacts : uploads RPM artifacts | ||
| trigger_wf --> woodpecker_ci : HTTP trigger\n(woodpecker-trigger.sh) |
There was a problem hiding this comment.
| pkg_wf --> gh_artifacts : uploads RPM artifacts | |
| trigger_wf --> woodpecker_ci : HTTP trigger\n(woodpecker-trigger.sh) | |
| pkg_wf ..> gh_artifacts : uploads RPM artifacts | |
| trigger_wf ..> woodpecker_ci : HTTP trigger\n(woodpecker-trigger.sh) |
I think this is more of an API call (like when fetching patches?)
| ' WOODPECKER PIPELINE → external | ||
| ' ───────────────────────────────────── | ||
| wp_s1 ..> gh_artifacts : downloads RPMs\n(GitHub API) | ||
| wp_s3 --> ftp_server : deploys signed RPMs\n+ updates repo metadata |
There was a problem hiding this comment.
| wp_s3 --> ftp_server : deploys signed RPMs\n+ updates repo metadata | |
| wp_s3 ..> ftp_server : deploys signed RPMs\n+ updates repo metadata |
| | A --> B | Sequential job dependency (needs:) | | ||
| | A ..> B | Cross-repo workflow call / API call | |
There was a problem hiding this comment.
This doesn't render and --> looks more like rendered ..>. Maybe:
| | A --> B | Sequential job dependency (needs:) | | |
| | A ..> B | Cross-repo workflow call / API call | | |
| | A <b>⇾</b> B | Sequential job dependency (needs:) | | |
| | A ⇢ B | Cross-repo workflow call / API call | |
This does render correctly in PlantUML server.
| @@ -0,0 +1,108 @@ | |||
| @startuml | |||
There was a problem hiding this comment.
Same issues as in grub diagram
| @@ -0,0 +1,119 @@ | |||
| @startuml Automatic rebase CI/CD Workflows for QubesOS packages - TrenchBoot/xen | |||
There was a problem hiding this comment.
Same issues as in grub diagram
| 2. [TrenchBoot/xen](https://github.com/TrenchBoot/xen) | ||
| 3. [TrenchBoot/qubes-antievilmaid](https://github.com/TrenchBoot/qubes-antievilmaid) | ||
|
|
||
| ## TrenchBoot/grub |
There was a problem hiding this comment.
I think it would be a good idea to add couple more simple diagrams e.g. with just rebase (how it's done, without details)
|
|
||
|  | ||
|
|
||
| ## TrenchBoot/xen |
There was a problem hiding this comment.
Xen + Grub look near identical (maybe the only differences are details e.g. variables?). Maybe merge it somehow? Or create more high level diagram e.g. with just:
- apply upstream patches
- rebase
- build
- upload
- download
- sign
- publish
|
|
||
| wp_s1 --> wp_s2 |
There was a problem hiding this comment.
| wp_s1 --> wp_s2 | |
| wp_pipeline --> wp_s1 : needs | |
| wp_s1 --> wp_s2 |
For more information check the TrenchBoot/trenchboot-issues#83 .