create-nemesis-pipelines should by default generate pipelines for all 3 clouds #7106
Assignees
Labels
Bug
Something isn't working right
Comments
k0machi
added a commit
to k0machi/scylla-cluster-tests
that referenced
this issue
Jan 29, 2024
This change adjusts `create-nemesis-pipelines` cli command to accept multiple `--backend` arguments and makes it generate all supported backends by omitting the option altogether. The new option syntax is as follows: `./sct.py create-nemesis-pipelines --backend aws --backend gce [...]` Fixes scylladb#7106
2 tasks
fruch
pushed a commit
that referenced
this issue
Jan 29, 2024
This change adjusts `create-nemesis-pipelines` cli command to accept multiple `--backend` arguments and makes it generate all supported backends by omitting the option altogether. The new option syntax is as follows: `./sct.py create-nemesis-pipelines --backend aws --backend gce [...]` Fixes #7106
fruch
pushed a commit
that referenced
this issue
Jan 29, 2024
This change adjusts `create-nemesis-pipelines` cli command to accept multiple `--backend` arguments and makes it generate all supported backends by omitting the option altogether. The new option syntax is as follows: `./sct.py create-nemesis-pipelines --backend aws --backend gce [...]` Fixes #7106 (cherry picked from commit d613b63)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
currently
create-nemesis-pipelinesis generate AWS only by default.people that using it are not aware of it, and currently the azure pipeline are not aligned to how AWS pipelines were built
we should generate all of them when this command is being use
The text was updated successfully, but these errors were encountered: