Skip to content
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

Update plugin test BK pipeline to parallel all steps #15440

Closed
andsel opened this issue Oct 13, 2023 · 0 comments · Fixed by #15454
Closed

Update plugin test BK pipeline to parallel all steps #15440

andsel opened this issue Oct 13, 2023 · 0 comments · Fixed by #15454
Assignees

Comments

@andsel
Copy link
Contributor

andsel commented Oct 13, 2023

The Buildkite pipeline supported_plugins_test_pipeline make an explicit depenceny between Tier1 and Tier2, giving priority to the ffirst:

- group: "Tier1 plugins test group"
key: "tier1_plugins"
steps:
- label: "Test Tier1 inputs"
command: ./ci/test_supported_plugins.sh -t tier1 -k input
- label: "Test Tier1 filters"
command: ./ci/test_supported_plugins.sh -t tier1 -k filter
- label: "Test Tier1 codecs"
command: ./ci/test_supported_plugins.sh -t tier1 -k codec
- label: "Test Tier1 outputs"
command: ./ci/test_supported_plugins.sh -t tier1 -k output
- label: "Test Tier1 integrations"
command: ./ci/test_supported_plugins.sh -t tier1 -k integration
- group: "Tier2 plugins test group"
key: "tier2_plugins"
# Wait all tier1 plugins testing ends before going on tier2
depends_on: "tier1_plugins"
steps:
- label: "Test Tier2 inputs"
command: ./ci/test_supported_plugins.sh -t tier2 -k input
- label: "Test Tier2 filters"
command: ./ci/test_supported_plugins.sh -t tier2 -k filter
- label: "Test Tier2 codecs"
command: ./ci/test_supported_plugins.sh -t tier2 -k codec
- label: "Test Tier2 outputs"
command: ./ci/test_supported_plugins.sh -t tier2 -k output

Remove this constraint, removing group definitions and flattening all the steps at the same level so that all can be launched in parallel.

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

Successfully merging a pull request may close this issue.

2 participants