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 image build on main branch #179

Merged
merged 2 commits into from
May 24, 2023
Merged

fix image build on main branch #179

merged 2 commits into from
May 24, 2023

Conversation

eguzki
Copy link
Contributor

@eguzki eguzki commented May 19, 2023

The main docker image tag has not been built for a while. Same for image builds with git sha tags from the main branch.

@eguzki eguzki requested a review from a team May 19, 2023 09:42
@alexsnaps
Copy link
Member

I actually had removed that… Cause I probably misunderstood the intent...
main is the equivalent of latest, always, right? So why do we need the two tags? Why can't we just use latest (ormain actually, I don't mind really - tho latest conveys more than main). Why do we need both...?

@@ -24,7 +24,7 @@ jobs:
if: ${{ github.ref_name == env.MAIN_BRANCH_NAME }}
id: add-latest-tag
run: |
echo "IMG_TAGS=latest" >> $GITHUB_ENV
echo "IMG_TAGS=${{ env.IMG_TAGS }} latest" >> $GITHUB_ENV
Copy link
Contributor

Choose a reason for hiding this comment

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

I've seen that missing and thought it was intentional. Sorry.

@eguzki
Copy link
Contributor Author

eguzki commented May 22, 2023

The actual intention was to generate the tag with the git sha, which is being used in the smoke test. I agree that main branch is the same as latest, hence useless. Question: do we want git sha tag to be generated of al lthe mainbranch commits?? I thought is was wanted for continuous testing (bundles passed to QE reference images with git sha tag).

@alexsnaps
Copy link
Member

do we want git sha tag to be generated of al lthe mainbranch commits?? I thought is was wanted for continuous testing (bundles passed to QE reference images with git sha tag).

I think we want to, yes… I'm just pondering the utility of main and latest… And if they are redundant, I'm arguing to keep the latter, i.e. latest. I think having the sha was the intent, but @didierofrivia or @pehala might correct me…

@eguzki
Copy link
Contributor Author

eguzki commented May 23, 2023

ok, let me change a bit to have only latest and the git sha for the main branch

@eguzki eguzki requested review from guicassolato and a team May 23, 2023 12:31
@@ -24,7 +24,7 @@ jobs:
if: ${{ github.ref_name == env.MAIN_BRANCH_NAME }}
id: add-latest-tag
run: |
echo "IMG_TAGS=latest" >> $GITHUB_ENV
echo "IMG_TAGS=${{ env.IMG_TAGS }} latest" >> $GITHUB_ENV
Copy link
Member

Choose a reason for hiding this comment

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

can we have this just be: github.sha for this step, where ref_name is main?

Copy link
Member

Choose a reason for hiding this comment

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

ugh nevermind that comment, I somehow never submitted this 🤔

@eguzki eguzki merged commit ec920a6 into main May 24, 2023
@eguzki eguzki deleted the fix-image-build branch May 24, 2023 15:15
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.

3 participants