jenkins 截取字符串_Jenkins shell字符串引用替换

最新推荐文章于 2024-04-28 10:48:46 发布

樊兆强

最新推荐文章于 2024-04-28 10:48:46 发布

阅读量663

点赞数

文章标签： jenkins 截取字符串

本文链接：https://blog.csdn.net/weixin_33331021/article/details/112807681

版权

在 Jenkins 的 Execute Shell 脚本中使用 Bash，遇到字符串包含转义换行符（）的问题，导致双引号被替换为单引号，从而无法正确解析换行。解决办法是在 git commit 命令中使用反引号包裹 printf 命令来保留多行字符串，例如：`printf"多行内容"`。这将在 Jenkins 的 Shell 步骤中正常工作，保持换行效果。

摘要由CSDN通过智能技术生成

I have a Jenkins job with an execute shell box. In the execute shell I use bash instead of dash (sh). In the execute shell I have strings which are supposed to be interpreted as they contain escape sequences (in this case the new line: \n), so here is an example execute shell:

#!/bin/bash

set -x #echo on

git fetch

...

git commit -m "Merging $DEVELOPEMENTBRANCH into $INITIALBRANCH\n\nThis is an example second paragraph."

...

My problem here is that the script block is interpreted/replaced by Jenkins in a way that it changes its behavior, to be specific it replaces the variables and replaces the double quotes with single quotes so in the console output it looks like this:

[4] $ /bin/bash /tmp/hudson7542128982632971668.sh

+ git fetch

...

+ git commit -m 'Merging my_feature into develop\n\nThis is an example second paragraph'

...

But in this way the \n part won't be interpreted because of the single quotes. What is the trick here? I want to preserve the double quotes or at least interpret the \n sequences.

解决方案

git commit -m "A multi-line\n\ncommit message" will not produce a multi-line

commit message anyway. The commit message will be, literally, A multi-line\n\ncommit message.

Double-quotes do not cause bash to interpret printf escape-sequences.

To get a multi-line commit-message you need:

git commit -m "`printf \"A multi-line\n\ncommit message\"`"

This works fine in a Jenkins shell step.