Post

20170627

20170627

gitlab CI

resolved

1.gitlab CI

tools

1
`gitlab-ci-runner`,`msbuild`,`nuget`

install and register runner win

  1. download git-lab runner
  2. mkdir to save runer exe
  3. register to gitlab
  4. install gitlab-runner windows service
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    
    ./gitlab.exe register
    # Please enter the gitlab-ci coordinator URL (e.g. https://gitlab.com )
    # https://gitlab.com
    # Please enter the gitlab-ci token for this runner
    # Please enter the gitlab-ci description for this runner
    # [hostame] my-runner
    # Please enter the gitlab-ci tags for this runner (comma separated):
    # my-tag,another-tag
    # Whether to run untagged jobs [true/false]:
    # [false]: true
    ./gitlab.exe install
    

nuget install and restore packages

1
c:\nuget\nuget.exe restore "build\cts.sln"

msbuild build solution

  1. download msbuild standalone package
  2. use msbuild build solution
1
2
#2333
&'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe' /consoleloggerparameters:ErrorsOnly /maxcpucount /nologo /property:Configuration=Release /verbosity:quiet "build\QingdaoBeer.CTS.sln"

pending

1.nuget

2.git commit rules

  1. buid pass

reference

  1. GitLab CI持续集成配置方案
  2. 劈荆斩棘:Gitlab 部署 CI 持续集成
  3. Install on Windows
  4. Setting up a PowerShell CI Pipeline using Gitlab
  5. PowerShell中运行带空格的命令
  6. NuGet CLI reference
  7. How can I install the VS2017 version of msbuild on a build server without installing the IDE?
This post is licensed under CC BY 4.0 by the author.