test: openpipeline pipeline groups E2E#983
Draft
Kirdock wants to merge 1 commit intofeat/openpipeline-pipeline-groupsfrom
Draft
test: openpipeline pipeline groups E2E#983Kirdock wants to merge 1 commit intofeat/openpipeline-pipeline-groupsfrom
Kirdock wants to merge 1 commit intofeat/openpipeline-pipeline-groupsfrom
Conversation
df7d39d to
b919ffc
Compare
9971a17 to
8d38dec
Compare
This adds the E2E tests for the pipeline groups. The examples are mostly identical. It's two pipelines, an empty one and one with davis/metricExtractions/securityContext defined, depending on whether it's enabled on that resource. One pipeline group that creates a group with the stages of a pipeline (the second-mentioned one) and assigns it to another pipeline (the first-mentioned one)
8d38dec to
b6c3f1a
Compare
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.
Why this PR?
The pipeline groups need to be tested, and there need to be some examples
What has changed?
This adds the E2E tests for the pipeline groups. The examples are mostly identical.
It's two pipelines, an empty one and one with davis/metricExtractions/securityContext defined, depending on whether it's enabled on that resource.
One pipeline group that creates a group with the stages of a pipeline (the second-mentioned one) and assigns it to another pipeline (the first-mentioned one)
How does it do it?
By adding examples to pipeline groups and tests that execute them.
How is it tested?
Every example is tested except the ones that are not enabled.
How does it affect users?
N/A
Issue: CA-16607
Notes
Some tests are currently not working due to a bug