Integrate with TeamCity

abstract TeamCity and other Continuous Integration systems can trigger Sahi scripts as part of the build process using Sahi's ANT target.

Sahi with TeamCity

Automation is useless without Continuous Integration. Sahi suites should be periodically executed and CI systems can trigger suites when code changes happen. Sahi suites can be triggered via ANT. We configure TeamCity to call Sahi's ANT target and then make Sahi's logs accessible from TeamCity.

Prerequisites

Before integration, you will first need an ant target to run the suite file. You can create the ANT target from the editor using playback options. Save the file in any path accessible by TeamCity (say C:\teamcity_sahi) and lets call it build.xml.

info At the end of the configuration steps in this page, your folder structure should look like this:

C:
  |--teamcity_sahi
         |
         |--build.xml
         |--email.properties
         |--lib
             |
             |--ant-sahi.jar

In the build.xml make sure that:

scriptDir points to where your Sahi scripts will reside on your TeamCity machine. This will mostly be the local directory where the scripts are checked out via Git or SVN. If your checkout directory is E:/automation/scripts/ your build.xml should have
```
<property name="scriptDir" value="E:/automation/scripts/"/>
```
Offline reports path should be configured correctly. The path in report tag in build.xml should be the same as that used in Publish HTML Reports in Jenkins configuration In this example, we use <report type="html" logdir="C:/teamcity_sahi/logs/html/"/>
If email is configured to be sent at the end of a build, the path to email.properties in build.xml should point to the correct location. You will need to copy SahiPro/userdata/config/email.properties into C:/teamcity_sahi/email.properties and have this in build.xml
```
<property name="emailproperties" value="C:/teamcity_sahi/email.properties"/>
```

Configure TeamCity

Create a new project with name as sahi_automation (This will be the name of the project identified by TeamCity.)
Now edit project settings

Click on Create build configuration. Specify build configuration name as run_sahi_scripts and click on Create

Now go to build configuration settings and add build steps

Choose Runner type as Ant and specify the path to the build.xml file

To publish HTML reports after build, go to build configuration settings. Edit general settings and specify Artifact paths

View Sahi Pro HTML Logs in TeamCity

Once Artifacts are configured, one can find Sahi's report logs by hovering over on the "Artificats" icon on the right side for that specific build number on the TeamCity project page.