Why precondition will be enforced against changeset in the baseline when replace with the baseline?
In RTC 4.0.1, two roles: one has no precondition against changeset, another one has precondition requiring workitem and comments for the changeset.
the developer has the first role can deliver the changeset without workitem association and created a baseline after that. Now configure admin with 2nd role needs to replace the component in another stream with the new baseline created by developer. When doing replace with the baseline, he got the problem that the changeset is missing workitem. The question is why the precondition applies to the changesets within the baseline? Is that how it should work and any reason behind that(as if we treat the changeset in the baseline as a new one?) Thanks
the developer has the first role can deliver the changeset without workitem association and created a baseline after that. Now configure admin with 2nd role needs to replace the component in another stream with the new baseline created by developer. When doing replace with the baseline, he got the problem that the changeset is missing workitem. The question is why the precondition applies to the changesets within the baseline? Is that how it should work and any reason behind that(as if we treat the changeset in the baseline as a new one?) Thanks
Accepted answer
The precondition applies to the baseline because it protects against users that would create a baseline and do a replace to get around the deliver precondition.
Comments
Thanks Tim for the info.
ok that makes since, i am doing this with scm command line and it shows what the errors are but no work items so you dont know what needs to be fixed. Is there a command we can use to fix these? I know in the gui we have a quick fix.
Can you describe your problem in more detail (ie. show the error message)?