Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Независимый от версии EDT поиск jar-файлов для Coverage41C #60

Conversation

ovcharenko-di
Copy link

@ovcharenko-di ovcharenko-di commented Nov 27, 2024

Сделал так, что вместо использования ARG в базовом образе (EDT) выполняется поиск каталога с jar-файлами, на этот каталог формируется симлинк.

На втором стейдже файлы копируются из каталога, на который ведет симлинк.

closes #59

Summary by CodeRabbit

  • Chores
    • Updated the Dockerfile for improved management of JAR files.
    • Removed the EDT_PLUGINS argument and implemented a symbolic link for better directory referencing.

Copy link

coderabbitai bot commented Nov 27, 2024

Walkthrough

The pull request modifies the Dockerfile for coverage41C by removing the EDT_PLUGINS argument and adding a command to create a symbolic link to the directory containing JAR files. The COPY command is updated to source JAR files from the newly created symbolic link directory instead of the removed variable. These changes address the issue of locating JAR files in the updated EDT version.

Changes

File Change Summary
coverage41C/Dockerfile Removed ARG EDT_PLUGINS; added symbolic link creation command; updated COPY command to use new link.

Assessment against linked issues

Objective Addressed Explanation
Make JAR file search independent of EDT version (#59)
Ensure correct assembly of coverage41C image with EDT version 2024+ (#59)

Possibly related PRs

🐰 In the land of code where rabbits play,
A Dockerfile changed, come what may.
No more EDT woes, just links that shine,
JARs found with ease, everything's fine!
Hops of joy for a build that's bright,
Coverage41C is now just right! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 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

@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

🧹 Outside diff range and nitpick comments (1)
coverage41C/Dockerfile (1)

Line range hint 1-24: Add documentation for the jar file discovery mechanism

The solution effectively addresses the EDT version independence requirement. Consider adding a comment block explaining:

  • The purpose of the jar file discovery mechanism
  • Which EDT versions are supported
  • How the symbolic link strategy works
 ARG DOCKER_REGISTRY_URL=library
+# The following implementation discovers debug jar files dynamically,
+# making it compatible with EDT 2024+ and earlier versions.
+# It works by:
+# 1. Finding the directory containing debug jar files in the EDT installation
+# 2. Creating a symbolic link to this directory
+# 3. Copying required files from the linked directory in the second stage
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c78c41e and 27f06a3.

📒 Files selected for processing (1)
  • coverage41C/Dockerfile (1 hunks)


COPY --from=base ${EDT_PLUGINS}/com._1c.g5.v8.dt.debug.core_*.jar ${EDT_PLUGINS}/com._1c.g5.v8.dt.debug.model_*.jar /opt/1C/1CE/
COPY --from=base /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.core_*.jar /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.model_*.jar /opt/1C/1CE/
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Verify successful file copy operation

The COPY command should be followed by a verification step to ensure the required files are present.

 COPY --from=base /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.core_*.jar /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.model_*.jar /opt/1C/1CE/
+RUN if [ $(ls /opt/1C/1CE/com._1c.g5.v8.dt.debug.*.jar 2>/dev/null | wc -l) -ne 2 ]; then \
+        echo "Error: Failed to copy required jar files" && \
+        exit 1; \
+    fi
📝 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
COPY --from=base /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.core_*.jar /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.model_*.jar /opt/1C/1CE/
COPY --from=base /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.core_*.jar /opt/1C/edt_plugins/com._1c.g5.v8.dt.debug.model_*.jar /opt/1C/1CE/
RUN if [ $(ls /opt/1C/1CE/com._1c.g5.v8.dt.debug.*.jar 2>/dev/null | wc -l) -ne 2 ]; then \
echo "Error: Failed to copy required jar files" && \
exit 1; \
fi

Comment on lines +9 to +10
RUN ln -s $(find /opt/1C -name "com._1c.g5.v8.dt.debug.*.jar" -printf '%h\n'| sort -u) /opt/1C/edt_plugins

Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add error handling to the symbolic link creation

The current implementation might fail silently in edge cases. Consider making it more robust:

-RUN ln -s $(find /opt/1C -name "com._1c.g5.v8.dt.debug.*.jar" -printf '%h\n'| sort -u) /opt/1C/edt_plugins
+RUN PLUGIN_DIR=$(find /opt/1C -name "com._1c.g5.v8.dt.debug.*.jar" -printf '%h\n' | sort -u) && \
+    if [ $(echo "$PLUGIN_DIR" | wc -l) -ne 1 ]; then \
+        echo "Error: Expected exactly one plugin directory, found:" && \
+        echo "$PLUGIN_DIR" && \
+        exit 1; \
+    fi && \
+    if [ ! -f "$PLUGIN_DIR/com._1c.g5.v8.dt.debug.core_"*.jar ] || \
+       [ ! -f "$PLUGIN_DIR/com._1c.g5.v8.dt.debug.model_"*.jar ]; then \
+        echo "Error: Required jar files not found in $PLUGIN_DIR" && \
+        exit 1; \
+    fi && \
+    rm -f /opt/1C/edt_plugins && \
+    ln -s "$PLUGIN_DIR" /opt/1C/edt_plugins
📝 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
RUN ln -s $(find /opt/1C -name "com._1c.g5.v8.dt.debug.*.jar" -printf '%h\n'| sort -u) /opt/1C/edt_plugins
RUN PLUGIN_DIR=$(find /opt/1C -name "com._1c.g5.v8.dt.debug.*.jar" -printf '%h\n' | sort -u) && \
if [ $(echo "$PLUGIN_DIR" | wc -l) -ne 1 ]; then \
echo "Error: Expected exactly one plugin directory, found:" && \
echo "$PLUGIN_DIR" && \
exit 1; \
fi && \
if [ ! -f "$PLUGIN_DIR/com._1c.g5.v8.dt.debug.core_"*.jar ] || \
[ ! -f "$PLUGIN_DIR/com._1c.g5.v8.dt.debug.model_"*.jar ]; then \
echo "Error: Required jar files not found in $PLUGIN_DIR" && \
exit 1; \
fi && \
rm -f /opt/1C/edt_plugins && \
ln -s "$PLUGIN_DIR" /opt/1C/edt_plugins

@nixel2007
Copy link
Member

А скрипты не надо обновить?

@nixel2007 nixel2007 merged commit fee08b4 into firstBitMarksistskaya:feature/first-bit Nov 27, 2024
11 checks passed
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.

Некорректно собирается образ coverage41C с EDT версии 2024+
2 participants