Why are changes to components not handled as other changes
Hi,
I find this to be really strange. Weve set a precondition that you cannot deliver any change without a WI, however, adding, renaming or removing a component does not adhere to these rules. A component can potentially contain a lot of files and should IMHO be treated as any other change.
Am I missing some crucial concept definition of components?
Regards,
Hampus
I find this to be really strange. Weve set a precondition that you cannot deliver any change without a WI, however, adding, renaming or removing a component does not adhere to these rules. A component can potentially contain a lot of files and should IMHO be treated as any other change.
Am I missing some crucial concept definition of components?
Regards,
Hampus
One answer
No, you're not missing any concept. This is a gap in the SCM preconditions support.
For more details see 110283: all delivery preconditions should offer to apply onto to a set of components.
The only workaround I'm aware of is to reduce the permissions on the component operations to restrict them to people who can be trusted to ensure all changes meet the preconditions. For a component addition, one could add the initial baseline, then deliver the changes separately.
For more details see 110283: all delivery preconditions should offer to apply onto to a set of components.
The only workaround I'm aware of is to reduce the permissions on the component operations to restrict them to people who can be trusted to ensure all changes meet the preconditions. For a component addition, one could add the initial baseline, then deliver the changes separately.