2 replies to this topic

[Rupert Ward (OxfordVR)]

We have a build stream that's had some files copied up to it that shouldn't have been - we missed that a folder needed to be excluded in the stream spec.

If we now add the exclusion of that folder to the stream spec, how can we go about safely removing the unwanted files from the stream?

We actually have 2 cases

1 - file was merged down in the folder that's now excluded
2 - file was merged down in a different location, but on the parent stream it was moved into an excluded folder

[Rupert Ward (OxfordVR)]

Re 1) Apologies, this seems to have been simpler than I thought. Getting latest has removed the files. Thought I'd tried that

Case 2 is still a problem though.

We have some large files that were mistakenly submitted in the root folder of the parent stream and merged to its child. Now, those files have been moved into a subfolder in the parent stream. But the subfolder is excluded in the child stream, so the delete/move pair is being ignore when we merge down. But we'd like those files to no longer be there in the child stream.

Is it safe to delete them from the child stream? What would happen when we copy back up to the parent?

[Sambwise]

It feels like the solution here is to exclude them from the child stream (in whatever path they currently exist in there); if you delete them, odds are at some point you'll do a merge or copy that will propagate the delete to somewhere that you don't want it to go.  Since the issue here is that you want these files to exist, just not in this particular stream, you should exclude them via the stream paths rather than delete the files themselves.