Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Dependency CI – Continuous testing for your dependencies

dependencyci.com

Post reply on HN
Print view View original

61–64 of 64 posts

Re: Show HN: Dependency CI – Continuous testing for your dependencies

#61

Post by happyslobro »

andrewnez wrote: post #21
code_research wrote: post #5

This 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…

Agreed, I'll definitely the ability to move your dependencyci.yml file into a .github folder like the issue and pull request templates: https://github.com/blog/2111-issue-and-pull-request-template...

How about we put each individual config file in its own individual directory? We could name the directory after the file too, so that it is clear where each file is ;)

No but seriously, I don't think this mess of config files in the project root is really a big deal. I already grouped the interesting stuff under /src. If it is a big deal, then lets hash out an RFC that covers the general concept of "configuration" once and for all and be done with it.

Re: Show HN: Dependency CI – Continuous testing for your dependencies

#62

Post by happyslobro »

tomstuart wrote: post #33
yellowsir wrote: post #32

Earlier quoted context omitted.

its bad decision making. but to be fair dependency ci will add gitlab and bitbucket in the future. it still sucks that awesome tools like this are github first, git is a central tool and tools arround git should not depend on any hoster at all - imho

What alternative decision are you imagining? A service like this can’t depend on Git alone. It needs to know when the repo is updated (e.g. GitHub’s webhooks) and has to publish its results somewhere (e.g. GitHub’s commit statuses). So it only really works with hosted repos. Since each hosting service has a different API, each integration needs to be built individually. And it makes sense to integrate with GitHub fir…

Maybe server-side git hooks would do the trick? Can we assume that any "decent" git server will be able to run a bash script? A service could instruct the user to download a couple scripts and put them in .git/hooks. Or just copy and paste a wget command from within the repo root.

https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks

Re: Show HN: Dependency CI – Continuous testing for your dependencies

#63

Post by happyslobro »

insomniacity wrote: post #39
tomstuart wrote: post #33

Earlier quoted context omitted.

What alternative decision are you imagining? A service like this can’t depend on Git alone. It needs to know when the repo is updated (e.g. GitHub’s webhooks) and has to publish its results somewhere (e.g. GitHub’s commit statuses). So it only really works with hosted repos. Since each hosting service has a different API, each integration needs to be built individually. And it makes sense to integrate with GitHub fir…

It's the most popular repo host on HN for sure, but think about all the private repos behind corporate firewalls etc!

Some of which are Github Enterprise :p

Re: Show HN: Dependency CI – Continuous testing for your dependencies

#64

Post by chriswarbo »

tomstuart wrote: post #33
yellowsir wrote: post #32

Earlier quoted context omitted.

its bad decision making. but to be fair dependency ci will add gitlab and bitbucket in the future. it still sucks that awesome tools like this are github first, git is a central tool and tools arround git should not depend on any hoster at all - imho

What alternative decision are you imagining? A service like this can’t depend on Git alone. It needs to know when the repo is updated (e.g. GitHub’s webhooks) and has to publish its results somewhere (e.g. GitHub’s commit statuses). So it only really works with hosted repos. Since each hosting service has a different API, each integration needs to be built individually. And it makes sense to integrate with GitHub fir…

> It needs to know when the repo is updated (e.g. GitHub’s webhooks)

post-receive hooks work well for this. I use them to push changes from my laptop up to my server and GitHub (which I use as a free mirror). My server uses a post-receive hook to regenerate a HTML view of the repo.

> has to publish its results somewhere (e.g. GitHub’s commit statuses)

Git has really good email integration.

Post reply on HN