Is there an easy way for me to move this project back from 'prep' to 'shared' in CM Synergy 6.4

BenN's picture
BenN asked on November 29, 2011 - 11:05am | Replies (2).

We have a few shared projects used as buckets for adhoc pieces of code, and it looks like one of them was checked in yesterday; they normally sit at 'shared' status, but one has now changed to 'prep' status and build managers are now unable to add new objects (permission denied to workarea folder).

Is there an easy way for me to move this project back from 'prep' to 'shared' that anyone knows?

Thanks in advance,

Ben

2 Answers

David Honey's picture

Hi Ben,

There are two things you might consider. The first is simply to perform a copy project to a new prep version and ensure that the work area location used has the required file permissions on the directory.

If you don't want to do that, there is a second option, but that requires a slight model customization. By default, the base model only defines the transitions listed below from [i]prep[/i] state:
[code]
transition prep1 = prep -> integrate;
transition prep2 = prep -> test;
transition prep3 = prep -> sqa;
transition prep4 = prep -> released;
[/code]

The platform code forbids any transitions from a static state to a non-static state. However, since both [i]prep[/i] and [i]shared[/i] are both non-static states, this platform restriction does not forbid adding such a transition.

If you want to add a transition, first ensure that you have a usable backup of the database just in case anything goes wrong. Then perform the following:
1) Start a CLI session as a user that has access to the [i]ccm_admin[/i] role.
2) Change your role to [i]ccm_admin[/i].
3) ccm query -t model -n base
4) ccm attr -m access @1

In the editor, find the transitions from prep and add the extra transition so you end up with:
[code]
transition prep1 = prep -> integrate;
transition prep2 = prep -> test;
transition prep3 = prep -> sqa;
transition prep4 = prep -> released;
transition prep5 = prep -> shared;
[/code]

Stop and restart your CLI session (many model attributes are cached on startup so changes do not become effective until a new session is started), and then transition the project to shared.

You may want to reverse the steps that added the transition since, in general, it's not a usual transition to have. There is a danger that a prep project could have members in prep state, and transitioning that project to shared would leave it with contents that are normally inconsistent with such a project.

BTW, as a reminder, Synergy 6.4 has been deprecated and out of support under standard maintenance for some years. Currently supported releases are Synergy 7.1 and 7.2.

Regards,
David.

BenN's picture
BenN replied on December 1, 2011 - 9:03am.

David,

thank you for what is undoubtedly one of the best responses I have ever had on a Forum! Having only started with Synergy a few months ago, and then replacing Glyn_Mo as the only Admin in our organisation, it is great to know that there is such a helpful forum to turn to when someone (me?) breaks everything.

I tried the second suggestion, and that worked perfectly, so panic over.

I have become well aware of the issues surrounding 6.4 and its redundancy, but unfortunately all I can do is make the case for upgrade - the choice lies elsewhere...

Thanks again,

Ben

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.