About Depfu
Depfu automates updating your dependencies so you spend less time keeping your app up-to-date and secure.
Depfu continuously updates your dependencies one gem at a time and creates a pull request with all the info you need. You stay in control if and when to merge.
Starting with Depfu and CodeShip is fast and easy. The Depfu documentation does a great job of providing more information about how to set up Depfu itself, in addition to the instructions below.
|
At the moment Depfu only works with Ruby projects hosted on GitHub. Support for more languages and other SCMs is planned. |
CloudBees CodeShip Pro
GitHub Status API
Depfu uses the results of your build to show you the risk of a dependency update. For that Depfu doesn’t run your tests, but gets the results directly from GitHub Statuses.
If you use CodeShip with a GitHub repo this works out of the box and is enabled by default. But it’s configurable in the "General" settings for your CodeShip project, so make sure to have that enabled.
You don’t need to change anything in your codeship-services.yml file to make Depfu work with CodeShip.
Branches and Pull Requests
CloudBees CodeShip Pro automatically builds all branches and pull requests that get pushed to GitHub, which is what Depfu needs to automate your dependency updates.
If you have limited your running the tests step to only
certain branches using the
tag/exclude attribute, make sure the Depfu branches are allowed. All Depfu branches
start with depfu/.
|
CloudBees CodeShip Basic
GitHub Status API
Depfu uses the results of your build to show you the risk of a dependency update. For that Depfu doesn’t run your tests, but gets the results directly from GitHub Statuses.
If you use CodeShip with a GitHub repo this works out of the box and is enabled by default. But it’s configurable in the "General" settings for your CodeShip project, so make sure to have that enabled.
You don’t need to change anything in your setup commands to make Depfu work with CodeShip.