[#QB-482] Migrate quickbuild from 1.2.13 to 2.0.11

QuickBuild

Migrate quickbuild from 1.2.13 to 2.0.11

Created: 15/Dec/09 04:01 AM Updated: 15/Dec/09 10:56 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
File Attachments:	1. migrate-log.html (1.58 Mb)
Environment:	« Hide OS : CentOS release 5.3 (Final) Quickbuild upgrade version : 2.0.11 Show » OS : CentOS release 5.3 (Final) Quickbuild upgrade version : 2.0.11

Description

« Hide

Hi Robin,

I am upgrading QuickBuild from 1.2.13 to 2.0.11

I would like you to have a look at the migration log to suggest any correction/improvement in the upgrade procedure as Quickbuild has been the build environment in production here for around 4 years.

The migration from 1.x to 2.x is a critical activity and any loss of data cannot be compromised, so I request you to kindly provide your suggestions/inputs on the data that has not been imported.

Also, I have received an error :

2009-12-14 05:51:41,904 ERROR - Error running scheduled configuration 'root/TestCopyConf/CopyConfTest_Continuous_build'.
jvm 1 | com.pmease.quickbuild.QuickbuildException: Number of configurations exceeds community license limit.
jvm 1 | at com.pmease.quickbuild.DefaultBuildEngine.ensureLicensed(DefaultBuildEngine.java:306)
jvm 1 | at com.pmease.quickbuild.DefaultBuildEngine.access$8(DefaultBuildEngine.java:288)
jvm 1 | at com.pmease.quickbuild.DefaultBuildEngine$4.execute(DefaultBuildEngine.java:996)
jvm 1 | at com.pmease.quickbuild.taskschedule.DefaultTaskScheduler$HelperTask.execute(DefaultTaskScheduler.java:89)
jvm 1 | at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

So, kindly provide the required license key for the server at [email protected]. I am upgrading this on a test machine, once its successful, then I'll migrate it on a UAT environment and then on the production server.

Hoping for your kind cooperation in this activity.

Regards,
Amit

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robin Shen [15/Dec/09 10:56 AM]

Since 2.0 changed a lot from 1.0, and expressions are not compatible any more. Most entries in the migration log states that various expressions and scripts defined are not migratable, and should be changed manually to conform to 2.0 format. We are very sorry that this means a lot of work for your migration, and we've thought of scripting API in 2.0 carefully and it will be compatible with future versions onward.

To reduce the migration overhead to some extendt you may recognize common expression patterns in QuickBuild 1.x backup.xml, and substitute them with 2.0 equivalent globally, for example, the variable reference var["some var name"] has below equivalent in 2.0:
vars.get("some var name")

[ Permlink | « Hide ]

Amit Pandey [15/Dec/09 04:21 AM]

Kindly have a look at the migration log for more details on issues in migration.

Regards,
Amit