It's all about the answers!

Ask a question

Problem with deployment of update package on IBM i


Mihael Schmidt (5154) | asked Mar 15 '11, 4:55 a.m.
Hi,

I have successfully created a complete package and installed it (which seems to be a requirement for an update package). The packaging of an update package also successfully finished. The save file is in subfolder of the package directory (/OpenSys/usr/local/rtc/packages).

But now the job for the deployment of the update package fails:

BUILD FAILED
/QIBM/ProdData/RTC/V3.0/Build/jazz/buildsystem/buildtoolkit/scripts/enterprise/deploy.xml:188: No complete package found in remote package root directory that matches timestamp -1 of last loaded complete package.

build.log:
http://pastebin.com/SBRtWA9c

file system structure:
http://imagebin.org/143093

I have no idea why?

Any ideas or hints?

Thanx in advance

Mihael

14 answers



permanent link
James Cole (9532630) | answered Mar 16 '11, 10:17 a.m.


Hi,

Below is a link to relating to creating packages and deployment.

https://jazz.net/wiki/bin/view/Main/RTCpHome

Hope this helps.

James


The Troubleshooting Guide was of some help. It seems one have to make a complete package with the same version number which was not clear to me. The normal way for me would be to make a complete build for a release (1.0.0) and because of a bug fix with only one program involved I would create an update package (1.0.1). It would never come to my mind to create a complete package for 1.0.1 and then make an update package which seems what needs to be done to work. Is this correct?

Mihael

Hi,

That is my understanding of how RTC 3.0 works. So the first time you ever create a new version/sub version there must be a complete package before a part release.

Glad the link was of help.

James

Does this "bugfix complete package" version 1.0.1 needs to be installed prior to the update package version 1.0.1 or can that be skipped as all objects should be installed with any previous version? I just want to update one or more objects.

Mihael

I'm not sure so don't quote me please!!!. I think it deploys them in the order you create them.

So if you create 3 update packages (in the same directory) and then do a deployment, it will require 3 deployments to get to the latest release.

Please let me know if this is wrong.

James

permanent link
Mihael Schmidt (5154) | answered Mar 17 '11, 4:34 a.m.

I'm not sure so don't quote me please!!!. I think it deploys them in the order you create them.

So if you create 3 update packages (in the same directory) and then do a deployment, it will require 3 deployments to get to the latest release.

Please let me know if this is wrong.

James


I think you are correct about this. But it seems that even the order of creation and deployment seems to matter somehow. I created a new topic:

http://jazz.net/forums/viewtopic.php?p=52821#52821

Mihael

permanent link
Mihael Schmidt (5154) | answered Mar 17 '11, 4:36 a.m.

I'm not sure so don't quote me please!!!. I think it deploys them in the order you create them.

So if you create 3 update packages (in the same directory) and then do a deployment, it will require 3 deployments to get to the latest release.

Please let me know if this is wrong.

James


I think you are correct about this. But it seems that even the order of creation and deployment seems to matter somehow. I created a new topic:

http://jazz.net/forums/viewtopic.php?p=52821#52821

Mihael

permanent link
James Cole (9532630) | answered Mar 17 '11, 6:31 a.m.

I'm not sure so don't quote me please!!!. I think it deploys them in the order you create them.

So if you create 3 update packages (in the same directory) and then do a deployment, it will require 3 deployments to get to the latest release.

Please let me know if this is wrong.

James


I think you are correct about this. But it seems that even the order of creation and deployment seems to matter somehow. I created a new topic:

http://jazz.net/forums/viewtopic.php?p=52821#52821

Mihael

OK. Thanks for the link

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.