Jenkins Integration SortSite Developer Manual
To test build outputs using SortSite Developer with Jenkins:
- Make sure the built app or site is available via an HTTP server
(e.g.
http://localhost/output
orhttp://your-staging/
) - Create a configuration file setting
ProcessURL
to the build output URL setup in the previous step - To flag a build failure when any issues are detected, set the
ExpectedResults
element in the XML configuration file - In Jenkins, create an Execute Shell task as the last build step to run SortSiteCmd passing the path of the XML configuration file, using a script similar to this:
Windows
"c:\Program Files (x86)\PowerMapper Software\SortSite 6\SortSiteCmd.exe" C:\Projects\SortSite.ssconfig
Mac
/Applications/SortSite.app/Contents/MacOS/SortSiteCmd /Projects/SortSite.ssconfig
Note: If you install Jenkins as a Windows service, it defaults to running under the Local System account.
This may cause problems if you need to access user-profile specific settings, such as self-signed certificates.
In general, only critical Windows services (and not Jenkins) should run under the Local System account, because it has a very high privilege level.