[JIRA] (JENKINS-10449) Excluded regions do not exclude commits from changelog

[brent.atkin...@gmail.com (JIRA)]

Brent Atkinson commented on JENKINS-10449 Excluded regions do not exclude commits from changelog Thanks for explaining, I agree with your reasoning and it matches my initial thinking. My personal preference would be to never exclude and use proper sub-trees. However, assuming that there are valid reasons for exclusion, which is suggested by the fact it exists: If it affects the build, it's a misconfiguration to exclude something that matters. You want to run verification on relevant changes. If there are a lot of them, like developer docs needing locality to code, you don't want to be spammed with those changes When excluding noisy edits that aren't functionality related. The full changelog may actually do more to hide changes in noise. Ultimately, you want the misconfiguration fixed because you were wrong to exclude in the first place. I can see valid cases where the changes in the excluded area are particularly long and it's unlikely they'll be affecting anything, docs for example. I also can see wanting to have those edits omitted from the stream rather than spamming on the next build. It's the same reasoning, but a simulation of http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira