chore:Removed no of batch and vulnerability shipper

[rnithinpaladin]

Description

Removed number of batch and vulnerability shipper

Problem

Solution

Fixes # (issue if any)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Chore (no code changes)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also
list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• My commit message/PR follows the contribution guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Other Information:

List any documentation updates that are needed for the Wiki

Summary by CodeRabbit

• Refactor
  • Improved job scheduling mechanism by removing the unused noOfBatches field, streamlining the schedulePluginShipperJobs method for better performance and maintainability.

[coderabbitai]

Walkthrough

In the JobScheduler.java file, the noOfBatches field was removed, and the schedulePluginShipperJobs method was modified to reflect changes in the scheduling logic. This update simplifies the class by removing unnecessary fields and potentially improves the efficiency of job scheduling.

Changes

File Path	Change Summary
jobs/job-scheduler/src/main/java/.../JobScheduler.java	Removed noOfBatches field and updated schedulePluginShipperJobs method for scheduling logic.

Poem

In the land of code where schedules reign,
A field called noOfBatches faced its bane.
With logic refined and cleaner slate,
Jobs now ship at a faster rate.
🐇✨ Hopping through the code with glee,
The scheduler's now as light as can be!

Warning

Review ran into problems

Problems (1)

• Git: Failed to clone repository. Please contact CodeRabbit support.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3ef999c and 4f2dddc.

Files selected for processing (1)

• jobs/job-scheduler/src/main/java/com/paladincloud/jobscheduler/service/JobScheduler.java (2 hunks)

Additional comments not posted (1)

jobs/job-scheduler/src/main/java/com/paladincloud/jobscheduler/service/JobScheduler.java (1)

237-237: The method schedulePluginShipperJobs appears to have been modified to adjust the scheduling logic. Ensure that the removal of the vulnerability shipper and other changes do not affect dependent systems or scheduled tasks negatively.

#!/bin/bash
# Description: Verify that the removal of the vulnerability shipper does not affect other systems.
# Test: Search for any references to `schedulePluginShipperJobs` in other parts of the codebase.
rg --type java 'schedulePluginShipperJobs'

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[rnithinpaladin]

Pr merged in release