Using deps in CI
Most CI systems have a cron or scheduled job function,
which is how we recommend using
This way you can decide how often you want updates (daily, weekly, monthly, etc.) and keep slow dependency updates out of your normal commit pipeline.
This way you'll also get dependency updates even if you haven't committed to the repo recently.
The basic steps for setting up
deps ci are:
- Copy your
- Add a scheduled job that installs and runs
- Set any other required environment variables and secrets
Supported CI providers:
deps ci automatically detects and configures various settings for common CI providers.
This includes setting
git config user name and email,
and changing the git remote from ssh to https.
To disable the automatic configuration (if you have other requirements or want to do it yourself) use
deps ci --manual.
For specifics on what is configured and how, you can read the code here.
Filtering by type or path
In some container-based CI systems, you'll only have certain languages and requirements installed in certain containers.
You can use the
--path options to run the appropriate updates based on the container you're in. For example, use
deps ci --type python in your Python container. Likewise you can use
deps ci --path docs. Both
--path also support negation, allowing you to do
--type js in one container and
--type !js in another.