Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use same home page branch for utoronto prod hub too #3600

Merged
merged 1 commit into from
Jan 9, 2024

Conversation

yuvipanda
Copy link
Member

Everything should use the utoronto branch now, as set in the common config file

Ref #2729

Everything should use the `utoronto` branch now, as set
in the common config file

Ref 2i2c-org#2729
@yuvipanda yuvipanda requested a review from a team as a code owner January 9, 2024 22:12
@yuvipanda
Copy link
Member Author

Self merging so users don't see the homepage on jupyter.utoronto.ca

@yuvipanda yuvipanda merged commit 954b015 into 2i2c-org:master Jan 9, 2024
4 of 6 checks passed
Copy link

github-actions bot commented Jan 9, 2024

🎉🎉🎉🎉

Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/7467494694

Copy link

github-actions bot commented Jan 9, 2024

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider Cluster Name Upgrade Support? Reason for Support Redeploy Upgrade Staging? Reason for Staging Redeploy
kubeconfig utoronto No Yes Following prod hubs require redeploy: prod

Production deployments

Cloud Provider Cluster Name Hub Name Reason for Redeploy
kubeconfig utoronto prod Following helm chart values files were modified: default-prod.values.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done 🎉
Development

Successfully merging this pull request may close these issues.

1 participant