Create new workspaces bound to existing repositories

[jeff]

Hello!
We have several SVN repositories on a SVN 1.6 server containing Powerbuilder applications (v 12.5.2) - among other files. I plan to use the SVN 1.7 client and TortoiseSVN 1.7 as well - and maybe Agent SVN. I am completely new to that tool and would like to ask if you might want to help me with a short guideline on how to create functional workspaces and PB projects.
The repositories each contain the files of one PB app and were so far managed through PushOK's SVNSCC. So PBG's are present but no PBL's. Our goal is to build a completely new workspace for each app each containing a PB workspace, several PBLs spread over different subdirectories – plus some PBLs containing a common class library whose repository is linked via an SVN „external“ property. We would be happy if somebody might want to show us the best way...
And another newbie question: Do we always have to edit AgentSVN's configuration if we want to switch to another PB workspace bound to a different repository?

Thanks a lot!

Jeff

[jussij]

Hi Jeff,

I am completely new to that tool and would like to ask if you might want to help me with a short guideline on how to create functional workspaces and PB projects.

On this page there is a video showing how to create a PB workspace and add it to Subversion using Agent SVN: http://www.zeusedit.com/agent/pb/classic.html

We would be happy if somebody might want to show us the best way...

This would be my suggestion.

Lets assume you have a simple PB project bound to Subversion using PushOK.

As a test I would do the following:

1. Backup the local working copy of that project. That backup will retain your current PushOK bindings.
2. Inside PB open that workspace and in the workspace properties remove the source control bindings. So now the workspace is no longer bound to source control.
3. Make sure that the Agent SVN configuration dialog is pointing to the repository of that PB project.
4. Now restart PB and in the workspace properties select Agent SVN as the source control provider.
5. Leave the project name blank and click on the ... button (see http://www.zeusedit.com/agent/pb/classic.html for details).
6. That will bring up the binding dialog and this will allow you to find the project in the repository and it will bind that workspace to that project.
7. With the workspace bound you can now start using the source control menus found in PB.

More details on what binding means can be found here: http://www.zeusedit.com/agent/com/binding.html

The test above should give you a feel for how Agent SVN actually works

And another newbie question: Do we always have to edit AgentSVN's configuration if we want to switch to another PB workspace bound to a different repository?

No.

The repository found in the configuration dialog is the default repository.

So let's imagine you have a new PB workspace.

When that workspace is added to SVN it will get added to whatever is the current default repository found in the configuration dialog.

But once it has been added, that workspace will remain bound to exact same repository even if configuration dialog repository is changed.

Cheers Jussi

PS: These two topics are also worth a read:

Powerbuilder Slowness
http://www.zeusedit.com/zforum/viewtopic.php?t=7167

Powerbuilder 12.5 - Client Library Error
http://www.zeusedit.com/zforum/viewtopic.php?t=7187

[jeff]

Hi Jussij and thanks somuch for this elaborated answer!

I followed your instructions for one of my projects:

As a test I would do the following:

1. Backup the local working copy of that project. That backup will retain your current PushOK bindings.
2. Inside PB open that workspace and in the workspace properties remove the source control bindings. So now the workspace is no longer bound to source control.
3. Make sure that the Agent SVN configuration dialog is pointing to the repository of that PB project.
4. Now restart PB and in the workspace properties select Agent SVN as the source control provider.
5. Leave the project name blank and click on the ... button (see http://www.zeusedit.com/agent/pb/classic.html for details).
6. That will bring up the binding dialog and this will allow you to find the project in the repository and it will bind that workspace to that project.
7. With the workspace bound you can now start using the source control menus found in PB.

Successful so far - to me the binding appears correct - but all menu items relevant for source control are greyed out after connecting to the repository. Maybe if I send you the log you've got an idea what is wrong? Could I send that log to some private address please?

Thanks in advance!

[jussij]

Could I send that log to some private address please?

Just use the e-mail in the bottom left of this screen.

Also send a screen grab of the project workspace properties.

Cheers Jussi