Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

Support selecting multiple test suite #309

Closed
mdelapenya opened this issue Sep 16, 2020 · 1 comment · Fixed by #324
Closed

Support selecting multiple test suite #309

mdelapenya opened this issue Sep 16, 2020 · 1 comment · Fixed by #324

Comments

@mdelapenya
Copy link
Contributor

We currently use a select in Jenkins UI, so only a single element is accepted when running this job. So upstream triggers can only pass one test suite (helm, integrations or metricbeat at this moment).

We'd like to pass a comma-separated list so an upstream job is possible to tell the downstream to run helm && metricbeat, i.e.

@mdelapenya
Copy link
Contributor Author

When calling from Beats/packaging job, we'd like to be able to:

  • when elastic-agent is modified in Beats, trigger the ingest-manager test suite
  • when metricbeat is modified in Beats, trigger the helm, integrations and ingest-manager test suites
  • when filebeat is modified in Beats, trigger the helm and ingest-manager test suites
  • when libbeat is modified in Beats, trigger all the test suites

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant