Tracking Jenkins changes #2133
Description
Originally posted by @sam-github in #2087 (comment)
I think the question of tracking and documenting changes is an issue, but not directly related.
Maybe it should be in a seperate issue, but continuing here since its where we are: if Jenkins itself had a way of tracking and explaining config changes, that'd be ideal, though I haven't bumped into it (but I'm far from a Jenkins expert).
If its not a Jenkins featue, our options seem limited.
A github centric expectation would be that for any config change there should be an issue open that its related to, and perhaps there should be a config label applied to every issue that resulted in or is related to a jenkins config change.
I think this is pretty reasonable, but is not perfect:
- its hard to describe UI made changes in github issues, and screenshots are painful to make and not searchable
- the opposite flow, that @rvagg describes, is the one we want, wherein we get a
git blame-like ability to look at something in the Jenkins UI, and then can somehow follow a trail back the github issue that motivated the change