We have a similar problem to the one that celltestr reported in JENKINS-16654">JENKINS-16654. However, we would prefer to retain changelogs when the builds are incremental, while disabling them when switching branch or building after a long gap. Therefore, it would be useful if we could specify a size limit on the changelog (for instance, maximum number of changesets). When the size limit is reached, the changelog would be truncated (perhaps with a summary noting the total original size).
Originally reported by krandell, imported from: User-specified changelog size limit
- status: Open
- priority: Minor
- component(s): mercurial-plugin
- label(s): mercurial, performance
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251216-225446
Raw content of original issue
We have a similar problem to the one that celltestr reported in JENKINS-16654. However, we would prefer to retain changelogs when the builds are incremental, while disabling them when switching branch or building after a long gap. Therefore, it would be useful if we could specify a size limit on the changelog (for instance, maximum number of changesets). When the size limit is reached, the changelog would be truncated (perhaps with a summary noting the total original size).
We have a similar problem to the one that celltestr reported in JENKINS-16654">
JENKINS-16654. However, we would prefer to retain changelogs when the builds are incremental, while disabling them when switching branch or building after a long gap. Therefore, it would be useful if we could specify a size limit on the changelog (for instance, maximum number of changesets). When the size limit is reached, the changelog would be truncated (perhaps with a summary noting the total original size).Originally reported by krandell, imported from: User-specified changelog size limit
Raw content of original issue