CI: Disable server unit test in TBD

[yatinappsmith]

Description

Disable server unit test in TBD
Fixes #Issue Number

Automation

/ok-to-test tags=""

Communication

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

• Yes
• [ X ] No

Summary by CodeRabbit

• Chores
  • Streamlined our automated build and test workflows by simplifying test dependencies.
  • Enhanced the release process efficiency by removing an outdated testing step from our continuous integration pipeline.

[coderabbitai]

Walkthrough

This pull request modifies the CI workflow defined in the GitHub Actions YAML file. The changes remove the execution of the server-unit-tests job by commenting it out and update the dependencies in the ci-test-result and package-master jobs to no longer require the results from server tests. This streamlines the CI path to focus solely on the ci-test and client-unit-tests jobs.

Changes

File	Change Summary
.github/workflows/.../test-build-docker-image.yml	- Commented out the server-unit-tests job (its name, conditions, parameters). - Removed server-unit-tests dependency from ci-test-result and package-master jobs.

Sequence Diagram(s)

Old Workflow

sequenceDiagram
    participant B as Build Docker Image
    participant ST as Server Unit Tests
    participant CT as Client Unit Tests
    participant CI as CI Test
    participant TR as CI Test Result
    participant PM as Package Master

    B->>ST: Trigger server unit tests
    CI->>TR: Provide CI test results (including server tests)
    CT->>TR: Provide client unit test results
    ST->>TR: Send server test results
    TR->>PM: Package build using all test results

Loading

Updated Workflow

sequenceDiagram
    participant B as Build Docker Image
    participant CT as Client Unit Tests
    participant CI as CI Test
    participant TR as CI Test Result
    participant PM as Package Master

    B->>CI: Build triggers CI test
    CI->>TR: Provide CI test results
    CT->>TR: Provide client unit test results
    TR->>PM: Package build using CI & client test results

Loading

Suggested labels

skip-changelog, CI

Suggested reviewers

• sharat87
• sagar-qa007
• abhvsn
• ApekshaBhosale

Poem

In our CI realm, a subtle change takes flight,
Server tests now rest in quiet night.
Dependencies trimmed for a smoother run,
New flow ignites like a rising sun.
Code sings its song in harmonious array –
A tweak, a triumph, brightening our day!
🚀✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 62fb0e2 and 6eb8ba1.

📒 Files selected for processing (1)

• .github/workflows/test-build-docker-image.yml (5 hunks)

✅ Files skipped from review due to trivial changes (1)

• .github/workflows/test-build-docker-image.yml

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 generate docstrings to generate docstrings for 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.

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.

[btsgh]

Server unit tests have been commented out to unblock TBD.. LGTM