Having gotten to know Andrew a bit over the last few months, I can wholeheartedly say that he cares a lot about the open source community. DependencyCI and Libraries.io are labours of love and craftsmanship!
Show HN: Dependency CI – Continuous testing for your dependencies
11–20 of 64 posts
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#12Great idea! My company requires external libraries licenses to be revieved every half a year and it usually takes a couple of days to do so. Your project could be a real time-saver. Unfortunately the integration with Maven does not seem to work in most cases, if it did I would already have sent the link to our CTO.
You could use the VersionEye Maven Plugin for that: https://github.com/versioneye/versioneye_maven_plugin. It checks your dependencies against a license whitelist on the VersionEye server and if there is a violation it breaks your build on your CI server. That way you can enforce a license policy continuously. It's much better than just checking licenses once a year ;-)
I'm working on VersionEye since a couple years, it's a similar project and I open sourced it last week: https://blog.versioneye.com/2016/06/28/versioneye-goes-open-.... I'm following Andrews activities since a while and like what he did with libraries.io. Great job! As both projects have a big overlap and are open source now I'm open for collaboration :)
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#13I’ve been working on Dependency CI along with https://libraries.io , the service that powers it, in my spare time for the past few months, it’s great to finally get it out into the real world. Dependency CI works like Travis CI but for the dependencies of your application, checking them for license and status issues every time you push to GitHub. I've written a up a post on medium with more details: https://medium.co…
Can you please support Deb packages as well? Thanks
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#14The Debian project's Continuous Integration project [1] re-tests all dependent objects whenever a dependency within the Debian archive changes. This way, changes that might negatively affect dependents can be caught early.
This is immensely useful, especially to the maintainers of libraries.
In order for them to be tested, dependent objects have to declare their testability using the autopkgtest [2] interface.
[2] https://people.debian.org/~mpitt/autopkgtest/README.package-...
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#15I added my project and the service claims it has 0 dependencies (Listed in the build.gradle file). Bug? https://dependencyci.com/github/RichTeaLang/RichTea
Also having an "error" status or 0 dependencies with my gradle projects...
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#16I added my project and the service claims it has 0 dependencies (Listed in the build.gradle file). Bug? https://dependencyci.com/github/RichTeaLang/RichTea
Will investigate that for you shortly, I've only just added support for gradle, might be skipping some sections of file
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#17This is a very interesting service, thank you! May I ask you for some little thing that might change the (development) world? Would you please like to introduce a folder, where people might put their dependency.yml file - this is an effort to finally stop the spreading cancer of "put one more config file into the project root". I would like to suggest to call that folder simply "config" - all the projects and tools o…
I've thought of the same thing, but I feel that the horse has well and truly bolted, run back through the barn a few times, kicked some shelving over and then continued out the front and over the horizon at a brisk pace.
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#18Great idea! My company requires external libraries licenses to be revieved every half a year and it usually takes a couple of days to do so. Your project could be a real time-saver. Unfortunately the integration with Maven does not seem to work in most cases, if it did I would already have sent the link to our CTO.
Pivotal Labs have a similar problem -- ensuring that only whitelisted licenses are represented in a codebase -- and developed License Finder for this kind of auditing: https://github.com/pivotal/LicenseFinder
We also use it for Cloud Foundry. It's fairly robust.
I work for Pivotal, but not on LF.
Re: Show HN: Dependency CI – Continuous testing for your dependencies
#19Re: Show HN: Dependency CI – Continuous testing for your dependencies
#20Great work on this, looks very useful. Does it only work with GitHub? Would love to have this for my private GitLab instance
Yep. Same for Bitbucket. Or just support all git repos that are accessible via the public internet.
Github's pricing model means that lots of people can't use it for private repos - 'per repo' pricing isn't fun if you prefer lots of small repos.