[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 I agree, that was my first reaction as well. If you're doing this systematically it will be an uphill battle and definitely suggests you're fighting your tooling. However, when considering the reasons to exclude parts of the tree from triggering a build, I couldn't generate reasonable arguments for including those changes in the changelog. If the commits will be noise for the builds, it seems to follow that they'll be noise in changelog as well. That's when I started looking at this differently and started working on a solution. Would you mind sharing your rationale? Why would you want to see the logs from excluded regions and not verify the project stability by building? Understanding the common reasons for using exclusions/inclusions might help steer others clear of expecting this.

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