-
Notifications
You must be signed in to change notification settings - Fork 96
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: fix hash.txt issue from build.yaml #1001
Conversation
86f48f9
to
2375ef1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi :)
Thanks for working on it
Just making sure we're on the same page - the preview uses s3 storage, so the fact the commit sha is available on https://s3.amazonaws.com/noam-gaash.co.il/12659976140/open-bus/268/hash.txt doesn't guarantee it will be served from the nginx docker file used in production. Anyway, we can try merging it and see if it helps 🤞 🙏
It is possible to add a verification in the test workflow, as it's using the real docker image that will be deployed to production later:
open-bus-map-search/.github/workflows/validate.yaml
Lines 77 to 78 in 1a5b121
- name: Run application | |
run: docker run -d -p 3000:80 ${{ env.DOCKER_APP_IMAGE_NAME }}:${{ env.DOCKER_APP_IMAGE_TAG }} |
291aee1
to
362560b
Compare
I added the test for file existence as you said and it seems to be missing. |
seems like you're testing for the existence of |
362560b
to
c425795
Compare
I will push this commit and create another one for the fix that you mentioned |
Description
Test and fix the issue with hash.txt file that needs to be created during the build process