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

Too much jobs :( #28

Open
mateusoliveira43 opened this issue May 30, 2023 · 2 comments
Open

Too much jobs :( #28

mateusoliveira43 opened this issue May 30, 2023 · 2 comments

Comments

@mateusoliveira43
Copy link
Owner

CI complained about the number of jobs

Continuos Delivery: .github#L1
Strategy produced more than 256

Think how to solve this issue

@mateusoliveira43
Copy link
Owner Author

mateusoliveira43 commented May 30, 2023

First idea: just send new images

From last execution, instead of 260 matrix runs, it would have run only 20 matrix runs

./scripts/pipeline.py cd | jq '.include[].version'

With this, when adding X new poetry versions, instead of running {number of poetry versions} * {number of python versions} * {number of distro variations} matrix jobs, it would run X * {number of python versions} * {number of distro variations} matrix jobs

And, when adding Y new python versions, instead of running {number of poetry versions} * {number of python versions} * {number of distro variations} matrix jobs, it would run Y * {number of poetry versions} * {number of distro variations} matrix jobs

@mateusoliveira43
Copy link
Owner Author

mateusoliveira43 commented May 30, 2023

Going to follow the first idea, but it will happen again once numbers gets too big, so still needs a proper solution

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

No branches or pull requests

1 participant