通过teamcity进行部署时记录卡纸

时间:2019-02-08 15:52:49

标签: java linux logging deployment teamcity

最近,我们从手动流程迁移到Teamcity部署。我们的是Linux服务器上的Java应用程序。 每当通过Teamcity进行部署时,日志都会卡住,即在关闭日志消息后,日志中不会再打印其他任何内容。然后,我们在服务器上运行手动停止和启动脚本,以使日志运行。 看起来Teamcity会以某种方式锁定日志文件并且不会释放它。

如何克服它?

在Teamcity中,部署步骤定义如下:

REMOTE_PATH="/opt/app/$ARTIFACT/releases/teamcity"

cd $TEAMCITY_REPO_HOME/$ARTIFACT/build/libs

echo "Uploading artifact"
ssh $UAT_HOST -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no "mkdir -p $REMOTE_PATH"
scp -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no $ARTIFACT.jar $UAT_HOST:$REMOTE_PATH

echo "Stopping service"
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no $UAT_HOST "sh /opt/app/$ARTIFACT/stop.sh"

sleep 3s

echo "Copying new artifact"
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no $UAT_HOST "cp $REMOTE_PATH/$ARTIFACT.jar /opt/app/$ARTIFACT"

sleep 6s

echo "Starting service"
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no $UAT_HOST "sh /opt/app/$ARTIFACT/start.sh"

1 个答案:

答案 0 :(得分:0)

根据安迪·杜弗雷斯(Andy Dufresne)的上述意见,我创建了一个部署脚本,如下所示: 这个单一脚本停止服务器,备份当前工件,复制新的内部版本,然后执行启动脚本以启动服务器。

#!/bin/bash
#check for correct number of arguments
if [ "$#" -ne 1 ]; then
    echo "Incorrect number of arguments, exiting..."
    exit 1
fi

ARTIFACT=$1

cd "/opt/app/$ARTIFACT"
echo $(pwd)

echo "Stopping service"
bash stop.sh

sleep 3s

echo "Tagging artifact with release"
cp "releases/teamcity/$ARTIFACT.jar" "releases/teamcity/$ARTIFACT`date +'_%y_%m_%d'`.jar"

echo "Deleting old releases"
cd "releases/teamcity" && \
ls | grep -v '/$' | head -n -6 | xargs -d '\n' -r rm -- && \
cd "/opt/app/$ARTIFACT" && \
ls -l "releases/teamcity"

echo "Copying new artifact"
cp "releases/teamcity/$ARTIFACT.jar" .

echo "Starting service"
bash start.sh

sleep 2s

此脚本在其构建步骤中从team-city调用(先前停止服务器,复制工件和启动服务器都是由teamcity明确完成的,如问题所述)。 现在,teamcity的构建步骤看起来很简洁,并且可以按预期工作(这很重要!!):

REMOTE_PATH="/opt/app/$ARTIFACT/releases/teamcity"

cd $TEAMCITY_REPO_HOME/$ARTIFACT/build/libs

echo "Uploading artifact"
ssh -o "StrictHostKeyChecking=no" "$UAT_HOST" "mkdir -p $REMOTE_PATH"
scp -o "StrictHostKeyChecking=no" "$ARTIFACT.jar" "$UAT_HOST:$REMOTE_PATH"

echo "Deploying artifact"
ssh -o "StrictHostKeyChecking=no" "$UAT_HOST" "sh /opt/app/$ARTIFACT/deploy.sh $ARTIFACT"