Continuous Integration and Deployment of Jira Configurations

[Amos Bennett]

Has anyone come across a continuous integration and deployment tool/method for Jira Data Center in relation to deploying and testing configuration changes across environments (e.g a development and production environment)?

We have some fairly complex configurations (schemes, asset models) and making changes manually across environments is not ideal. Configuration Manager for Jira has worked well, however there are somethings it misses, particularly if it's a third party application configuration.

It would be great if Jira's configuration state could be fully defined in a manifest (or set of manifests) that could then be synchronised with a GitOps workflow.

[Sagi Bracha Salto_io]

Hi Amos, that's exactly what Salto does. 

We translate configuration into textual format so it can be analyzed, deployed between environments and version controlled. We integrate with any version control/ CI provider so you can customize and automate a complete CI/CD pipeline, including pull requests, CI jobs, etc. 

You can find more details and demos in our marketplace listing but for this use case you may want to talk with one of our DevOps engineers.

[Amos]

Amazing - thank you so much for this. I'm definitely going to have a serious look at this.

[Amos]

Hi Sagi, are you able to quickly describe (or send a link) how this works? I’ve come across the CLI however in our situation, Jira DC is sitting on infrastructure that is air-gapped (not connected to the internet). Does Salto support that or does it require connectivity to the Salto.io domain?

[Dan Avigdor]

@Amos Bennett, nice to e-meet you. I'm Dan, also part of the Salto family. Regarding your question, please note that in order to connect to Salto via CLI or SaaS, you need to whitelist our IP addresses as outlined in this document: Salto's IP Addresses.