chore: Reverted server cache skip changes

[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

• New Features

  • Enhanced workflow for building, testing, and packaging the Java server codebase with improved conditional logic.
  • Added new input parameters for better customization during workflow execution.

• Bug Fixes

  • Refined steps for checking out code and identifying changed files, improving accuracy in test execution.

• Documentation

  • Updated descriptions for new input parameters to clarify their usage and default values.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces updates to the GitHub Actions workflow for the Java server codebase. Key modifications include the addition of input parameters for pr, skip-tests, branch, and is-pg-build. The workflow now conditionally executes steps based on changes detected in the app/server directory and the specified input parameters. Improvements in caching for Maven dependencies and the PostgreSQL setup process are also included, enhancing the overall clarity and efficiency of the build and testing process.

Changes

File Path	Change Summary
.github/workflows/server-build.yml	Updated workflow to include inputs for pr, skip-tests, branch, and is-pg-build. Refined steps for checking out code and identifying changes in the app/server directory. Enhanced conditional logic for running tests and caching Maven dependencies. Adjusted PostgreSQL setup handling based on is-pg-build input. Restructured steps for clarity and efficiency.

Possibly related PRs

• chore: Added pg branch #36086: This PR adds the is-pg-build input parameter to the workflow, which is directly related to the changes made in the main PR that also introduced this parameter in the server build workflow.
• CI : fix build cache #37712: This PR modifies the server build workflow to include the is-pg-build parameter, aligning with the changes in the main PR that enhance the handling of PostgreSQL builds.
• chore: skipping file change #37774: This PR involves changes to the client build workflow that may affect the overall build process, which is relevant to the main PR's focus on enhancing the server build workflow.

Suggested labels

Task, Stability Pod, Stability Issue

Suggested reviewers

• sharat87
• yatinappsmith
• rishabhrathod01

🎉 In the land of code where workflows thrive,
New inputs and logic help the build come alive!
With PostgreSQL checks and caching so bright,
The server's now ready, all set for the flight!
So let’s cheer for the changes, both clever and neat,
A smoother process, oh what a treat! 🚀

---

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