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

[IA-4821] Add branch name to leo release tag #4185

Closed
wants to merge 1 commit into from

Conversation

LizBaldo
Copy link
Collaborator

@LizBaldo LizBaldo commented Feb 6, 2024

Jira ticket: https://broadworkbench.atlassian.net/browse/IA-4821

Summary of changes

What

Appends the build branch to the image release tag to make it more easily searchable on GCR

Why

The move from jenkins to GHA removed the ability to tag the docker image with multiple tags, including the branch name that was very useful for developers when updating their BEEs. The leonardo build GHA unfortunately only takes in one tag as an input so we could do:

  • This PR that simply appends the name of the branch to the version (pending the syntax is correct)
  • Modify the leonardo build GHA to add another tag to the docker image using the build branch name

Testing these changes

What to test

Who tested and where

  • This change is covered by automated tests
    • NB: Rerun automation tests on this PR by commenting jenkins retest or jenkins multi-test.
  • I validated this change
  • Primary reviewer validated this change
  • I validated this change in the dev environment

Copy link

codecov bot commented Feb 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b3e5df7) 71.32% compared to head (25cabf5) 71.37%.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #4185      +/-   ##
===========================================
+ Coverage    71.32%   71.37%   +0.05%     
===========================================
  Files          147      145       -2     
  Lines        13913    13888      -25     
  Branches      1110     1110              
===========================================
- Hits          9923     9913      -10     
+ Misses        3990     3975      -15     
Flag Coverage Δ
pact ?

Flags with carried forward coverage won't be shown. Click here to find out more.

see 3 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3e5df7...25cabf5. Read the comment docs.

@@ -108,7 +108,7 @@ jobs:
inputs: '{
"repository": "${{ github.event.repository.full_name }}",
"ref": "${{ needs.init-github-context.outputs.build-branch }}",
"leonardo-release-tag": "${{ steps.tag.outputs.tag }}"
"leonardo-release-tag": "${{ steps.tag.outputs.tag }}-${{ needs.init-github-context.outputs.build-branch }}"
Copy link
Collaborator

Choose a reason for hiding this comment

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

me, personally, I would not add the branch name to the leonardo-release-tag. it looks like that version is going to find its way into helm charts and a bunch of other downstream systems (not sure if that is intended).

the branch name is also in the "ref" input above.
I would modify the leonardo-build.yaml with the a tag for ${{ inputs.ref }}

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yep, this is the consensus from Devops as well. I will work on it when I have some focus time this week :)

@LizBaldo LizBaldo closed this Feb 6, 2024
@LizBaldo
Copy link
Collaborator Author

LizBaldo commented Feb 6, 2024

Closing this as we don't need to use the docker tag anymore when updating the leonardo app version on a BEE

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