Riverside-Software / pct

Build automation for OpenEdge ABL
Apache License 2.0
96 stars 62 forks source link

St file is not created properly #428

Closed shireeshkumarn closed 4 years ago

shireeshkumarn commented 4 years ago

We have currently moving to progress 12.2. When i am executing the command create DB this error been thown. When i have seen what the problem in .e, i came accross the st file is created with basic but not from the server.

[Step 1/1] create.db (28s)
[11:53:39][create.db] PCTCreateBase (28s)
[11:53:39][PCTCreateBase] Copying empty DB to lab
[11:53:39][PCTCreateBase] Working with PCT source code, either because you asked for it or because the compiled version is missing in JAR file
[11:53:55][PCTCreateBase] Loading D:\TeamCity_build\tmp\devSchema12\lab.df in database
[11:54:07][PCTCreateBase] 10217 errors and 0 warnings during load
[11:54:07][PCTCreateBase] Log file can be found in D:\TeamCity_build\workspaces\DevRsd12AutomatedBuild\scripts\TeamCity\lab.e.19102020.42847.12513
[11:54:08][PCTCreateBase] Return code : 1
gquerret commented 4 years ago
[11:53:39][PCTCreateBase] Working with PCT source code, either because you asked for it or because the compiled version is missing in JAR file

You're either using an old version of PCT which doesn't have support for v12, or a custom version. In any case, please reproduce the problem with v215.

shireeshkumarn commented 4 years ago

Yes they have made a custom changes, I have seen they are using the older version(192 or 184) of the build. If you could share this builds of v192 & v184 will be helpful to investegate the custom changes they have done previosly.

gquerret commented 4 years ago

I'm afraid those builds are not available anymore. You may ask on https://community.progress.com, maybe somebody is still using those versions. As those versions were released before the Git migration, they are not properly tagged. But v184 was released on December 17th, 2013, so that should be commit ID 847db1a139bbdcdaf7fe07ce9ba1c547a6ec4345. Finding commit ID for v192 is left as an exercise for the reader 😄

stefandrissen commented 4 years ago

I have a pct-192.jar in our source control which I can share if needed.

shireeshkumarn commented 4 years ago
[11:53:39][PCTCreateBase] Working with PCT source code, either because you asked for it or because the compiled version is missing in JAR file

You're either using an old version of PCT which doesn't have support for v12, or a custom version. In any case, please reproduce the problem with v215.

[Ant output] Buildfile: D:\TeamCity_build\workspaces\DevRsd121AutomatedBuild\scripts\TeamCity\build.xml [14:39:37][Ant output] [14:39:37][Ant output] dump.df: [14:39:37][Ant output] [PCTDumpSchema] Dumping schema to D:\TeamCity_build\tmp\devSchema12\lab.df [14:39:37][Ant output] [PCTDumpSchema] The dump file will not contain any buffer pool definitions for the objects. [14:39:37][Ant output] [PCTDumpSchema] You must be a Security Administrator to maintain object attributes. [14:39:37][Ant output] [14:39:37][Ant output] create.db: [14:39:37][Ant output] [PCTCreateBase] Copying empty DB to lab [14:39:37][Ant output] [PCTCreateBase] ** "pct/v11/loadSch.p" was not found. (293) [14:39:37][Ant output] [14:39:37][Ant output] BUILD FAILED [14:39:37][Ant output] D:\TeamCity_build\workspaces\DevRsd121AutomatedBuild\scripts\TeamCity\build.xml:198: Progress procedure failed - No output file [14:39:37][Ant output] [14:39:37][Ant output] Total time: 5 seconds

I can see the file loadSch.p is in directory "pct/v11"

Currently it is using 12.0 version of progress why this is pointing to v11 dir ? Is there any way to debug - Very new to this, want to rectify the problems ASAP.

shireeshkumarn commented 4 years ago

I have a pct-192.jar in our source control which I can share if needed.

shireeshkumarn commented 4 years ago

I have a pct-192.jar in our source control which I can share if needed.

Thanks. I have this jar file, on the basis of jar file, i could find the pct version.

gquerret commented 4 years ago

Please add <PCVersion /> in your build script before your DumpSchema task. That will display the current version number. But if you're using PCT v192, don't expect it to work with OE12.

shireeshkumarn commented 4 years ago

Please add <PCVersion /> in your build script before your DumpSchema task. That will display the current version number. But if you're using PCT v192, don't expect it to work with OE12.

Sure will add PCVersion, i have updated the scripts to v215, so i could see this errors.

shireeshkumarn commented 4 years ago

Please add <PCVersion /> in your build script before your DumpSchema task. That will display the current version number. But if you're using PCT v192, don't expect it to work with OE12.

Sure will add PCVersion, i have updated the scripts to v215, so i could see this errors.

@gquerret

[Ant output] Buildfile: D:\TeamCity_build\workspaces\DevRsd121AutomatedBuild\scripts\TeamCity\build.xml
[15:47:24][Ant output] [PCTVersion] PCT Version 1.1-pre - Build 192
[15:47:24][Ant output]      [echo] 12.2
gquerret commented 4 years ago

So you're still using version 192, and not v215. Make sure you only have a single PCT.jar in $ANT_HOME/lib ; or check the -lib parameter of your command line. That depends on how you've installed PCT. See https://github.com/Riverside-Software/pct/wiki/InstallDocumentation

shireeshkumarn commented 4 years ago

Yes corrected accordingly. Working as expected.