News for hackers. Stuff that matters.

A comment on The creeping scourge of tooling config files in project root directories. Parent comment

Re:The creeping scourge of tooling config files in project r... by pm215 on Thursday August 06, 2020 @03:11AM (#24068781)
I think there are similarities -- the project's root is the project's, so why does eg the Travis CI system get to insist on having a config file sat in the project root?
[ Parent | on HN ]
Re:The creeping scourge of tooling config files in project r... by pas on Thursday August 06, 2020 @04:16AM (#24069056)
Where should it go?

Just like the gitlab-ci.yml, it handles things related to the whole repo, it basically runs a script in the root of the repo anyway.

Sure, supporting other paths is useful (eg. in case of a monorepo), but this default seems sane. Though I'm interested in where others move it, and why.

[ Parent | on HN ]
Re:The creeping scourge of tooling config files in project r... by dijit on Thursday August 06, 2020 @04:48AM (#24069206)
it's pretty common to have a .ci folder for your build scripts.

But nothing is fundamentally wrong either with XDG-esque directory structures.

.config/travis/

.ci/travis/

all the same to me, as long as it's consistent.

[ Parent | on HN ]
Re:The creeping scourge of tooling config files in project r... by rumanator on Friday August 07, 2020 @08:08AM (#24080993)
> the project's root is the project's, so why does eg the Travis CI system get to insist on having a config file sat in the project root?

Because it defines the project's CICI pipeline? Aka how the project is built, tested, delivered, and deployed?

I mean, that's a more fundament part of the project than which files should be automatically ignored when committing stuff to git (i.e., .gitignore)

[ Parent | on HN ]