Jump around, Jump around. No maps this time, but Continuous Integration. My current work involves a lot of a software piece called Jenkins. I’ve been swimming with it the last 2 months and I feel compelled to share how we changed our ways.
This post is an overview guide on how to configure Jenkins to generate the jobs that are defined in a git repo.
This one is going to be short, it is something that would fit better under commandlinefu, tips and tricks!
Look for al the cpp files under a directory and modify all the text with foo to bar.
First we find all the cpp files under the current directory
find . -name "*.cpp" -print
And a possible command to replace from a file is using sed.
sed -i 's/foo/bar/g'
We just have to connect those two together to replace in all the files with a name ending in .cpp, that’s what pipes are for.
find . -name "*.cpp" -print | xargs sed -i 's/foo/bar/g'
Ta-Dah
Castells 