Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

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 ?

0 votes


Accepted answer

Permanent link

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

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 1,202
× 562
× 151

Question asked: Oct 01 '19, 2:40 a.m.

Question was seen: 2,064 times

Last updated: Oct 01 '19, 2:43 a.m.

Confirmation Cancel Confirm