e DASTARDLY_OUTPUT_FILE=%%/reports/dastardly-report. The upload to the server and packaging of the tool to a zip seems to work fine. Param('xmlReportParsing.reportDirs', '+:**/reports/**.xml')ĭockerImage = '/portswigger/dastardly:latest'ĭockerImagePlatform = TeamCity General Topics Failed to download upgrade from server on agents after adding handle.exe tool Follow Completed Nicola Fera Created Ap10:15 Hello, I just recently added the handle.exe tool via the TeamCity UI. Import .buildSteps.scriptĭescription = 'Contains all other projects' Creating the settings fileĬonfigure access from TeamCity to the repository where your settings.kts file is stored.Īdd the following content to your settings.kts file: No plugins beyond the TeamCity defaults are required to run Dastardly in a TeamCity CI/CD pipeline.įor information on the machine specification required to run Dastardly scans, see the Dastardly system requirements. Your TeamCity agent must have Docker configured to run containers. These instructions have been tested with TeamCity 2022.04.4. This page contains instructions on how to integrate Dastardly with a simple (example) TeamCity CI/CD pipeline. This enables you to run Dastardly web vulnerability scans as a stage in your existing CI/CD pipeline.

You can integrate Dastardly with TeamCity. DASTARDLY Integrating Dastardly with TeamCity The configuration added to these build steps allows defining the artifacts to upload and download by either using File Specs or.

Download teamcity tool