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

Run automated tests 1 #6

Open
wants to merge 36 commits into
base: automate-tests-merge-1
Choose a base branch
from

Conversation

MukuFlash03
Copy link
Owner

No description provided.

Mahadik, Mukul Chandrakant and others added 30 commits July 16, 2024 10:57
…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.
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.
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.

1 participant