Udpate scale-ci workflow #152
Open
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
chaitanyaenr
force-pushed
the
workflow
branch
from
8814c89
to
2eb5608
Compare
|
I think we can also deprecate scale-ci_ScaleUp_OpenShift.yml |
chaitanyaenr
force-pushed
the
workflow
branch
from
2eb5608
to
6bb5af5
Compare
|
we can also remove some remnants from scale-ci-pipeline.yml like https://github.com/chaitanyaenr/scale-ci-pipeline/blob/6bb5af5be3dc85db119e5a627b8b00d979e8641d/jjb/static/scale-ci-pipeline.yml#L153 @chaitanyaenr |
This commit: - Updates the scale-ci-workflow to depict the usage of the new tools including the Benchmark-operator, Kube-burner, Cerberus etc. and how it leverages Prometheus and Elasticsearch for metrics collection and storage. - Deprecates OCP 3.x stuff.
Done. Thanks. |
mohit-sheth
approved these changes
Jan 12, 2021
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.
This commit:
new tools including the Benchmark-operator, Kube-burner, Cerberus etc.
and how it leverages Prometheus and Elasticsearch for metrics collection
and storage.