Disable CI until a solution for molecule is found #260
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
I frequently have to deal with broken CI due to system changes: - systemd gets updated, and start to break cgroup integration of docker - docker includes a bug, so molecule tests starts to fail - molecule gets updated, dependencies are a mess - molecule[docker] gets updated, same issues. I am tired of maintaining this fragile CI. I will remove it. There is no less fragile option that I know of. Github actions could be used to test basic features, like deployment. It cannot test the clustering, as we do not have an inventory containing multiple nodes. If anyone is interested by brining the test coverage back, I am fine with it, please submit a PR.
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.
I frequently have to deal with broken CI due to system changes:
I am tired of maintaining this fragile CI. I will remove it.
There is no less fragile option that I know of.
Github actions could be used to test basic features, like deployment. It cannot test the clustering, as we do not have an inventory containing multiple nodes.
If anyone is interested by brining the test coverage back, I am fine with it, please submit a PR.