forked from EVerest/everest-demo
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Run automated tests 1 #6
Open
MukuFlash03
wants to merge
36
commits into
automate-tests-merge-1
Choose a base branch
from
run-automated-tests-1
base: automate-tests-merge-1
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ory loss issue Failure test case in this commit. Will test success next.
… file I'm expecting that since the mqtt server matrix job will refer to updated tagged image, it won't find it since it's still being built in manager matrix job. So it would fail the workflow?
I'm not sure this would work, as the order just defines the order in which the jobs are created. So, the jobs will still run parallelly, as I've already seen this all workflow runs. But I will still try it out. Documentation link: https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs#:~:text=The%20order%20of%20the%20variables%20in%20the%20matrix%20determines%20the%20order%20in%20which%20the%20jobs%20are%20created.
Trying out this to ensure only one matrix job runs at a time. Let's see if this solves the issue that manager matrix job isn't able to see the cached image layers from latest mqtt tagged image built in the workflow.
…e manually for my repo
Hoping that by doing this, the jobs are able to see the cached layers. I did see in previous runs that is possible. https://github.com/MukuFlash03/everest-demo/actions/runs/9985959128/job/27597677357 https://github.com/MukuFlash03/everest-demo/actions/runs/9985959128/job/27597677497
Had cleared cache via gh commands earlier and this interferred with the previous workflow run.
Trying to force it to load caches for both mqtt and manager by running docker build push action again. Build failed since Dockerfile context not specified - https://github.com/MukuFlash03/everest-demo/actions/runs/9998773200/job/27638557716 Running again after specifying it
Previous step is handling all logic to use TAG appropriately from .env file. Let's just re-use that value. Else needed to load from .env every place we need TAG.
… is built and used in docker compose
…g some COPY commands.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.