CI: Changing cron timing - Update test-build-docker-image.yml

[btsgh]

Changed TBP to run at different times, and added a new one

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
  • Updated GitHub Actions workflow schedule to run at different times on weekdays
  • Modified cron expression to adjust workflow execution timing

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request modifies the GitHub Actions workflow configuration file .github/workflows/test-build-docker-image.yml. The primary change involves adjusting the scheduled execution times for the workflow. The cron expression has been updated to run at different times during weekdays, shifting from 7:00 AM, 1:00 PM, and 7:00 PM IST to 7:00 AM, 11:00 AM, and 3:00 PM IST. The modification is purely related to the workflow scheduling timing.

Changes

File	Change Summary
.github/workflows/test-build-docker-image.yml	Updated cron schedule expression from "30 1-12/6 * * 1-5" to "30 1-11/4 * * 1-5", modifying workflow execution times

Possibly related PRs

• ci: Do not fail on image remove #38660: Modifies build-docker-image workflow
• ci: return true if command fails #38662: Updates input parameter description in build-docker-image workflow
• chore: Added pg branch #36086: Modifies GitHub Actions workflow files

Suggested labels

skip-changelog, CI

Suggested reviewers

• sharat87
• yatinappsmith

Poem

🕰️ Cron schedules dance and sway,
Workflows pirouette through the day,
Bits and bytes in rhythmic flight,
Automation's elegant might!
CI/CD's gentle refrain 🤖

---

📜 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 eb8e0e3 and 1b71720.

📒 Files selected for processing (1)

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

---

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. (Beta)
• @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.