• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Powerclient: Release planning with test and productive versions

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

Resolved Powerclient: Release planning with test and productive versions

  1. Advice
0
Votes
Undo
  1. Reto Stucki
    Reto Stucki
  2. PowerBuilder
  3. Thursday, 31 August 2023 06:17 AM UTC

Hello

Our procedure is as follows
We automatically create test versions on the build server. On day X, we copy the data of the released test version to the productive version. For this we only have to exchange the INI file with the connection parameters.
 
Now we want to automate the whole distribution with PowerClient or PBAutobuild.
In the PowerClient Json file the Appname = Application1Test. The PowerClient now creates an exe with the name Application1Test.exe.zip.
If we now make a test version into a productive version, we copy the directory on the web server and rename the directory
With the file CustomizeDeploy.dll we can exchange the INI file. But we cannot rename the exe. We don't want or are not allowed to start a build again just to change the app name.
 
How can we change the name of the exe from Application1Test to Application1?
 
How do you work with test and production versions in release planning?

 

Best regards

Reto

 

  1. Release
  2. PowerClient
Manage DB pwd for a PB app on a dev machine
Need background on Accessibility dlls/setting
Responses (4)
Reto Stucki
Reto Stucki Accepted Answer Pending Moderation
  1. Friday, 1 September 2023 08:21 AM UTC
  2. PowerBuilder
  3. # 1

@Chris

This is exactly how we work. Except that we only have a test and prod environment.
The last released test version must not be changed when it is ported to the production.

Regards Reto

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 1 September 2023 12:04 PM UTC
Hi Reto;

Thank you for your insight. Yes, the process can be the same but you can setup as many test environments between Dev & Prod as your organization requires. ;-)

Regards ... Chris
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 31 August 2023 10:09 AM UTC
  2. PowerBuilder
  3. # 2

Why not take away the need to rename the EXE in the first place?

Use the same name for test and production?

regards

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 31 August 2023 12:11 PM UTC
Hi Miguel;

What I've seen over my decades in IT, that's normally the way most IT shops use that technique. The development team does a production "candidate" build & does a quick "sanity" test on the App. From there, the production candidate is copied "as is" to the QA environment. The only change would be to a control file that allows the App to connect to the QA DB. If the App passes QA, then the production candidate App is copied "as is" from the QA environment to the Systems Integration test environment. Again, the only change there is the control file that directs the App to connect to an SI based DB. If the App passes SI testing, it's then copied to the User Acceptance test environment with the appropriate control file changes for DB connection in UA. Once the App passes UAT, it's copied into production. At NO time is the app ever recompiled as this could easily break its integrity. If the App fails to pass any these environments, it's sent back to development where it's fixed & recompiled as another production candidate & the cycle starts again over to QA.

There is no reason why PowerClient or PowerServer Apps should not follow the same SDLC IMHO. HTH

Regards... Chris
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Thursday, 31 August 2023 12:36 PM UTC
HI Chris,

Yes, I agree with all that, but since the exe is already in different folders, I don't see the need to name the executable differently or maybe I didn't fully understand they the OP works with this.

regards
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 1 September 2023 04:33 AM UTC
  2. PowerBuilder
  3. # 3

For security reasons, PowerClient limits what you can modified after the compile is done.  Just keep app name same and the folder can be renamed test so the URL would clearly differentiate the test from production version of the app.

 

Comment
There are no comments made yet.
Reto Stucki
Reto Stucki Accepted Answer Pending Moderation
  1. Friday, 1 September 2023 08:25 AM UTC
  2. PowerBuilder
  3. # 4

@Armeen

A different URL is our plan.
But the exe files have the same name in test and production. The shortcut on the desktop has also the same.
How should the user distinguish between the test and the production?

 

Regards

Reto

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 4 September 2023 05:20 AM UTC
Exactly as Miguel said.
  1. Helpful
Reto Stucki
  1. Reto Stucki
  2. Tuesday, 5 September 2023 12:39 PM UTC
@Armeen

It would be great if it were that simple. Unfortunately, the PowerClient creates the shortcuts and these cannot be changed. A solution would be to adapt the PowerClient project and start a build again. BUT, as already described, we are not allowed to start another build for a productive version, we have to use the last released test version.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 5 September 2023 15:18 PM UTC
The way you could do it without rebuilding is have the build shortcut configured for the production app/URL. For the test app/URL, you just create your own shortcut that points to the URL of the test app. It will pop up a browser and that can be a little annoying, but it is only test app for short period of time.
  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.