Gitlab CI/CD using FTP for .NET Core



我正在尝试自动生成,测试和部署我的.NET Core应用程序,到目前为止,它会构建和测试,但不会部署。Gitlab 管道显示作业成功,但实际上并没有工作。这是我的 Dockerfile:

FROM microsoft/dotnet:2.2-sdk AS build-env
WORKDIR /source
RUN curl -sL https://deb.nodesource.com/setup_11.x |  bash - 
    && apt-get install -y nodejs

COPY ./src/*.csproj .
RUN dotnet restore
COPY ./src/ ./
RUN dotnet publish "./Spa.csproj" --output "./dist" --configuration Release --no-restore
FROM microsoft/dotnet:2.2-aspnetcore-runtime
WORKDIR /app
COPY --from=build-env /source/dist .
RUN apt-get update 
    && apt-get install -y php-cli
COPY deployment.ini /app
EXPOSE 80
ENTRYPOINT ["dotnet", "Spa.dll"]

这就是我的.gitlab-ci.yml文件的样子:

# ### Define variables
#
variables:
 OBJECTS_DIRECTORY: 'obj'    
 NUGET_PACKAGES_DIRECTORY: '.nuget'
 SOURCE_CODE_PATH: 'src/'             
# ### Define stage list
stages:
 - build
 - test
 - deploy
cache:
 # Per-stage and per-branch caching.
  key: "$CI_JOB_STAGE-$CI_COMMIT_REF_SLUG" 
  paths:
    - '$SOURCE_CODE_PATH$OBJECTS_DIRECTORY/project.assets.json'
    - '$SOURCE_CODE_PATH$OBJECTS_DIRECTORY/*.csproj.nuget.*'
    - '$NUGET_PACKAGES_DIRECTORY'
    - '**/node_modules/'
build:
  image: docker:stable
  stage: build
  services:
    - docker:dind
  before_script:
    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
  script:
    - docker build -t registry.gitlab.com/chinloyal/spa .
    - docker push  registry.gitlab.com/chinloyal/spa
tests:
  image: microsoft/dotnet:2.2-sdk
  stage: test
  before_script:
    - curl -sL https://deb.nodesource.com/setup_11.x |  bash -
    - apt-get install -y nodejs
  script:
    - dotnet test --no-restore Tests/
deploy:
  image: docker:stable
  services:
    - docker:dind
  stage: deploy
  before_script:
    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
    - docker pull registry.gitlab.com/chinloyal/spa
    - docker run --name spa -p 80:80 -d registry.gitlab.com/chinloyal/spa
  script:
    - docker exec -d spa curl -S "https://gitlab.com/chinloyal/ftp-deploy-tool/raw/master/deployment.phar" --output deployment.phar
    - docker exec -d spa bash -c "echo remote = $FTP_HOST >> deployment.ini"
    - docker exec -d spa bash -c "echo user = $FTP_USER >> deployment.ini"
    - docker exec -d spa bash -c "echo password = $FTP_PASSWORD >> deployment.ini"
    - docker exec -d spa php deployment.phar deployment.ini
  environment:
    name: production
  only:
    - master

此行docker exec -d spa php deployment.phar deployment.ini是假定从 docker 容器内部上传文件的行。但我相信这是因为 Gitlab 在该行之后立即结束了该过程。然后容器内的进程就结束了。

我尝试使用注册表映像(registry.gitlab.com/chinloyal/spa(作为部署映像,但是每次尝试使用它时,它都会开始在Gitlab上运行项目,直到超时或取消为止。

顺便说一下,我只能通过ftp访问服务器,因为它是共享服务器。我用来部署的 ftp 工具在这里。我以前试过,所以我知道它有效。

我想通了,所有docker exec命令都使用-d标志,所以我删除了-d标志,以便 gitlab 显示正在下载和上传的文件的输出。 所以我把这个docker exec -d spa curl -S "https://gitlab.com/chinloyal/ftp-deploy-tool/raw/master/deployment.phar" --output deployment.phar改成docker exec spa curl -S "https://gitlab.com/chinloyal/ftp-deploy-tool/raw/master/deployment.phar" --output deployment.phar

我也把docker exec -d spa php deployment.phar deployment.ini改成了docker exec spa php deployment.phar deployment.ini.

因此,在它们以分离模式运行之前,由于 gitlab 认为他们已经完成了并继续下一个命令,删除 -d 标志让 gitlab 等待。

最新更新