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

Simpler deploy of patch releases #371

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

alexander-veit
Copy link
Member

I think it would be helpful, if the release of patches was simpler.

I suggest that the AWSF image defaults to the minor version of the deployed Tibanna. E.g. if Tibanna version 2.1.1 is deployed, the default AWSF image is 2.1.0. The advantage would be that patch releases only require a redeploy of Tibanna but not a new docker image. If the docker image required changes, it should be a minor release anyway.

@@ -21,5 +21,6 @@ jobs:
- name: Docs
env:
DOCS_TOKEN: ${{ secrets.DOCS_TOKEN }}
TIBANNA_VERSION: 2.2.0
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs-deploy GA does not work anymore. I think that's because it can't determine the version, since it is now parsed from pyproject.toml. One solution would be to set the env variable here. Not elegant at all, but I am not sure how to get it otherwise.
I had the same issue with the Lambda function and solved it there via env variables.

@@ -21,3 +22,7 @@ def _get_project_meta():
# they can't parse the pyproject.toml. For all other use cases, fall back to the pyproject.toml version
__version__ = os.environ.get('TIBANNA_VERSION', False) or str(pkg_meta['version'])

# AWSF image version - will default to the minor version of the deployed Tibanna
tibanna_version = semantic_version.Version(__version__)
__awsf_image_version__ = str(semantic_version.Version(major=tibanna_version.major, minor=tibanna_version.minor, patch=0))
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would import __awsf_image_version__ into tibanna_ff as we do with __version__ to bring that change to CGAP.

Copy link
Member

@willronchetti willronchetti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would make a note about this in the deployment documentation - namely that updates to the awsf image must always update the minor version in light of this change.

@@ -21,5 +21,6 @@ jobs:
- name: Docs
env:
DOCS_TOKEN: ${{ secrets.DOCS_TOKEN }}
TIBANNA_VERSION: 2.2.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This version won't matter for the docs build though right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the version matters. It is also used in the conf.py in the docs folder.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants