[#BAM-341] Cannot change version repositories

Bamboo

Cannot change version repositories

Created: 17/Oct/06 02:11 AM Updated: 16/Nov/06 04:38 PM

Component/s:

Administration (Projects)

Affects Version/s:

0.5

Fix Version/s:

0.6

Time Tracking:

Original Estimate:

2 hours

Remaining Estimate:

2 hours

Time Spent:

Not Specified

Participants:	Mark Chaimungkalanont [Atlassian] and Riaz Khanmohamed
Since last comment:	2 years, 9 weeks, 6 days ago
Number of comments:	3
Labels:

Description

« Hide

We have a build setup under cvs. We have now moved to svn, and want to switch. Although it gives the option to change the repository to svn, it doesn't seem to want to save it.... and so reverts back to cvs

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Riaz Khanmohamed added a comment - 17/Oct/06 02:14 AM

FYI, log entries post hitting save:

2006-10-17 08:13:27,426 INFO [SocketListener0-2] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.ww2.actions.build.admin.ConfigureBuildRepository: Build: com.atlassian.bamboo.build.LegacyBuildObject@c61ff06d
2006-10-17 08:13:28,051 WARN [SocketListener0-2] [LocalizedTextUtil] Unable to find text for key 'repository.type.description' in 'class com.atlassian.bamboo.ww2.actions.build.admin.ConfigureBuildRepository' and locale 'en_US'
2006-10-17 08:13:33,488 INFO [SocketListener0-2] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.ww2.actions.build.admin.ConfigureBuildRepository: Build: com.atlassian.bamboo.build.LegacyBuildObject@c61ff06d
2006-10-17 08:13:34,379 INFO [SocketListener0-2] [BuildAwareInterceptor] Set build on BuildAware com.atlassian.bamboo.ww2.actions.build.admin.BuildConfigurationSupport: Build: com.atlassian.bamboo.build.LegacyBuildObject@c61ff06d

[ Permlink | « Hide ]

Riaz Khanmohamed added a comment - 19/Oct/06 06:24 AM

As a follow on, I don't believe beetlejuice ever worked in letting you change the source repository either.

It may be easiest to disable the ability to change repositories after the build has been created. However, through the wonders of xml hackery, it is possible to switch repositories, but the first update needs to be on a clean checkout folder rather than an update call on a current one.

My way of changing it without losing history was (in case you intend to implement this ability):

1) changed project.xml for individual project from

<myRepository class="CVSRepository">
<myModule>[MODULE NAME]</myModule>
<myCvsRoot>[CVS ROOT]</myCvsRoot>
<myRepositoryUrl>[REP URL]</myRepositoryUrl>
<myRepositoryUrlRepoName></myRepositoryUrlRepoName>
<myQuietPeriod>2000</myQuietPeriod>
<myTriggerIpAddress>[IP ADDRESS]</myTriggerIpAddress>
</myRepository>

<myRepository class="SvnRepository">
<myRepositoryUrl>[SVN ROOT]</myRepositoryUrl>
<myWebRepositoryUrl>[REP URL]</myWebRepositoryUrl>
<myUsername></myUsername>
<myWorkingDirectorySubDirectory>[MODULE NAME]</myWorkingDirectorySubDirectory>
<myWebRepositoryUrlRepoName>[REP SUB NAME]</myWebRepositoryUrlRepoName>
<myLatestRevision>12509</myLatestRevision>
<myRequiresPreClean>false</myRequiresPreClean>
</myRepository>

2) renamed the checkout build-dir folder to [MODULE]CVS (not necessary - was a temporary measure) so it would checkout the module from scratch.

That's it. Hope this helps

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 01/Nov/06 11:01 PM

All works again now