Paul Jefferies Posted March 7, 2017 Report Share Posted March 7, 2017 Hi We are using the latest version of the plastic scm plugin for TeamCity SNAPSHOT-201703031558 running on version 10.0.4 (build 42538). We have also upgraded the client on the build servers and agents to version 5.4.16.814 (Doobie Brothers - China Groove) Since this update the checkout rules to exclude folders and repository items no longer function and seem to return the below error Before this update these builds worked perfectly. Is this a known/expected issue and is there a planned resolution? Link to comment Share on other sites More sharing options...
mig Posted March 8, 2017 Report Share Posted March 8, 2017 Hi Paul, I'm sorry you're experiencing this issue. It hasn't been reported previously. As I see on the screenshot, you're using server-side checkout, right? Could you please send us the TeamCity VCS log file, compressed in .zip or .gz format? It's located by default at ${TEAMCITY_SERVER_HOME}/logs/teamcity-vcs.log . Thank you! Regards, Miguel Link to comment Share on other sites More sharing options...
Paul Jefferies Posted March 8, 2017 Author Report Share Posted March 8, 2017 Hi Miguel, Please find attached the VCS logs as requested. We are using server side checkout as when I have used Agent side checkout the rules placing the files from the repositories into their specific locations does not seem to work - this breaks all of the library references to interdependent files from different repositories so this has not been a viable option. Since the update I did try (as an experiment) to checkout on the agent and received the error message that checkout rules were not supported on agent side checkout - the system failed again. many thanks in advance for your help on this! PJ teamcity-vcs.log.zip Link to comment Share on other sites More sharing options...
mig Posted March 10, 2017 Report Share Posted March 10, 2017 Hi Paul, I've had a look at the logs and it seems TeamCity is not properly solving the checkout rules when paths are remapped. We'll need some time to analyze the issue and produce a fix, though. We'll notify you as soon as the fix is published! I'm really sorry for all the inconveniences. Regards, Miguel Link to comment Share on other sites More sharing options...
Paul Jefferies Posted March 17, 2017 Author Report Share Posted March 17, 2017 Hi Miguel, Do you have any updates on this issue or possible workaround? It is now causing serious issues with some of the projects we are now having to build and implement. The issue has also started affecting checkout rules set up to map specific folder structures. Your help is appreciated. PJ Link to comment Share on other sites More sharing options...
mig Posted March 27, 2017 Report Share Posted March 27, 2017 Hi Paul, I'm sorry about the issues you're experiencing. The fix has been scheduled to be implemented in the following days, We'll notify you as soon as it's ready to be released. Regards, Miguel Link to comment Share on other sites More sharing options...
Paul Jefferies Posted April 7, 2017 Author Report Share Posted April 7, 2017 Hi Miguel, I have noticed a new version of the plugin has been released does this address the issue of interpreting the mapping rules? many thanks in advance, PJ Link to comment Share on other sites More sharing options...
manu Posted April 7, 2017 Report Share Posted April 7, 2017 Hi Paul, the mapping rules issue is fixed but not released yet. It has to go trough the release pipeline. As soon as we publish it we'll update this thread. Link to comment Share on other sites More sharing options...
mig Posted April 17, 2017 Report Share Posted April 17, 2017 Hi Paul, I'm glad to notify you that the fix for this bug you detected has been released in our latest version 6.0.16.1013! Regards, Miguel Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.