For per-project config, optional co-location with project's own source.

Open paul-hammant opened this issue 12 years ago • 1 comments

scm-sync-configuration-plugin currently stores config in one repo.

It would be great to have an option of storing config alongside the sources/build-file of project in question. This way developers for the project itself, can make changes (provided they don't break the XML) without needing accounts/permissions for Jenkins itself.

i.e. if they are permitted to the source tree itself, they are permitted to make changes to the CI configuration.

CruiseControl had this feature in 2006, and we made it more robust - http://markmail.org/message/epsjbwqmspydu2tt - after the initial release - http://markmail.org/message/cq5ss23z3pmcokor

Oct 09 '13 12:10 paul-hammant

I think you will be interested in watching this improvement

(prefer submitting issues on jira, github won't be checked really often)

Oct 09 '13 13:10 fcamblor