Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

The SeaLights dotnet agent can be integrated with MSBuild to scan the binary code and provide the SeaLights server the build information.

Generating a session ID

Before running the build scan and tests, you need to create a session ID. The session ID is provided to each step in order link them together as one complete cycle

Sample command
SL.DotNet.exe config --tokenFile C:\path\to\sltoken.txt --appName "myApp" --branchName "master" --buildName "1" --includeNamespace myNameSpace [--excludeNamespace <arg>] [--include <arg>] [--exclude <arg>] [--buildSessionId <arg> | --buildSessionIdFile <arg>] [--proxy <arg>]


Automatic setup

TheSeaLights agent can automatically setup your msbuild to work with the SeaLights agent.

SL.DotNet.exe prepareForMsBuild --tokenFile C:\path\to\sltoken.txt --buildSessionIdFile buildSessionId.txt --workspacePath"C:\path\to\project" --logEnabled true

This creates a file called 'after.{SOLUTION_FILE_NAME}.targets' which sits alongside your solution file with all the needed parameters in it for.

Run MSbuild

When running MSBuild, it will identify the above file and cause our agent come up and report the details needed from the binary files.

Sample
Msbuild SlnFolders.sln /t:rebuild
  • No labels