Concourse lets you put the file anywhere; the act of applying configuration is distinct from committing it.
Initially people put `pipeline.yml` or `concourse.yml` files in the top of their repo.
It's rapidly evolved so that typically you'll find either `ci/pipelines/{some,number,of,pipelines}.yml` in the main repo, or a separate repo for the CI/CD system. I prefer the former, most teams I've seen so far prefer the latter.
The amount of top-level files in these projects has started to become quite large, and it is unclear at first glance to see what it is important when exploring a new ecosystem.
I'd like to see these products would move in a direction where these were would do any/some of the following:
1) use a file extension rather than "important" describing filename (.docker for Dockerfiles and .groovy/.jenkins for Jenkinsfile)
2) moved into a product specific folder (travisci/ci.yml, github/ for the issue and pull request templates)
3) use yet another top level file for indirection that is agreed upon (my initial thought is something named integrations.yml)
Could developers of these tools please stop dictating where people have to put the "Blahfile" dsl config files and finally allow people to configure these kind of details.
Also I would like to propose a common standard directory "projectroot/config" for these kind of files, NOT the project root directory itself.
Thanks for your attention!