It's all about the answers!

Ask a question

RTC: skip "Require work item approval" for some files only


Mark Frost (122) | asked Apr 08 '14, 1:03 p.m.
We use RTC 4.0.0.1 with precondition "Require work item approval" configured for our development stream. This is working well, however we've got one file only that contains test metadata, and frequently changes. This file needs to match the stream, so is also held in source control, but it doesn't really need strict control, and it would be faster for us if changes to that file only could be delivered without requiring approvals.

What's the best way to configure this in RTC? I think it can be done using two parallel streams, one for the single file, and one for everything else. These could be owned by two team areas with different operational preconditions configured. This seems a little complex for one file, is there anything simpler?

We have several RTC build engines (different platforms) running continuous build&test which would need to work with the solution. If two streams are used, can each build engine's workspace be configured so it receives changes from both the development stream and also the matching no-approval stream?


Comments
sam detweiler commented Apr 08 '14, 2:05 p.m.

 you could also disable (not configure) the approval requirement for a person with a particular role and have them check in these files

2 answers



permanent link
Michael Valenta (3.7k3) | answered Apr 14 '14, 9:20 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
I can't think of a better way to do it. What Sam mentioned should work although it may not be what you want since that role could deliver any change without approvals. A build workspace can be configured to accept changes from multiple streams by scoping the flows for each stream in the flow table of the build workspace.

permanent link
Ralph Schoon (61.1k33643) | answered Apr 14 '14, 10:37 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
One additional idea: You could create a new "Requires Approval" precondition that basically wraps the existing one, reuses the schema and the configuration UI.
This could have a check that tests if the change set only contains the configuration file and, in this case aborts the check for the approval. The configuration UI would only needed to be deployed in the Eclipse Admin UI's for the administrators.

Just a thought. Not nice and easy, but the best I could come up with.

Your answer


Register or to post your answer.