How to check out a CVS repository in Windows with Unix line endings with Jenkins? -


i've got jenkins instance running on windows , 1 item, need check out cvs repository. is, built-in cvs plugin jenkins checking out windows crlf line endings. however, of needs done requires files have unix style lf line endings.

running dos2unix utility on entire repository seems painful safely , reliably.

i use cygwin's cvs running shell script build step, prefer better integrated jenkins.

so, short of writing script call external cvs, or fixing afterwards dos2unix, can jenkins check out cvs repository unix line endings on windows?

edit:

i've since come across this bug report indicating issue has been known since 2012 , not has been done it. i'll leave question open in case know of alternative i've mentioned.

i've added dos2unix steps pretty in build scripts windows (automake chain sensitive stuff), might seem bit ugly/fragile, it's ok think jenkins build : if breaks because of new files you'll build issues.

in experience, there couple of platform specific steps in build, bit of custom code support windows seems ok.

an alternative might tag files "binary" on cvs server (-kb flag) , make sure encoded correctly there, avoid transcoding @ checkout time, seems more intrusive me. haven't used sources, think might mess "diff" command.

a last idea might more precisely @ tools expecting lf style endings on win box, there might mingw or windows versions deploy support crlf.

my vote still goes dos2unix solution overall.


Comments

Popular posts from this blog

searchKeyword not working in AngularJS filter -

sequelize.js - Sequelize: sort by enum cases -

user interface - how to replace an ongoing process of image capture from another process call over the same ImageLabel in python's GUI TKinter -