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

feat: add environment suffix to github artifact #140

Conversation

tkloht
Copy link
Contributor

@tkloht tkloht commented Sep 14, 2023

currently we're only using the tree_hash as name of our artifact, but tree_hash is the same across all environments. So we're overwriting existing artifacts and only have a single one for production in the end.
After this change we should have an artifact per environment.

I'm hopeful that this will also fix the errors we're seeing since introducing the product-dev environment, my assumption is that github locks the artifact for a short time during upload and when the stars align product-dev and staging upload at the same time, creating this error.

to my best knowledge we're not using these artifacts programatically & we only upload the artifact for reference, so this should be safe to rename.

Screenshot 2023-09-14 at 13 15 22

@tkloht tkloht requested review from macko911 and jogilvyt September 14, 2023 11:20
@linear
Copy link

linear bot commented Sep 14, 2023

@tkloht tkloht changed the title add environment suffix to github artifact feat: add environment suffix to github artifact Sep 14, 2023
Copy link
Contributor

@macko911 macko911 left a comment

Choose a reason for hiding this comment

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

Lovely, well I sure hope we don't use the same artifact for staging/production.. 😅

@tkloht
Copy link
Contributor Author

tkloht commented Sep 14, 2023

sure hope we don't use the same artifact for staging/production

just for reference, we definitely don't use the github artifact for upload to s3 - that happens here

- name: Copy Static Files

i'm not aware of anything else we use it for

currently we're only using the tree_hash as name of our artifact, but tree_hash is the same across all environments. So we're overwriting existing artifacts and only have a single one for production in the end.
After this change we should have an artifact per environment.
I'm hopeful that this will also fix the errors we're seeing since introducing the product-dev environment, my assumption is that github locks the artifact for a short time during upload and when the stars align product-dev and staging upload at the same time, creating this error.
@tkloht tkloht force-pushed the feature/web-667-investigate-github-upload-issues-that-are-causing-deployment branch from ec67123 to 1aee4ef Compare September 14, 2023 11:27
Copy link

@jogilvyt jogilvyt left a comment

Choose a reason for hiding this comment

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

🤞 Thanks for looking into this, hope this solves the issue!

@tkloht tkloht merged commit 7f0680d into main Sep 14, 2023
@github-actions github-actions bot mentioned this pull request Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants