DevOps for ArcGIS Enterprise

Automate ArcGIS
content deployments.
From development
to production.

Version your maps, apps, and services. Promote content across ArcGIS Enterprise environments with automated deployments, a traceable change history, and rollback when you need it. Nodeology helps your team put the workflow into practice.

See GaiaBuilder in action

Watch Merkator’s introduction ↗

Developed by Merkator. Delivered and supported by Nodeology.

FROM DEVELOPMENT TO PRODUCTION

01
DevelopPrepare content and track changes
02
Test & acceptValidate in a separate environment
03
DeployPromote a repeatable configuration
↶   Version history & rollback

More control over change

Replace repetitive publishing
with a managed release process.

Copying items, adjusting URLs, and repeating changes across environments takes time. GaiaBuilder brings content configuration, version history, deployment, and recovery into a process your GIS and IT teams can maintain together.

01

Automate deployment

Move ArcGIS content through repeatable deployments and reduce the manual steps required for each release.

02

Version your content

Use Git-friendly JSON configurations to track changes to ArcGIS content alongside your development work.

03

Return to a previous release

Keep previous versions available and use rollback capabilities when a deployment needs to be reversed.

Inside a GaiaBuilder workflow

See the content.
Follow the changes.

These Azure DevOps views show a GaiaBuilder demonstration repository, including version history and successful and failed build results.

GaiaBuilder demonstration repository in Azure DevOpsView full size ↗
Content files and their version history in Azure DevOps.
Azure DevOps commit graph with pull requests and build status for a GaiaBuilder demonstrationView full size ↗
Trace commits and pull requests alongside their build status.

A governed deployment workflow

From the first change
to the next release.

Bring content, configuration, and deployment into a connected workflow across development, testing, acceptance, and production.

Walk through your deployment process ↗
  1. 01

    Prepare and version

    Author your content, capture its configuration, and maintain it in version control.

  2. 02

    Deploy and validate

    Promote content to a test or acceptance environment and review it before production.

  3. 03

    Promote and maintain

    Deploy repeatably, retain change history, and keep previous versions available for recovery.

ArcGIS content, connected

Web mapsWeb applicationsDashboardsMap & feature servicesGeoprocessing services

Manage content relationships and environment-specific URLs as items move across your deployment environments.

Connect GIS and IT

Bring ArcGIS into
your DevOps workflow.

GaiaBuilder includes an ArcGIS Pro add-in and integrates with Git-based release processes.

Integration options

Azure DevOpsGitHubGitLabJenkins

Review the change history

Git records who changed what and when, supporting release reviews and audits.

Separate credentials from code

Integrations such as Azure Key Vault keep credentials out of Git and deployment logs.

Support server transitions

Use GaiaBuilder’s deployment capabilities when moving content to another server.

Product capabilities: Merkator’s GaiaBuilder overview ↗

Across the organization

Built around
how your teams work.

Enterprise GIS teams

Establish consistent promotion workflows for the maps, apps, and services your organization depends on.

IT & DevOps teams

Connect GIS deployment to version control and automation practices used elsewhere in the organization.

Engineering & managed services

Build a repeatable delivery approach for client ArcGIS environments, supported by implementation and training.

Published customer examples

See what a repeatable
release process changes.

Some of the most respected companies and government agencies rely on GaiaBuilder to manage and automate their ArcGIS application and content deployments. Discover what GaiaBuilder can do for your organization.

Examples reported by Merkator, the developer of GaiaBuilder.

Government organization

Deployments in about two minutes

Merkator describes an organization managing critical infrastructure that replaced unpredictable manual deployments with standardized pipelines, Git traceability, and rollback.

Read Merkator’s government case study ↗

Waternet / Utility

GIS releases connected to IT

Waternet used GaiaBuilder to replace lengthy manual release processes, introduce rollback, and establish a Git-based workflow across its ArcGIS Enterprise services and applications.

Read Merkator’s Waternet case study ↗

Client perspective

“GaiaBuilder enables us to implement ArcGIS Enterprise updates with confidence. What used to take a full day now only takes minutes, and if something goes wrong, we can instantly roll back.”
GIS Manager

Implementation, training & support

Put GaiaBuilder to work
with Nodeology.

Start with the content your team deploys today. Nodeology provides implementation, training, and support, from reviewing your environments and configuring an initial workflow to helping your team manage everyday releases.

What happens during implementation?

We review your ArcGIS environments and deployment needs, configure GaiaBuilder, and help your team establish a practical release workflow. Training covers using and maintaining that workflow.

What does development-to-production mean?

Changes move through separate development, testing, acceptance, and production environments. Your team can review content before releasing it to users and retain previous versions for recovery.

Do we need an existing CI/CD pipeline?

You can begin by discussing the workflow you have today. We’ll help identify a practical starting point for version control, deployment automation, and integration with your preferred tools.

How is this different from a one-time content copy?

GaiaBuilder supports ongoing content lifecycle management: versioning, repeatable promotion across environments, deployment automation, and rollback. The focus is a process your team can maintain and use again.

Who develops and supports GaiaBuilder?

GaiaBuilder is developed by Merkator. Nodeology resells the solution and provides implementation, training, and support.

Let’s put it to work

Make your next deployment
a repeatable one.

Bring an example of a release your team manages today. We’ll walk through how to version, deploy, validate, and recover that content with GaiaBuilder.

Schedule a GaiaBuilder walkthrough