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

Update version based on commit hash #51

Closed
blrnw3 opened this issue Sep 9, 2021 · 3 comments
Closed

Update version based on commit hash #51

blrnw3 opened this issue Sep 9, 2021 · 3 comments
Labels
backend core backend (rest api, web, engine) P3 Priority 3 - Do we need P3? tech Tech issues that do not require product prioritization. Tech debt, tooling, ops, etc.

Comments

@blrnw3
Copy link
Contributor

blrnw3 commented Sep 9, 2021

instead of having the version hard coded (and updated when we do a new release) it would be great to have the version based on the current commit hash. Currently if you click the i button on the explorer it displays version but it would be really helpful if it showed the deployed version.

Version is hardcoded in server/init.py

@metakuni
Copy link
Contributor

metakuni commented Oct 1, 2021

It would be extra nice if we could retrieve the deployed commit hash by hitting an endpoint similar to Portal's /deployed_version:

This would make it easier to verify deployments, especially while on-call.

@metakuni
Copy link
Contributor

metakuni commented Oct 6, 2021

It might be good to include the commit hash from single-cell-infra as well. (e.g. for a quick way to check for config changes like https://github.com/chanzuckerberg/single-cell-infra/pull/442/files)

@maniarathi maniarathi added the P1 Priority 1 - Improvement with wide impact, fix within 1 week label Dec 13, 2021
@atolopko-czi atolopko-czi added P3 Priority 3 - Do we need P3? tech Tech issues that do not require product prioritization. Tech debt, tooling, ops, etc. and removed P1 Priority 1 - Improvement with wide impact, fix within 1 week labels Dec 8, 2022
@metakuni metakuni added the backend core backend (rest api, web, engine) label Feb 7, 2023
@atolopko-czi
Copy link
Contributor

dup of newer issue #582

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend core backend (rest api, web, engine) P3 Priority 3 - Do we need P3? tech Tech issues that do not require product prioritization. Tech debt, tooling, ops, etc.
Projects
None yet
Development

No branches or pull requests

4 participants