Skip to content

Minor fix for s390x CI runner#1886

Merged
Dead2 merged 1 commit intodevelopfrom
s390x-ci-fix
Mar 18, 2025
Merged

Minor fix for s390x CI runner#1886
Dead2 merged 1 commit intodevelopfrom
s390x-ci-fix

Conversation

@Dead2
Copy link
Copy Markdown
Member

@Dead2 Dead2 commented Mar 17, 2025

Instead of selecting the most recent tag when downloading the actions runner, select the highest version number.

Summary by CodeRabbit

  • Chores
    • Refined the version selection process in the deployment workflow to ensure that only properly formatted, semantic version tags are used for version checkout.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 17, 2025

Walkthrough

This pull request updates the command in the Dockerfile for the self-hosted GitHub Actions runner. The Dockerfile now uses a command that filters Git tags to only include those following a semantic versioning pattern, sorts them, and selects the most recent tag. This change replaces the previous approach that relied on git describe and ensures that only valid semantic version tags are considered.

Changes

File(s) Change Summary
arch/s390/self-hosted-builder/actions-runner.Dockerfile Updated the Git command for checking out the latest tag. The new command filters tags using a regex to match semantic versions (vX.X.X), sorts them, and selects the newest one.

Possibly related PRs

  • s390x: Update CI clang version #1858: Adjusts the same Dockerfile to install a custom version of the Clang compiler, indicating a code-level modification to the Dockerfile that relates to the changes in this PR.

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)
  • We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
    - To enable this feature, set early_access to true under in the settings.

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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
arch/s390/self-hosted-builder/actions-runner.Dockerfile (1)

17-17: Refine the Git tag selection in the checkout command.
The updated command correctly filters out semantic version tags and selects the highest version using version sort and tail -1. A couple of suggestions:

  • Consider using grep -E with a simplified regex (e.g., grep -E "^v[0-9]+\.[0-9]+\.[0-9]+$") to enhance readability and portability.
  • Think about adding a fallback or error handling in case no matching tag is found, which would help diagnose issues in environments where tags do not conform to the expected format.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5f1c730 and d7860af.

📒 Files selected for processing (1)
  • arch/s390/self-hosted-builder/actions-runner.Dockerfile (1 hunks)

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.52%. Comparing base (5f1c730) to head (d7860af).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1886      +/-   ##
===========================================
+ Coverage    82.51%   82.52%   +0.01%     
===========================================
  Files          141      141              
  Lines        12672    12672              
  Branches      2909     2909              
===========================================
+ Hits         10456    10458       +2     
  Misses        1243     1243              
+ Partials       973      971       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Dead2 Dead2 merged commit fd0d263 into develop Mar 18, 2025
294 of 296 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Jul 4, 2025
@Dead2 Dead2 mentioned this pull request Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant