Remove pipeline test config json#150
Merged
ycombinator merged 5 commits intoelastic:masterfrom Mar 17, 2021
Merged
Conversation
Contributor
Author
|
I expect CI to fail on this PR as it stands at the moment because I have deliberately not yet removed the Once this CI failure is confirmed, I will remove the |
7 tasks
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪 |
Contributor
Author
Proceeding with removing the offending file now... |
mtojek
approved these changes
Mar 17, 2021
This file contains hidden or 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.
What does this PR do?
This PR removes the deprecated JSON-formatted pipeline test configuration files.
Why is it important?
In #139, we deprecated JSON-formatted pipeline test configuration files. Stakeholders were immediately notified of that change, including the notification that the deprecated files would be removed in a couple of weeks. We're at that point in time now.
Checklist
test/packagesthat prove my change is effective.versions/N/changelog.yml.Related issues