Step name: Run Smartmeter test (or whatever you like)Ĭommand executable: path to SmartMeter /usr/local/bin/smartmeter/SmartMeter.shĬommand parameters: runTestNonGui /test.jmx -Jetn_report_name=%unter% -Jetn_reports_path= %ReportIndex% %Reporturl% %TrendsIndex% /home/teamcity/reports/report-%build.number%ġ) Go to build configuration of your project and add new build step. Spec - text validationMode='not_empty' label='Report Url' display='normal'ĥ) Now we have these 3 parameters configured.ġ) Go back to General settings of Build configuration settings of your project.Ģ) Add parameters to Artifacts paths. We will use here predefined build parameters : rverUrl, , build.number This will be the URL where you find report of the build. Spec - text validationMode='not_empty' label='Trends' display='normal'Ĥ) Add ReportUrl to parameters. Spec - text validationMode='not_empty' label='Perf Report' display='normal'ģ) Add TrendsIndex to parameters. Click button Add new parameter.Ģ) Add ReportIndex to parameters. Go to Parameters section of your build configuration. Example: /home/teamcity/reports in our setup.ģ: Running SmartMeter.io tests from TeamCity 3.1: Configuring Build Parametersġ) Add new parameters to your build configuration. Theese reports will be artifacts for your build runs. Reports directory - directory to store repors from SmartMeter.io.This is usually pulled from Version Controll System (VCS). Test directory - directory, that contains prepared. SmartMeter.io instalation directory - TeamCity’s agent need to have access to this directory and to run SmartMeter.sh in it. Before we begin, you have to gather some information about your SmartMeter instalation:
0 kommentar(er)
