[code_research]

I would like to ask you to please establish a new standard of NOT expecting all kind of config files in a project root directory - this is an annoying pestilence that has to stop and the Jenkins team could really help with that.

Please instead establish any kind of directory that is expected where all that project and tooling related meta files are kept, I would like to suggest a top level folder called "config" - but I really do not care, how this is called, as long as that top level config file annoyance will disappear forever.

I believe it might be acceptable to expect exactly one optional top level config file that might be called "configrc" that would contain only the path of that actual config path if this is not in a default place.

Thank you very much for your attention!

[stephenconnolly]

Well my original plan was that the default build instructions would be in a README.md file in the root of the source control as a verbatim block in the highest level heading containing the word "build"

If you needed any additional configuration for Jenkins specific instructions then that would be in a folder called ".jenkins"

Sadly, people did not embrace that project type... perhaps because it was given the nerdy name "literate" by a colleague of mine (who's name rhymes with Nichale Meale)

[i386]

So dry, Stephen :)