Changing VCS root while having changes pending for/in a build

Hi,

what exactly happends in a scenario as described above when:

- the VCS root change discards the already collected changes -> the agent would get other versions of these files???
- don't knwo what other strange things could happen here... feel free to contribute

Is there a way to escape such a situation???
Best regards
Mark

3 comments
Comment actions Permalink

Hi Mark

Not sure I understand the question. After you change VCS root settings agent should perform clean checkout.
Could you provide some examples please.

Michael

0
Comment actions Permalink

Hi Michael,

the agent is not the problem.
The changes for such a build are not 'recalculated'. In my oppinion you wil have to discard the already collected changed files set and start from scratch.
So the changes overview is simply wrong in the Web UI.
Hope that clarified my question.

Regards
Mark

0
Comment actions Permalink

Aha, I got it.

This is the issue described in TW-2929.
UI shows changes from both old and new VCS roots, but actualy when next build starts they are not used - the agent performs clean checkout, and gets all the sources from new VCS root from scratch.

Michael

0

Please sign in to leave a comment.