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

Add fixed stable version of controller #21

Merged
merged 3 commits into from
Feb 15, 2023
Merged

Conversation

markusweigelt
Copy link
Collaborator

Fixes #11

Copy link
Member

@bertsky bertsky left a comment

Choose a reason for hiding this comment

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

Great stuff. So we can manually trigger the action by editing STABLE_VERSION (getting a new latest and stable) or automatically by any other change (getting a new latest, because the other is cached). Right?

with:
context: .
push: true
tags: ${{ env.REGISTRY_PATH }}/ocrd_controller:stable
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps we can even add some release tag here:

Suggested change
tags: ${{ env.REGISTRY_PATH }}/ocrd_controller:stable
tags: ${{ env.REGISTRY_PATH }}/ocrd_controller:stable,${{ env.REGISTRY_PATH }}/ocrd_controller:${{ env.vcs_tag }}

(Will be just HEAD if there is no tag for it.)

Copy link
Collaborator Author

@markusweigelt markusweigelt Feb 14, 2023

Choose a reason for hiding this comment

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

The question was whether saving the tags will cause problems on GitHub. I assumed that the stable tag simply overrides the stable image version.

Copy link
Member

@bertsky bertsky Feb 14, 2023

Choose a reason for hiding this comment

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

I assumed that the stable tag simply overrides the stable image version.

I'm sure it does. This is just to make sure we also produce some persistent images ourselves from time to time (viz. whenever we decide to make a release).

Copy link
Member

Choose a reason for hiding this comment

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

Why didn't you commit my suggestions?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

oh I thought I had already done that. Was not intentional. I'll change that directly.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Added your suggest changes with seperate pr #22

@markusweigelt
Copy link
Collaborator Author

Great stuff. So we can manually trigger the action by editing STABLE_VERSION (getting a new latest and stable) or automatically by any other change (getting a new latest, because the other is cached). Right?

Atm the stable version rebuilds with same behaviour like the latest version but with the different of using the parent version. So when something in Controller repo is changed than the stable version rebuilds too.

@markusweigelt markusweigelt merged commit 58d6a67 into master Feb 15, 2023
@markusweigelt markusweigelt deleted the fix-ocrd-all-version branch February 15, 2023 08:16
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.

Fix ocrd/all version
2 participants