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

Fix canary build of the server image #3174

Merged
merged 2 commits into from
Jul 9, 2024

Conversation

kichristensen
Copy link
Contributor

What does this change

Building and publishing the server image during a canary build, did not use the canary tag, instead it used the version of the build, e.g., v1.1.0-7-gd0387ecb. It also means that on each canary build a new tag is used when publishing the image.

By checking if we are doing a release of a tagged version or a canary build we can use the correct tag.

Checklist

  • Did you write tests?
  • Did you write documentation?
  • Did you change porter.yaml or a storage document record? Update the corresponding schema file.
  • If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Building and publishing the server image during a canary build, did not
use the canary tag, instead it used the version of the build, e.g.,
v1.1.0-7-gd0387ecb. It also means that on each canary build a new tag
is used when publishing the image.

By checking if we are doing a release of a tagged version or a canary
build we can use the correct tag.

Signed-off-by: Kim Christensen <[email protected]>
@schristoff schristoff merged commit 91ae5c3 into getporter:main Jul 9, 2024
34 of 35 checks passed
@kichristensen kichristensen deleted the canaryBuildServerImage branch August 25, 2024 20:07
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