Improve UI CI workflow with caching, micromamba, etc. #1098
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
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.
The set up wasn't consistent across the three UI jobs. I'm now trying out this GitHub Action to create and cache the Conda environment: https://github.com/mamba-org/setup-micromamba — seems to work very well.
I'm also removing the Python version matrix, and adding the
wait-ondev dependency to wait for the server to respond at127.0.0.1:8081. This will help catch problems with starting the MXCuBE server, since the E2E tests won't try to run if the server has not successfully started.🥳