Jenkins for Jira Now Supports EU and US Data Residency, Government Cloud and Isolated Cloud

For many teams, moving Jira to the cloud isn't only a question of features. It's a question of where the data lives and who else shares the infrastructure. Security reviews ask it, procurement asks it, and in regulated industries the answer decides whether a tool can be used at all.

Jenkins for Jira now has answers for all three kinds of Atlassian cloud:

• Data residency in the EU or the US for the commercial cloud
• Atlassian Government Cloud for US government agencies and their partners
• Atlassian Isolated Cloud for organisations that need dedicated infrastructure

Here's what each one means, and what to check when you set up the connection to Jenkins.

Data residency: your build data stays in your region

Jenkins for Jira stores build, deployment and job data in its own backend. That backend now runs in two data residency realms: Europe and the United States.

Your installation is served from the realm that matches your Jira site's data residency location. So a Jira site pinned to the EU keeps its Jenkins data in the EU, and a US site keeps it in the US. Build and deployment history, job details and issue links stay in the same region as your Jira data.

Why this matters:

• Regulatory requirements. GDPR, sector regulators and internal policies often require data to stay within a region. Now your CI/CD data can meet the same rule as your Jira data.
• Simpler security reviews. "Where is our data stored?" has one answer for Jira and for the app.
• No change for developers. Issue keys in branches and commits still link builds to issues, exactly as before.

Update your firewall allowlist

The app uses a small, fixed set of IP addresses per realm to reach your Jenkins controllers. If you allowlist incoming connections to Jenkins, allowlist the addresses for your realm.

The current list is always available in machine-readable form:

• EU: https://jjc.marvelution.com/status/ip-addresses
• US: https://us.jjc.marvelution.com/status/ip-addresses

These addresses can change, so automate your firewall rules against these endpoints where you can, and keep an eye on IP notifications in the app. The security requirements page lists the current addresses and the endpoints Jenkins needs to reach.

If your Jenkins isn't reachable from the internet, you don't need to open anything: use a unidirectional connection, where Jenkins pushes data to Jira, or a tunneled connection (Advanced edition).

Atlassian Government Cloud

Atlassian Government Cloud is a separate cloud environment for US government agencies and their contractors, with FedRAMP Moderate authorisation for Jira, Jira Service Management and Confluence.

Jenkins for Jira supports Government Cloud, so federal teams and their partners get the same Jenkins integration as commercial cloud customers: builds and deployments on issues, triggering builds from Jira, and Jira Automation triggers and actions.

A few things work differently in Government Cloud:

• Installation goes through Atlassian. Government Cloud customers can't install Marketplace apps themselves yet; Atlassian support handles app discovery, assessment and installation. Ask your Atlassian contact to install Jenkins for Jira.
• Your own authorisation process still applies. Some agencies require their own review of third-party services. Contact us for the security documentation you need.

Atlassian Isolated Cloud

Atlassian Isolated Cloud is a dedicated, Atlassian-managed cloud environment. Data, compute, storage and networking run in a physically separate environment, and data egress is blocked by default, so the customer decides what's allowed to leave.

It's aimed at large organisations with sensitive data whose policies don't allow shared cloud infrastructure, and it's often the path to cloud for teams that stayed on Data Center for that reason.

Jenkins for Jira supports Isolated Cloud. Because egress is closed by default, plan the connection with your security team:

• Decide which connection model fits your network (unidirectional, bidirectional or tunneled).
• Agree which traffic between Jira, the app and your Jenkins controllers is allowed.
• Include the app in your Isolated Cloud app review, as with any other app you add.

Also new: site admins finalise the connection

With this release, connecting a Jenkins site now requires the Jira Site Administrator permission to finalise. That keeps control over which Jenkins instances can send data into your Jira in the hands of your site admins, which is what security teams expect.

Which cloud fits your team?

	Commercial Cloud	Government Cloud	Isolated Cloud
For	Most teams	US government agencies and contractors	Organisations with sensitive data that can't share infrastructure
Infrastructure	Multi-tenant, EU or US data residency	Separate environment, FedRAMP Moderate	Dedicated, Atlassian-managed, egress blocked by default
App installation	Self-service from the Marketplace	Through Atlassian support	Through the Isolated Cloud app process
Jenkins for Jira	✓	✓	✓

Planning your move off Data Center?

With Data Center reaching end of life in March 2029, these options remove one of the most common blockers: "our integrations can't meet our data requirements in the cloud." Your Jenkins history can come along too; see Moving to Jira Cloud? What happens to your Jenkins integration.

Have questions about data residency, Government Cloud or Isolated Cloud for your setup? Contact our support team or visit the Marvelution Trust Center.