We have captured here some
Azure DevOps Pipeline for a DotNet application
$sldomain="m.sealights.co" $slagenttoken="$(AgentToken.Sandbox)" $APP_NAME="Calculator-CS" #Retrieve the same name of target branch as reported in Sealights Dashboard $PR_TARGET_BRANCH="$(System.PullRequest.TargetBranch)".Replace("refs/heads/","") #Retrieve the last Commit Hash from the PR branch and not the one from the ADO local Merge $PR_LAST_COMMIT=$(git log -2 --format=%H).Split(" ")[1] $PR_NUMBER="$(System.PullRequest.PullRequestId)" $REPO_URL="$(System.PullRequest.SourceRepositoryURI)" [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Write-Output "Retrieve DotNet agent version set in Sealights settings..." $agentversion = ((iwr -Uri https://$($sldomain)/api/v2/agents/dotnet/recommended -Headers @{'Accept' = 'application/json'; 'Authorization' = "Bearer $($slagenttoken)"}).Content | ConvertFrom-Json | Select-Object agent).agent.version Write-Output "Download Sealights DotNet agent..." iwr -OutFile sealights-dotnet-agent.zip -Uri http://agents.sealights.co/SL.DotNet/SL.DotNet-$($agentversion).zip Expand-Archive .\sealights-dotnet-agent.zip -DestinationPath SL.DotNet -Force Write-Output "Sealights agent version used is: $(Get-Content .\SL.DotNet\version.txt)" Write-Output "`n*** Create PR BSID ***" .\SL.DotNet\x64\SL.DotNet.exe prConfig --appName $APP_NAME --pullRequestNumber $PR_NUMBER --targetBranch $PR_TARGET_BRANCH --latestCommit $PR_LAST_COMMIT --repositoryUrl $REPO_URL --includeNamespace CalculatorServer.Controllers --buildSessionIdFile $(Build.ArtifactStagingDirectory)\SealightsBuildSessionId.txt --token $(AgentToken.Sandbox) --logEnabled true --logAppendConsole true --ignoreCertificateErrors true Write-Output "`n*** Prepare for MSBuild ***" .\SL.DotNet\x64\SL.DotNet.exe prepareForMsBuild --buildSessionIdFile $(Build.ArtifactStagingDirectory)\SealightsBuildSessionId.txt --workspacePath $(Build.Repository.LocalPath)\src --baseDir $(Build.Repository.LocalPath) --ignoreGeneratedCode true --debugMode true --logEnabled true --logAppendConsole true --ignoreCertificateErrors true --token $($slagenttoken) --scm git --scmProvider vsts
Maven Build for a Java application
In the example below, we simply create the buildSessionId outside the JSON command using the relevant parameters.
The Target branch must have builds already reported to Sealights, otherwise the prConfig command will fail.
If your development process includes pull requests merged to features branch, you may want to exclude them from the scope if Sealights analysis or enforce a build to be reported with the creation of the feature branch (via a webhook).
#!/bin/bash echo "Downloading Sealights Agents..." wget -nv https://agents.sealights.co/sealights-java/sealights-java-latest.zip unzip -o sealights-java-latest.zip # sample values export SL_APP_NAME="myApp" export SL_PACKAGES_INCLUDED="*com.mycompany.*" # Pull request parameters per the Sealights documentation if [ -n "${BITBUCKET_PR_ID}" ]; then #Pull Request context (Bitbucket environment variables) java -jar sl-build-scanner.jar -prConfig -token $SL_TOKEN -appname $SL_APP_NAME \ -targetBranch "origin/$BITBUCKET_PR_DESTINATION_BRANCH" -pullRequestNumber $BITBUCKET_PR_ID \ -latestCommit $BITBUCKET_COMMIT -repoUrl "https://bitbucket.mycompany.int/$BITBUCKET_REPO_SLUG" \ -pi $SL_PACKAGES_INCLUDED else #Regular Build java -jar sl-build-scanner.jar -config -token $SL_TOKEN -appname $SL_APP_NAME \ -branchname "${GIT_BRANCH}" -buildname "${BUILD_NUMBER}" -pi $SL_PACKAGES_INCLUDED fi echo '{ "token": ${SL_TOKEN}, "createBuildSessionId": false, "buildSessionIdFile": "./buildSessionId.txt", "filesIncluded": "*.class", "filesExcluded": "*test-classes*", "recursive": true, "includeResources": true, "testStage": "Unit Tests", "labId": null, "executionType": "full", "logEnabled": false, "logDestination": "console", "logLevel": "off", "logFolder": "/tmp/sl-logs", "sealightsJvmParams": {}, "enabled": true, "filesStorage": "/tmp" }' > slmaven.json echo "Updating POM with Sealights..." java -jar sl-build-scanner.jar -pom -configfile slmaven.json -workspacepath .