Problem with deployment of update package on IBM i
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
Hi, Hi Michael, The think the update package must be created in the same directory as the full, for the deployment to work. It must be clever enough to decide what is full and what is an update by the property you set. Regards James |
Hi, Hi Michael, The think the update package must be created in the same directory as the full, for the deployment to work. It must be clever enough to decide what is full and what is an update by the property you set. Regards James Hi, thanx for the response. But which directory do you mean? I am not aware that I changed any directory. Thanx Mihael |
|
Hi,
How many package definitions do you have? How many deployment definitions? Are you able to upload images? I understand that you may not be able to due the nature of the builds. James |
Hi, Hi, I have one package definition for a complete package and one for an update package. The same goes for the deployment. So I got 2 definitions for each (packaging and deployment). The deployment is local on the same machine into another library (specified in the mapping file). What additional info do you need? Mihael |
Hi, Hi, I have one package definition for a complete package and one for an update package. The same goes for the deployment. So I got 2 definitions for each (packaging and deployment). The deployment is local on the same machine into another library (specified in the mapping file). What additional info do you need? Mihael Hi, Inside the package definition do you output the same IFS dir? I have a feeling they do not and they have a feeling they need to. James |
|
Hi,
I don't know exactly what directory/entry you mean. I have always these for every definition: team.deploy.common.localPackageRoot.dir : /QOpenSys/usr/local/rtc/load team.deploy.common.remotePackageRoot.dir : /QOpenSys/usr/local/rtc/packages team.package.common.packageRoot.dir : /QOpenSys/usr/local/rtc/packages It seems that he can't find the package to be deployed. But where should it be? Mihael |
Hi, 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 |
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 |
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 |
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.