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

Update server-build.yml #37702

Open
wants to merge 1 commit into
base: release
Choose a base branch
from
Open

Update server-build.yml #37702

wants to merge 1 commit into from

Conversation

yatinappsmith
Copy link
Contributor

@yatinappsmith yatinappsmith commented Nov 26, 2024

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags="@tag.All"

🔍 Cypress test results

Warning

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12026463021
Commit: c1bfa6b
Cypress dashboard.
Tags: @tag.All
Spec:
It seems like no tests ran 😔. We are not able to recognize it, please check workflow here.


Tue, 26 Nov 2024 10:23:49 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Chores
    • Enhanced the build and testing workflow for the Java server codebase.
    • Introduced a new job step for improved interactive capabilities.
    • Updated the checkout process and refined conditions for executing steps related to test results and caching.

Copy link
Contributor

coderabbitai bot commented Nov 26, 2024

Walkthrough

The pull request modifies the GitHub Actions workflow file .github/workflows/server-build.yml, focusing on the build and testing processes for a Java server codebase. Key changes include the addition of a new job step for setting up an upterm session, commenting out the previous artifact extraction step, and updating the checkout action. The conditions for executing various steps have been refined, particularly regarding test results and caching strategies, while preserving the overall structure for managing PostgreSQL builds and caching artifacts.

Changes

File Path Change Summary
.github/workflows/server-build.yml - Added job step for setting up an upterm session using lhotari/action-upterm@v1.
- Commented out the step for extracting server build artifacts from a tar file.
- Updated to use actions/checkout@v2.
- Refined conditions for executing steps, particularly for test results and caching Maven dependencies, while retaining overall structure for PostgreSQL builds.

Possibly related PRs

Suggested labels

skip-changelog, CI

Suggested reviewers

  • sharat87
  • abhvsn
  • pratapaprasanna

🌟 In the land of code where workflows play,
A new upterm session brightens the day.
With artifacts tucked away in a tar,
The build process shines like a bright, shining star.
Caching and testing, all in a row,
Our Java server is ready to go! 🚀


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.

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.

@yatinappsmith yatinappsmith added the ok-to-test Required label for CI label Nov 26, 2024
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

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8cb0bee and c1bfa6b.

📒 Files selected for processing (1)
  • .github/workflows/server-build.yml (1 hunks)
🧰 Additional context used
🪛 actionlint (1.7.4)
.github/workflows/server-build.yml

349-349: the runner of "actions/checkout@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 yamllint (1.35.1)
.github/workflows/server-build.yml

[error] 348-348: trailing spaces

(trailing-spaces)

🔇 Additional comments (1)
.github/workflows/server-build.yml (1)

347-348: ⚠️ Potential issue

Verify the removal of tar extraction step

The commented tar extraction step might break the cache restoration process. Please ensure that the server.jar artifact is properly handled without this step.

🧰 Tools
🪛 yamllint (1.35.1)

[error] 348-348: trailing spaces

(trailing-spaces)

tar -xzvf ./server.jar
# tar -xzvf ./server.jar

- uses: actions/checkout@v2
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Update actions/checkout to v4

The checkout action version v2 is outdated. Other steps in this workflow are using v4, which includes important security updates and performance improvements.

-      - uses: actions/checkout@v2
+      - uses: actions/checkout@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
- uses: actions/checkout@v2
- uses: actions/checkout@v4
🧰 Tools
🪛 actionlint (1.7.4)

349-349: the runner of "actions/checkout@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

Comment on lines +350 to +351
- name: Setup upterm session
uses: lhotari/action-upterm@v1
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Restrict upterm session access

Adding unrestricted upterm session access to the workflow runner poses a security risk. Consider:

  1. Adding conditions to limit when the session is created (e.g., only on workflow failure)
  2. Restricting access to specific users or teams
       - name: Setup upterm session
+        if: failure()
         uses: lhotari/action-upterm@v1
+        with:
+          limit-access-to: appsmithorg/server-team
📝 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
- name: Setup upterm session
uses: lhotari/action-upterm@v1
- name: Setup upterm session
if: failure()
uses: lhotari/action-upterm@v1
with:
limit-access-to: appsmithorg/server-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ok-to-test Required label for CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant