Skip to content

fix(log-collector): properly extracts image version for ci build#1717

Merged
ygrishajev merged 1 commit intomainfrom
feature/log-collector
Jul 22, 2025
Merged

fix(log-collector): properly extracts image version for ci build#1717
ygrishajev merged 1 commit intomainfrom
feature/log-collector

Conversation

@ygrishajev
Copy link
Contributor

@ygrishajev ygrishajev commented Jul 22, 2025

Summary by CodeRabbit

  • Chores
    • Improved Docker image tagging in the release workflow for more consistent versioning.

@ygrishajev ygrishajev requested a review from a team as a code owner July 22, 2025 10:40
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 22, 2025

Walkthrough

The GitHub Actions workflow for releasing the log-collector Docker image was updated to refine the image tagging process. Instead of using the full git tag as the Docker image tag, the workflow now extracts a simplified version string to use as the tag, removing any prefix and leading 'v' character.

Changes

File(s) Change Summary
.github/workflows/log-collector-release.yml Modified Docker image tagging logic to extract and sanitize version string from git tag output

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Git
    participant Docker

    GitHub Actions->>Git: Get git tag
    Git->>GitHub Actions: Return full git tag
    GitHub Actions->>GitHub Actions: Extract version (remove prefix and 'v')
    GitHub Actions->>Docker: Build image with sanitized version tag
    GitHub Actions->>Docker: Push image with sanitized version tag
Loading

Estimated code review effort

1 (~2 minutes)

Possibly related PRs

Suggested reviewers

  • baktun14

Poem

A tag with a v, or a slash in its way,
Now trimmed and neat for Docker display.
Our log-collector sails with a version so clean,
In the registry, it’s crisp and pristine!
🐇✨


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.

@ygrishajev ygrishajev force-pushed the feature/log-collector branch from f8d9e4c to faaac09 Compare July 22, 2025 10:44
Copy link
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: 2

🧹 Nitpick comments (1)
.github/workflows/log-collector-release.yml (1)

42-43: Consider docker buildx build --push for multi-arch images and fewer steps.

Using Buildx with --push pushes the manifest and layers atomically and enables --platform for multi-architecture support, which is increasingly expected for GitHub-hosted images.

-docker build -f apps/log-collector/Dockerfile -t "$image" .
-docker push "$image"
+docker buildx build \
+  --file apps/log-collector/Dockerfile \
+  --tag "$image" \
+  --push \
+  --platform linux/amd64,linux/arm64 .

This is optional but future-proofs the release pipeline.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between df359c6 and faaac09.

📒 Files selected for processing (1)
  • .github/workflows/log-collector-release.yml (1 hunks)

@ygrishajev ygrishajev merged commit d904409 into main Jul 22, 2025
64 checks passed
@ygrishajev ygrishajev deleted the feature/log-collector branch July 22, 2025 10:54
@anilmurty anilmurty added this to the Log Forwarding milestone Jul 28, 2025
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.

3 participants

Comments