WinRT App CI on Jenkins(VS2013)
* Need install vs env on Win Server 2012
* MSTest not support Store App
* Need change Jenkins startup/logon account so that it can read code sign cert from cert store
****************************
So you need to setup continuous integration using Jenkins to drive Visual Studio 2013, eh? Unit Testing, too? No problem.
This system, by far, has proven to be the easiest to understand among all of the Continuous Integration options explored so far (TeamCity, Bamboo).
Proof of concept build:
- Setup a virtual machine, loading the TurnKeyLinux Jenkins appliance.
- Go to, and log in to the new Jenkins machine.
- Manage Jenkins -> Manage Plugins -> Available / Installed
- Acquire the following plugins, and have them enabled:
- Git Plugin
- Git Client Plugin
- BitBucket Plugin (because I was using BitBucket)
- MSBuild Plugin ( compiler )
- VSTest Runner Plugin ( unit tests - Microsoft's standard issue system )
- NUnit Plugin ( unit tests - Popular pseudo standard issue system )
- MSBuild
- Click "MS Build installations..."
- Click "Add MSBuild"
- Name: ".NET 4.0"
- Path to MSBuild: "C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"
- Click "Add MSBuild"
- Name: ".NET 3.5"
- Path to MSBuild: "C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild.exe"
- Repeat as needed for other versions
- Click "VSTest installations..."
- Click "Add VSTest"
- Name: "VSTest Console"
- Path to VSTest: "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe"
- Provide a name
- Root Directory: "C:\" (quotes not needed)
- Launch Method: "Launch slave agents via Java Web Start" (this is the easiest option)
- Save
- Provide a name
- Build a free-style software project
- (optionally) Restrict where this project can be run ( provide the name of a "slave" / "agent" )
- Source Code Management: "Git"
- Provide URL
- Provide Credentials (password is acceptable when you fully control the machine, SSH key is best in shared-with-team development mode)
- Add Build Step ( compile - required )
- "Build a Visual Studio project or solution using MSBuild"
- Provide Build File ( a ".sln" is a good choice )
- "Build a Visual Studio project or solution using MSBuild"
- Add Build Step ( for Visual Studio's default test system - optional )
- "Run unit tests with VSTest.console"
- Provide the names of the DLLs produced (ex: Bank.Test.dll)
- "Run unit tests with VSTest.console"
- Add Build Step ( for NUnit - optional )
- "Execute Windows batch command"
- "C:\Program Files (x86)\NUnit 2.6.3\bin\nunit-console.exe" BankNTest/bin/Debug/BankNTest.dll /xml=NTestResults/nunit-result--%BUILD_NUMBER%--%BUILD_ID%.xml
- "Execute Windows batch command"
At this point, Jenkins should remotely launch builds and tests whenever you make a push to your git repository. The above steps did not setup any "build triggers", because, my currently functional Jenkins project does not have any build triggers yet still works.
相关推荐
synshitou 2020-10-21
pursuemylife 2020-08-14
达观数据 2020-11-11
汪康 2020-10-30
ppppfly 2020-10-24
programmeryu 2020-09-24
Topbeyond 2020-08-21
lrcoop 2020-08-18
young依然 2020-08-17
oden 2020-08-16
lrcoop 2020-08-15
yserver 2020-08-15
王永迪 2020-08-15
pandaphinex 2020-08-09
leonranri 2020-07-26
CloasGao 2020-07-21
zccheu 2020-07-18