Components overview

• Windows Server 2012R2 or higher
• ArcGIS Pro 2.2 or higher
• Git Client https://git-scm.com/download/win
• Jenkins https://jenkins.io/download/thank-you-downloading-windows-installer-stable/

Prerequisites

• Windows Service account for Jenkins

Installation

ArcGIS Pro

To publish mapservices, Arpcy is needed and therefore an ArcGIS Pro installation on the server is needed. Obtain the installation files from Esri. ArcGIS Pro 2.2 and 2.3 have been tested.

Install ArcGIS Pro with the default options. See licensing for more information on how this ArcGIS Pro should be licensed

Jenkins

'The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.'

Jenkins will be used to checkout the repositories and to run the Python scripts.

Install Jenkins with default options.

Go to Windows Services and configure the Jenkins service to run under the Service Account.

Run the powershell script. This powershell script configures Jenkins Service to interact with the desktop. This setting is only available in the services menu when the service runs under Local System Account, but this account has insufficient privileges. 'interact with the desktop' is required to get font symbology working with custom fonts. If custom fonts are used for point symbols and this 'interact with the desktop' setting is not set, the custom fonts will be replaced with default fonts and the symbology will break in the resulting mapservice.

GIT

Install the GIT client

Licensing

ArcGIS Pro has different licensing options

• Named user: when you license ArcGIS Pro with a named user account, you need to login as the Service User to configure this. The license connection will get lost sometimes for unknown reasons and Jenkins cannot publish the service in this situation. Don't try to fix this by taking you license offline, because you might experience an error when ArcGIS Pro tries to start and you need to ask Esri support to reset your license!
• License Server: If your organization is entitled to floating users licenses for ArcMap, you can convert Pro named user licenses to licenses which you then can configure in your license manager. This works very good with publishing automation.
• Single license: If your organization is entitled to single licenses for ArcMap, you can convert Pro named user licenses to licenses which you then can configure in ArcGIS Pro. This works very good with publishing automation.

Configuration

GaiaBuilder

Unzip the GaiaBuilder Python Toolboxes to the local harddrive (C:\GaiaBuilder), the zip can saved from the ArcGIS Pro Add-In:

Optionally, configure the GaiaBuilder Geoprocessing service. The GaiaBuilder Geoprocessing moves all Arcpy functions to ArcGIS Server and a future release of GaiaBuilder will no longer have a dependeny on Arcpy, resulting in more flexibility for build server or agent architecture. Open Publish GaiaBuilder Geoprocessing Service to Federated Server Tool from the Amin Section of GaiaBuilder Map Publising in ArcGIS Pro.

• Log in with an user with Administrative privileges on ArcGIS Enterprise in ArcGIS Pro
• Enter the URL of your ArcGIS Server where you want to publish the service. The webadaptor must have administrative access enabled, when this is not the case, publish to port 6443. Examples: https://your.arcgisserver.local/server or https://your.arcgisserver.local:6443/arcgis
• When the ArcGIS Server does not have the hosting role in your ArcGIS Enterprise, generate a connection file and provide the file location of the .ags file
• When a previous version of GaiaBuilder Geoprocessing exists on the server: select Update existing GaiaBuilder Geoprocessing Service

Open GaiaBuilder.ini.template and configure the ini file . Save the file as GaiaBuilder.ini