Skip to content

docs: dev-docsL QubesOS-packages-sync.md: add#59

Open
DaniilKl wants to merge 1 commit intomasterfrom
add-qubes-cicds
Open

docs: dev-docsL QubesOS-packages-sync.md: add#59
DaniilKl wants to merge 1 commit intomasterfrom
add-qubes-cicds

Conversation

@DaniilKl
Copy link
Copy Markdown

For more information check the TrenchBoot/trenchboot-issues#83 .


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:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Comment on lines +96 to +97
pkg_wf --> gh_artifacts : uploads RPM artifacts
trigger_wf --> woodpecker_ci : HTTP trigger\n(woodpecker-trigger.sh)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
wp_s3 --> ftp_server : deploys signed RPMs\n+ updates repo metadata
wp_s3 ..> ftp_server : deploys signed RPMs\n+ updates repo metadata

Comment on lines +111 to +112
| A --> B | Sequential job dependency (needs:) |
| A ..> B | Cross-repo workflow call / API call |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't render and --> looks more like rendered ..>. Maybe:

Suggested change
| 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.

Image

@@ -0,0 +1,108 @@
@startuml
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same issues as in grub diagram

@@ -0,0 +1,119 @@
@startuml Automatic rebase CI/CD Workflows for QubesOS packages - TrenchBoot/xen
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)


![grub-diagram](../img/cicd-diagram-grub.png)

## TrenchBoot/xen
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Comment on lines +71 to +72

wp_s1 --> wp_s2
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
wp_s1 --> wp_s2
wp_pipeline --> wp_s1 : needs
wp_s1 --> wp_s2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants