Fix deploy preview

[BenjaminSsempala]

Summary of Changes (What does this PR do?)

• Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

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

• Chores
  • Disabled preview and production website deployment features to streamline release workflows and reduce unnecessary deployment overhead.
  • Enhanced version management by integrating an automatic retry mechanism in the cleanup process to address transient issues efficiently.
  • These key improvements ensure consistency and reliability in our release operations, ultimately contributing to a smoother and more responsive end-user experience.

[coderabbitai]

Warning

Rate limit exceeded

@BenjaminSsempala has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between fedbd2a and 0779b68.

📒 Files selected for processing (3)

• .github/workflows/deploy-frontend-pr-previews.yml (3 hunks)
• .github/workflows/deploy-frontends-to-production.yml (1 hunks)
• .github/workflows/deploy-frontends-to-staging.yml (2 hunks)

📝 Walkthrough

Walkthrough

This pull request disables the website deployment functionality by removing or commenting out the website job (and in one case the website-pr-comment job) across multiple GitHub Actions workflow files. In addition, the deletion process in the website2 job has been enhanced with a retry mechanism that introduces an attempt counter and delays between retries. These changes ensure the removal of obsolete deployment steps while improving error handling during old version deletions.

Changes

File(s)	Change Summary
.github/workflows/deploy-frontend-pr-previews.yml .github/workflows/deploy-frontends-to-staging.yml	Removed/commented out the website job (and the website-pr-comment job in the previews file); enhanced the "Delete Old Versions" step in the website2 job with a retry mechanism.
.github/workflows/deploy-frontends-to-production.yml	Removed/commented out the website job, leaving the remaining workflow steps intact.

Sequence Diagram(s)

sequenceDiagram
    participant W as Website2 Job
    participant D as Delete Script
    participant S as Cloud Service
    W->>D: Initiate deletion of old versions
    D->>S: Request deletion
    alt Deletion fails
        S-->>D: Error response
        D->>D: Increment attempt counter & wait
        loop While attempts < max
            D->>S: Retry deletion
            S-->>D: Error/Success response
        end
    else Deletion succeeds
        S-->>D: Success response
    end
    D-->>W: Return deletion status

Loading

Possibly related PRs

• App Engine optimisation: Reducing idle instances for app engine #2390: Addresses adjustments to the website job, including scaling configurations, which directly relate to its removal in this PR.
• Added website2 deployment workflow #2258: Introduces a new website2 job affecting similar deployment workflows, making its context and changes closely related.
• Fix Deployment Website #2503: Modifies error handling and retry logic within the website2 job, aligning with the enhanced deletion mechanism in the current changes.

Suggested reviewers

• Psalmz777
• OchiengPaul442
• Baalmart

Poem

In the realm of workflows bold and bright,
Old jobs retire into the night.
With retries set and logic tuned,
Our pipelines hum a smoother tune.
Code flows like art in pure delight,
Cheers to changes shining light!
🚀✨

---

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.