Code checkout from RTC using Jenkins do not contain file extension affecting builds using external application
We have an external application where we code using Cobol which is integrated with RTC. We check-in the code to RTC. However, on check-out we see that the files checked-out do not have any extension. In Jenkins we have configured an external tool for build which expects file with .cbl extension. Hence the builds are not functioning.
What could be the reason ?
|
Accepted answer
|
RTC do not modify or edit the file extension. The files are presented as is in the repository. If the file was checked-in with the appropriate extension, the same would be seen on check-out.
This issue was related to the external application used to write cobol code where a property mapping was missing. We had to add a property mapping to map .cbl extension in the application before check-in.
After mapping the property and checking-in the code to RTC, the check-out now contains the file extension which resolved the issue with build.
Ralph Schoon selected this answer as the correct answer
|
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.