Unable to Find Repository Location on Promotion (SVN) #2815

Michaelcc73 · 1 decade ago

We are running into an issue with the checkout step (SVN) of a promotion build. We are currently running QB 5.1.20.

The promotion has 1 repository defined on it (inherited and shared from the root configuration). The URL is parameterized and passed in by the build being promoted, and since it is the same repository definition as the original configuration it is desired that the original revision number is checked out.

Multiple configurations use this same promotion. We are finding that if the previous run of the promotion configuration was promoted from a different configuration and with a different repository URL, if the repository containing the URL to be checked on the current promotion does not have a revision as high as the revision checked out on the last run of the configuration (different URL/potentially different repository), the checkout step will fail with following error:


Failed to run command: "C:\Program Files\TortoiseSVN\bin\svn.exe" log https://myrepo/svn/MiscJavaWebApps/MyApp/branches/mybranch/ --non-interactive --trust-server-cert -v --xml -r 4429:18071 
Command return code: 1
Command error output: svn: E175002: Unexpected HTTP status 500 'Internal Server Error' on '/svn/MiscJavaWebApps/!svn/rvr/4429/MyApp/branches/mybranch'

svn: E160006: Additional errors:
svn: E160006: No such revision 18071

In this scenario, the previous run of this promotion was from a different configuration and the revision of the URL checked out on that run was 18071. The repository this run is attempting to checkout does not have a revision this high.

We have turned off the 'Record SCM Changes' option but that did not resolve the issue. Is there an issue with the way we have this configured?

Thanks,
Mike Cordeiro

replies 6
views 2719
stars 0

robinshen ADMIN · 1 decade ago

Please make sure repository url evaluates to same value in source build and target build when do the promotion, as promotion checkouts the same revision used by source build, and that revision may not exist if you are checking out a different url than original.

Michaelcc73 · 1 decade ago

The url is always the same between the source build and the target build, as it is passed as a variable on the promotion. The promotion is shared among multiple configurations, so consecutive runs of the promotion can come from different configurations and thus have different URLs.

The problem occurs when those two urls point to different repositories and the revision checked out on the previous run is larger than the highest revision in the repository of this run.

We believe this may have been something introduced between 5.1.14 and 5.1.20, as we did not run into this issue prior to upgrading.

Thanks

robinshen ADMIN · 1 decade ago

We have not introduced any changes in this regard between 5.1.14 and 5.1.20. Are you able to reproduce this issue with a sample database? If so, please take backup of the sample database and send to [robin AT pmease DOT com] with reproducing steps.

Michaelcc73 · 1 decade ago

Hi Robin,

Just wanted to ensure you received my email (sent 5/20/2014) regarding this issue.

Thanks

robinshen ADMIN · 1 decade ago

Yes, this is a bug and we have got it fixed in below build:
https://build.pmease.com/build/2675/overview
Please upgrade to this build and keep "record SCM changes" turned off.

I also notified you about the fix in 5/21 via email you used in this post. But unfortunately it seems that you did not get that email for some reason.

Michaelcc73 · 1 decade ago

Thanks. Sorry, didn't seem to get your email.

Upgrading to 5.1.27 resolved the issue.

Thank you for your help