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

Resolved Migrate by command line

  1. How-to
0
Votes
Undo
  1. Giuseppe moglia
    Giuseppe moglia
  2. PowerBuilder
  3. Saturday, 3 October 2020 09:26 AM UTC

Hi Guys

we want to migrate from PB 2017 to 2019

We have set up a CI sstem with Jenkins and we need to mantain PB2017 for some months

So it would be nice to work with PB2017 and commit to SVN and to set up anoher workspace in jenkins to compile with PB2019, but to do so I need to migrate my code

Is there any trick or command line tool to migrate during the Jenkins Pipeline before to compile?

Thanks a lot

  1. PowerBuilder (Appeon)
Paste into singleline edit
PowerBuilder 12.6
Responses (2)
mike S
mike S Accepted Answer Pending Moderation
  1. Saturday, 3 October 2020 14:43 PM UTC
  2. PowerBuilder
  3. # 1

if you just want to compile in any later version than the one you are developing in, you just have to load your source code in and compile.

 

in any case, it is good practice in builds to delete all pbls and recreate them empty.  then load in your source code, then build.  that all can be done via  scripts and/or build tool such as powergen.  if you do that, then you simply change the PB version that is doing the load and build.    

We currently are using the 2017R3 IDE and our real production build for our last 2017 version is being done in that.  At the same time we are building the same source code in 2019R2 and well as 2019R3 Beta.

 

Comment
There are no comments made yet.
Giuseppe moglia
Giuseppe moglia Accepted Answer Pending Moderation
  1. Saturday, 3 October 2020 14:51 PM UTC
  2. PowerBuilder
  3. # 2

Thank you Mike

I figured you use orca scripts, could you share an example please?

Thanks

Comment
mike S
  1. mike S
  2. Saturday, 3 October 2020 15:00 PM UTC
this is a list of commands. Your script will need to be written by you.

https://docs.appeon.com/pb2019/pbug/apbs02.html



this is an example of loading source into my empty pbls. you may or may not need 3pass for your loads, depends on your requirements



start session

scc set connect property provider "WizSource"

scc set connect property userid "loginname"



scc set connect property project "projectname"

scc set connect property localprojpath "c:\build"



scc connect

scc set target "mybuild.pbt" "refresh_all"

scc refresh target full



scc close







end session
  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.