fix: Commented check step

[sagar-qa007]

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=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

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

• Yes
• No

Summary by CodeRabbit

• Chores
  • Adjusted workflow conditions for executing actions, refining triggers for test runs and caching processes.
  • Commented out the step for checking changes in the server folder, altering how subsequent actions are triggered.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request modifies the .github/workflows/server-build.yml file, primarily altering the conditions under which job steps are executed. The step that checks for changes in the server folder has been commented out, affecting the triggering of actions based on file changes. Additionally, conditions for restoring previous run results, downloading artifacts, and setting up the Java environment have been refined to ensure they only execute under specific circumstances. The workflow retains its overall structure while emphasizing tighter control over the execution of tests and caching mechanisms.

Changes

File	Change Summary
.github/workflows/server-build.yml	Commented out the step checking for changes in the server folder; refined conditions for restoring results, downloading artifacts, and setting up Java; adjusted logic for caching Maven dependencies and executing tests.

Possibly related PRs

• CI: commented files changed step. It is a notification step #35460: This PR comments out a step in a CI workflow related to file changes, similar to the main PR's focus on commenting out the step that checks for changes in the server folder.
• chore: Update for workflow name #37696: This PR updates the name of a workflow, which is a change in the workflow configuration similar to the modifications made in the main PR regarding the handling of job steps and conditions in the workflow file.

Suggested labels

skip-changelog, ok-to-test

Suggested reviewers

• sharat87
• yatinappsmith

In the workflow's dance, changes take flight,
Commented steps, now hidden from sight.
Conditions refined, like a well-tuned song,
Tests run with care, ensuring we belong.
With artifacts waiting, our code will prevail,
In the CI journey, we shall not fail! 🎉

---

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