Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Batch adding Workspaces to SVN

  1. How-to
0
Votes
Undo
  1. yakov werde
    yakov werde
  2. PowerBuilder
  3. Thursday, 2 April 2020 16:48 PM UTC

Hello

We are migrating our trunk code from TFS (VCS, MSSCCI) to SVN. [We don't put the 1.5 gig of PBLs in SVN (total waste of space and effort) as the tool leads you to think you must do.  It works just fine without PBLs.  Branching works fine too.

When adding a workspace, there is a major manual effort to unselect / select all the proper files under the workspace to go into ws_objects.

We have 100+ applications which are based on a 15 PBL common PBD framework code set.

Must each application be manually added to source control?   (big manual effort) 

or 

Is there a way to automate the process?

Thanks for your thoughts

Yakov Werde

Dev Ops & Sr Developer

Openlink Financial

  1. SVN
Sending an email
What/Who is the PowerBuilder Catalog Owner?
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 2 April 2020 19:26 PM UTC
  2. PowerBuilder
  3. # 1

Hi Yakov;

  For the older SSCAPI you could use the ORCA API (not ORCAScript) - however, I suspect that ORCA has not been updated to handle the newer SCM options. So my guess answer for now is no - just manually via the IDE.

  BTW: Why the switch to SVN from TFS?

Regards ... Chris

Comment
yakov werde
  1. yakov werde
  2. Tuesday, 7 April 2020 18:20 PM UTC
This confirmation from 2019R2 help doc *** e



You can use "scc connect offline" to compile the source code managed by the SVN/Git source control system in PowerBuilder 2019 R2; while ***you cannot use "scc connect" to connect with the SVN/Git server or get the source code from the server. Therefore, the following OrcaScript source control commands do not work with the SVN/Git solution in 2019 R2: ****



scc connect

scc get connect properties workspaceName

scc get latest version file_list [file_list ...]

The commands related with connecting to the server such as "scc set connect property userid userID", "scc set connect property password password" etc. will be simply ignored.



  1. Helpful
There are no comments made yet.
yakov werde
yakov werde Accepted Answer Pending Moderation
  1. Thursday, 2 April 2020 21:15 PM UTC
  2. PowerBuilder
  3. # 2

Thanks Chris,  Not the answer I wanted to hear.  But I hear it.  It will be a long drive (are we there yet....)

We are moving away from TFS for several reasons

1) No more support for MSSCCI - 2015 was the last release.  it's legacy technology

2) Management chose to unify on a single repository host.  The .NET side of our house (which now dominates) is SVN based.

3) .NET builds are Jenkins based and pull from SVN.  We will be moving our custom PB build suite under Jenkins control and have a unified build process

Any idea if there are plans to update ORCA for use with SVN/GIT?

Yakov

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 2 April 2020 21:23 PM UTC
Hi Yakov;

Thanks for the feedback on your SCM journey.

I have not heard about any planned ORCA API enhancements.

Regards ... Chris

  1. Helpful
Noel Hibbard
  1. Noel Hibbard
  2. Tuesday, 21 April 2020 20:16 PM UTC
If you migrate to git you can script the build process with something similar to this:

git fetch --all

git reset --hard origin/master



That will pull the most resent source and completely wipe out anything left over from a previous build process. Then simply call an orca script that will build PBLs from scratch using the loose source files that you just pulled with git. Here is a sample orca script that would do that:

https://pastebin.com/d5WbSJWw



You would run this with the working directory set to the root of your git repo.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.