[WIP] upstream ci: Remove dependency on molecule #1254
Closed
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
rjeffman
force-pushed
the
remove_molecule
branch
6 times, most recently
from
ad32a87
to
026f46c
Compare
rjeffman
force-pushed
the
remove_molecule
branch
from
026f46c
to
f3edbda
Compare
|
Closing this in favor of #1260 |
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.
We only use molecule to build images and start testing containers, which adds unneeded complexity by increasing the software stack in a way that does not bring any advantage.
There's also risk that changes on molecule break the tests, which has happened a few times.
This change removes the dependency on molecule by using docker/podman directly to build and run the test containers.