Skip to content

Run CI tests on dependency updates #1524

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

Closed
tim-schilling opened this issue Nov 4, 2021 · 2 comments
Closed

Run CI tests on dependency updates #1524

tim-schilling opened this issue Nov 4, 2021 · 2 comments

Comments

@tim-schilling
Copy link
Member

#1523 started running the CI tests on a periodic basis to identify integration problems with dependencies or other libraries. Ideally we'd only run the CI tests when one of the dependencies actually changes. Otherwise we're wasting resources. I think the best option for this is to use Dependabot.

I think it'd be possible to do by using pip-tools and creating a requirements_ci.in and requirements_ci.txt file. This file would contain all the dependencies listed within the tox.ini file. The goal is to have Dependabot identify the changes in that requirements file, then create a PR which will run CI, thus identifying integration problems.

If we do go this route, I think it'd be a good idea to use the auto-merge functionality such that it will automatically merge these PRs specifically when they pass.

@matthiask
Copy link
Member

There seems to be a problem with dependabot where it's impossible to disable it on forks:
dependabot/dependabot-core#2804
numpy/numpy#18977

I'm not against it but one should be aware of this.

@tim-schilling
Copy link
Member Author

I'm going to close this. I'm not sure it's worth the inherent problems with managing dependencies and the forking issue.

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

2 participants