Fix timeout interval: App Engine Deployment and add App start timeout in staging

[BenjaminSsempala]

Summary of Changes (What does this PR do?)

• Fix timeout interval: App Engine Deployment.
• Add App start timeout in staging to mimic production runtime

Status of maturity (all need to be checked before merging):

• I've tested this locally
• I consider this code done
• This change ready to hit production in its current state
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included issue number in the "Closes #ISSUE-NUMBER" part of the "What are the relevant tickets?" section to link the issue.
• I've updated corresponding documentation for the changes in this PR.
• I have written unit and/or e2e tests for my change(s).

How should this be manually tested?

• Please include the steps to be done inorder to setup and test this PR.

What are the relevant tickets?

• Closes #
• Jira_card_number (If exists)

Screenshots (optional)

Summary by CodeRabbit

• Deployment Configuration
  • Updated readiness check settings for website2 in production and staging environments
  • Reduced check interval to 5 seconds
  • Decreased timeout to 4 seconds
  • Added failure and success thresholds
  • Set app start timeout to 30 minutes

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The pull request modifies deployment workflow configurations for website2 in both production and staging environments. The primary changes involve adjusting readiness check parameters in the app.yaml configuration, specifically reducing the check_interval_sec and timeout_sec values in production, while introducing a new readiness_check section in staging. These modifications aim to enhance the deployment process by refining the conditions under which the application is deemed ready to serve traffic.

Changes

File	Change Summary
.github/workflows/deploy-frontends-to-production.yml	Reduced check_interval_sec from 10 to 5 seconds and timeout_sec from 15 to 4 seconds for website2 readiness check.
.github/workflows/deploy-frontends-to-staging.yml	Added new readiness_check configuration with parameters: check_interval_sec: 5, timeout_sec: 4, failure_threshold: 2, success_threshold: 2, app_start_timeout_sec: 1800 for website2.

Possibly related PRs

• Adding Readiness checks and upscaling instances to handle Website deployments #2415: This PR adds a readiness_check section to the app.yaml configuration for website2, which directly relates to the changes made in the main PR regarding the readiness check parameters.

Suggested reviewers

• Psalmz777
• Baalmart

Poem

🚀 Deployment dance, configs so light
Readiness checks now swift and tight
Seconds trimmed with surgical care
Workflows singing without a scare
Efficiency blooms, deployment takes flight! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fdd718f and e676444.

📒 Files selected for processing (2)

• .github/workflows/deploy-frontends-to-production.yml (1 hunks)
• .github/workflows/deploy-frontends-to-staging.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 or @coderabbitai title anywhere in the PR title to generate the title automatically.

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