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.

Sign up for GitHub

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

Jump to bottom

Move to deploy-on-release #281

Open
3 tasks
surchs opened this issue Sep 18, 2024 · 0 comments
Open
3 tasks

Move to deploy-on-release #281

surchs opened this issue Sep 18, 2024 · 0 comments
Labels
flag:schedule Flag issue that should go on the roadmap or backlog. maint:process Improvement to internal processes type:maintenance Upkeeping efforts & catch-up corrective improvements that are not Features nor Bugs

Comments

@surchs
Copy link
Contributor

surchs commented Sep 18, 2024

Like we learned with the annotation tool (neurobagel/annotation_tool#790): deploying to prod from every main merge is risky. Let's not do that anymore.

Instead

  • Change our deployment process to only run on a release
  • Find a way to have a running "nightly" version with a persistent name (i.e. not the staging previews, but maybe netlify works)
  • Setup / carry over the auto-release workflow from other projects
@surchs surchs added type:maintenance Upkeeping efforts & catch-up corrective improvements that are not Features nor Bugs maint:process Improvement to internal processes flag:schedule Flag issue that should go on the roadmap or backlog. labels Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flag:schedule Flag issue that should go on the roadmap or backlog. maint:process Improvement to internal processes type:maintenance Upkeeping efforts & catch-up corrective improvements that are not Features nor Bugs
Projects
Neurobagel
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@surchs