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

[tests-only] Balance out length of web acceptance test pipelines #2872

Closed
Tracked by #765
phil-davis opened this issue Dec 13, 2021 · 3 comments
Closed
Tracked by #765

[tests-only] Balance out length of web acceptance test pipelines #2872

phil-davis opened this issue Dec 13, 2021 · 3 comments
Labels

Comments

@phil-davis
Copy link
Contributor

Similar to owncloud/web#6095

A recent full-ci run was done for #2871 - drone logs https://drone.owncloud.com/owncloud/ocis/8322

  1. have a look at that CI run and comment in this issue about the range of run-times of the 20 web-tests pipelines

Then we can discuss/decide if it is worth manually allocating test suites to pipelines, to balance the run times better. (Currently they are auto-split into 20 pipelines)

If so, then:

  1. Balance out the number of features/scenarios in each pipeline so that each pipeline can finish in about the same time (let's aim for about 15 minutes maximum for a pipeline). Do not increase the total number of pipelines.
@stale
Copy link

stale bot commented Feb 11, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status:Stale label Feb 11, 2022
@phil-davis
Copy link
Contributor Author

This can still be looked at. I thought that the stale bot would ignore issues with the QA:team label.

@amrita-shrestha
Copy link
Contributor

new issue has been created in the QA repo.So closing this issue

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

No branches or pull requests

2 participants