buildableFiles.xml not filled
Hi all,
we are using RTCz 2.* and do our first tests with the build engine on z/OS. We created language definition, translators and dataset definitions. We also assigned the language definition to the zFiles and the dataset definitions to the zFolders, but when we request a build, the generated file "buildableFiles.xml" does'nt contain any of our Cobol files in the zFolder. Therefore the build ends successfully but did not build any file. Any ideas what is wrong or missing?
bkrgr1
we are using RTCz 2.* and do our first tests with the build engine on z/OS. We created language definition, translators and dataset definitions. We also assigned the language definition to the zFiles and the dataset definitions to the zFolders, but when we request a build, the generated file "buildableFiles.xml" does'nt contain any of our Cobol files in the zFolder. Therefore the build ends successfully but did not build any file. Any ideas what is wrong or missing?
bkrgr1
6 answers
Have you created the project as the zComponent project?
Tami
Thank you! Yes, we created a zComponent project with zFolders and zFiles. Our mistake was an invalid element handling in the repository. They were not correctly accepted.
bkrgr1
Could you give some more details on what you mean by 'an invalid element handling in the repository'. I'd like to understand exactly what the issue was as we are always looking out for common mistakes people make.... We may be able to protect people from them in the tooling or at least document it.
Guy
Have you created the project as the zComponent project?
Tami
Thank you! Yes, we created a zComponent project with zFolders and zFiles. Our mistake was an invalid element handling in the repository. They were not correctly accepted.
bkrgr1
Could you give some more details on what you mean by 'an invalid element handling in the repository'. I'd like to understand exactly what the issue was as we are always looking out for common mistakes people make.... We may be able to protect people from them in the tooling or at least document it.
Guy
Hallo Guy,
there sems to be a problem with our stream or workspace definitions. We defined the zFolder, assigned it to a private workspace in the repository and defined a flow to a stream in the project area. We checked in our changes to the private workspace and delivered them to the stream. When we request 'show repository files' we can see the files in the stream. but when we request a build for that stream, it does not select the files. When we request the build for the private workspace, it works correctly. How can we enable the artifacts in the stream to be selected by the build proess?
It could be an issue with read permissions due to the use of a private workspace.
Is this workspace a developer workspace, or is it configured as the build workspace (in the build definition)? Also, what user owns the build workspace, and is it the same as the user given on the JBE command line? If not using JBE for this build, what user do you have configured as the 'run as' user in the server's Advanced Properties section for the Build Agent?
Is this workspace a developer workspace, or is it configured as the build workspace (in the build definition)? Also, what user owns the build workspace, and is it the same as the user given on the JBE command line? If not using JBE for this build, what user do you have configured as the 'run as' user in the server's Advanced Properties section for the Build Agent?