You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do end-to-end tests in the CI, but the dockerfile generation is actually performed as a separate action.
What can we do to improve this?
Run the docker job after all other steps from main using the needs keyword. However, this still allows issues with the docker image itself (e.g. missing a port forward, or some compatibility issue with the image). Also, it might run too often this way.
In the docker job, run the e2e tests after building the image, but before pushing it. This requires some changes, because currently one action does both the pushing and the building.
The text was updated successfully, but these errors were encountered:
We do end-to-end tests in the CI, but the dockerfile generation is actually performed as a separate action.
What can we do to improve this?
docker
job after all other steps frommain
using theneeds
keyword. However, this still allows issues with the docker image itself (e.g. missing a port forward, or some compatibility issue with the image). Also, it might run too often this way.docker
job, run thee2e
tests after building the image, but before pushing it. This requires some changes, because currently one action does both the pushing and the building.The text was updated successfully, but these errors were encountered: