How to restrict the Change-Set size in EWM
2 answers
Why? For what purpose? What is the problem?
EWM provides advanced properties. In the advanced properties you can specify "Versioned Content Maximum Size". This is by default 0 - unlimited. You can set a value, it would limit, as far as I know, the maximum size of a file that can be checked in. I don't think it limits on change set level.
You can configure EWM SCM to store large content in a binary repository. This is transparent for the user. It is controlled by com.ibm.team.scm.service.internal.content.VersionedContentService and "Versioned Content External Content - Artifact Minimum Size". See the documentation.
We do not have an option to specifically limit the size of a change set, but you can use the check-in preconditions:
https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.0.2?topic=reference-operation-preconditions-follow-up-actions
- Restrict the number of changes that can be contained within a single change set.
- Files cannot be checked in when they exceed the specified size limit.
- Restrict Check-in of files based on the specified MIME types and encodings.
- A resource cannot be checked in when its name is the same as another resource in the same location, even when the capitalisation is different.
You could also add a custom developed Precondition.