Production Deploy#3604
Merged
Merged
Conversation
…ks-py313-compat ci: bump pre-commit/pre-commit-hooks to v5.0.0 for Python 3.13 compat
…4-rbio-diagnostics
…3572-05-relocate-format-batch
…ejia/3572-06-app-shell-callers
…/3572-07-infrastructure-callers
…mejia/3572-08-ci-workflow
…foundation rbio: add @requires decorator + mtime-gated common sdist rebuild
…local-dev rbio: add compose:* + new dev:* + test:all (local dev surface)
…cloud rbio: add deploy:* ops:* install:* (cloud surface)
…diagnostics rbio: add debug:* diagnostics (env, deps, venv)
…ate-format-batch relocate format_batch_with_env.sh into infrastructure/
…hell-callers api: migrate serve scripts to rbio build + refinebio_default network
…structure-callers infra/deploy.sh: drop scripts/common.sh source, inline its consumers
…rkflow ci: switch deploy to rbio commands, inline branch resolution, rename CI_* -> DEPLOY_*
rbio migration cleanup
…ntu-22 upgrade base ubuntu 22 + common sdist output file name fix
…a-compendia Move compendia off of nvidia cuda image and onto base
…ation feature/rbio scripts migration
…mpendia-timeout fix list compendia timeout
django upgrade prep
avrohomgottlieb
approved these changes
Jul 2, 2026
migrage drf-yasg OpenAPI2-> drf-spectacular OpenAPI3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces significant improvements and refactoring to the deployment pipeline, especially around environment variable management, Docker image building, and deployment orchestration. The main goals are to standardize environment variable names, remove legacy scripts, and modernize the build and deploy process for better reliability and maintainability.
The most important changes are:
Deployment Pipeline Refactoring:
.github/scripts/remote_deploy.shand.github/workflows/config.yml, replacingCI_TAGandCI_USERNAMEwithDEPLOY_TAGandDEPLOY_USERthroughout the workflow. This ensures consistent and clear naming for deployment metadata. [1] [2] [3] [4] [5] [6]DEPLOY_ENV,DOCKERHUB_REPO, andBATCH_USE_ON_DEMAND_INSTANCES) directly from theBRANCHvariable, simplifying and centralizing environment configuration.Docker Build and Verification:
./bin/rbio build --push deploy, and added explicit verification that all images exist on Dockerhub before proceeding with deployment. This addresses previous issues where Docker could exit successfully even if pushes failed.Terraform and Legacy Script Removal:
.github/scripts/run_terraform.shscript, migrating infrastructure deployment to the new./bin/rbio deploy:upcommand. This streamlines and modernizes infrastructure management. [1] [2]Workflow Improvements:
bin/rbio dev:upto use the newbin/rbio compose:upcommand, reflecting the current recommended approach for service orchestration. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Miscellaneous:
pre-commit-hooksversion in.pre-commit-config.yamlfromv2.4.0tov5.0.0to use the latest linting and formatting hooks.These changes collectively modernize the deployment pipeline, improve reliability, and make the process more transparent and maintainable for future development.