Skip to content

[ci] Split build artefacts - #1010

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
split-artefacts
May 29, 2025
Merged

[ci] Split build artefacts#1010
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
split-artefacts

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented May 29, 2025

Copy link
Copy Markdown
Member

Signed-off-by: Andrei Kvapil kvapss@gmail.com

Summary by CodeRabbit

  • Chores
    • Improved workflow for pull requests by separating artifact uploads and downloads, resulting in clearer and more organized handling of installer and image files during build and test processes.

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@coderabbitai

coderabbitai Bot commented May 29, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The workflow configuration was updated to split artifact handling into two parts: the installer and the Talos image are now uploaded and downloaded as separate artifacts with distinct names and paths. The test job was adjusted to download these artifacts individually, and code checkout was removed from the test job.

Changes

File(s) Change Summary
.github/workflows/pull-requests.yaml Split artifact upload into two steps (installer and Talos image), updated artifact names/paths, removed code checkout from test job, adjusted download steps accordingly.

Sequence Diagram(s)

sequenceDiagram
    participant BuildJob
    participant ArtifactStore
    participant TestJob

    BuildJob->>ArtifactStore: Upload "cozystack-installer"
    BuildJob->>ArtifactStore: Upload "talos-image"
    TestJob->>ArtifactStore: Download "cozystack-installer"
    TestJob->>ArtifactStore: Download "talos-image"
Loading

Possibly related PRs

Suggested labels

ok-to-test

Suggested reviewers

  • lllamnyp
  • klinch0

Poem

Two artifacts now take their place,
Installer and image, each in their space.
No more bundles, no more mess,
The workflow’s cleaner—what progress!
With hops and leaps, our CI flows,
Like a rabbit, swift as it goes! 🐇


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@kvaps
Andrei Kvapil (kvaps) merged commit e0c3d23 into main May 29, 2025
@kvaps
Andrei Kvapil (kvaps) deleted the split-artefacts branch May 29, 2025 22:53

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 1

🧹 Nitpick comments (2)
.github/workflows/pull-requests.yaml (2)

42-42: Remove trailing whitespace.

Line 42 has unnecessary trailing spaces which can lead to lint errors.
Apply this diff to remove them:

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 42-42: trailing spaces

(trailing-spaces)


49-53: Approve splitting Talos image upload into its own artifact.

Separating the Talos image (nocloud-amd64.raw.xz) into its own artifact (talos-image) aligns with the PR objective of decoupling build outputs.

Note: line 54 also contains trailing whitespace (see static analysis). Consider removing it:

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6130f43 and cb303d6.

📒 Files selected for processing (1)
  • .github/workflows/pull-requests.yaml (2 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/pull-requests.yaml

[error] 42-42: trailing spaces

(trailing-spaces)


[error] 54-54: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test
🔇 Additional comments (3)
.github/workflows/pull-requests.yaml (3)

43-48: Approve splitting installer upload into its own artifact.

The new Upload installer step correctly isolates the installer file (cozystack-installer.yaml) as a separate build artifact, improving clarity and downstream handling.


65-69: Approve downloading the installer artifact.

The Download installer step correctly retrieves the cozystack-installer artifact into _out/assets/, matching the upload path.


72-76: Approve downloading the Talos image artifact.

The Download Talos image step mirrors the upload configuration and ensures the image is available for testing.

Comment on lines 64 to +65
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Download installer

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.

⚠️ Potential issue

Missing checkout in test job: tests won’t run without source.

The test job no longer checks out the repository, so make test will not find any code. Insert a checkout step before downloading artifacts. For example:

 jobs:
   test:
     steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          fetch-tags: true
       - name: Download installer
         uses: actions/download-artifact@v4
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Download installer
jobs:
test:
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0
fetch-tags: true
- name: Download installer
uses: actions/download-artifact@v4
🤖 Prompt for AI Agents
In .github/workflows/pull-requests.yaml around lines 64 to 65, the test job is
missing a checkout step, so the source code is not available for running tests.
Add a step to checkout the repository before the "Download installer" step to
ensure the code is present for the test commands.

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.

1 participant