-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid rebuilding operator and checking ES twice #187
Conversation
5292aff
to
4536df6
Compare
/rerun all |
6ac5861
to
a24e408
Compare
Results for SNAFU CI Test
|
/rerun all |
a24e408
to
3c51d93
Compare
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO We should remove the es_check
in Ripsaw. It should be only checked via SNAFU (removing the double check).
Yeah, I get your point. However snafu's CI depends on ripsaw's CI and not the opposite. Checking ES in ripsaw's CI is the only way now to ensure changes in snafu and ripsaw don't break indexing. |
If there is a circular dependency, I wonder if we can set a var to skip indexing? by default the indexing is enabled, but if running w/ Ripsaw CI, we disable SNAFU |
3c51d93
to
5ce3135
Compare
Results for SNAFU CI Test
|
I think a variable for this is redundant. We are not removing the check_es script from SNAFU, we are just not calling it for the functions that are using ripsaw. If we add a new workload, foo, that is outside of ripsaw we can simply call the check_es script from foo's ci_test.sh file. Thoughts? |
Results for SNAFU CI Test
|
5ce3135
to
e05ef5e
Compare
!!! Couldn't read commit file !!! |
/rerun all |
Results for SNAFU CI Test
|
+1 This PR simplifies the overall CI besides of preventing double-checking of ES indices. |
@rsevilla87 CI from the last run is showing an error when building the benchmark-operator:snafu_ci
|
/rerun all |
Results for SNAFU CI Test
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
7317715
to
b40dabc
Compare
/rerun all |
Results for SNAFU CI Test
|
b40dabc
to
09903f4
Compare
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
/rerun all |
Results for SNAFU CI Test
|
Signed-off-by: Raul Sevilla <rsevilla@redhat.com>
09903f4
to
dd8d9dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Results for SNAFU CI Test
|
Would fix #186 along with avoid rebuilding and pushing ripsaw in each test.
Also simplifies the function wait_clean since deleting a namespace waits for the deletion of all objects within it by default.
Rather than doing all those "sed" invocations, we might use the image argument of the benchmark YAMLs to overwrite the image. However I'm not sure about that idea since we would have to reference each test benchmark CRD.
Thoughts?