# Ignition with Azure DevOps

**URL:** <https://forum.inductiveautomation.com/t/ignition-with-azure-devops/46095>\
**Category:** General Discussion\
**Created:** [April 28, 2021, 8:08am UTC](https://forum.inductiveautomation.com/t/ignition-with-azure-devops/46095 "2021-04-28T08:08:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![indenkleefj](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/indenkleefj/32/10961_2.png) [@indenkleefj](https://forum.inductiveautomation.com/u/indenkleefj)\
**Post date:** [April 28, 2021, 8:08am UTC](https://forum.inductiveautomation.com/t/ignition-with-azure-devops/46095/1 "2021-04-28T08:08:17Z")

</div>

Hi,

I want to use Azure DevOps to manage the development of my project.  
At this point, I’m going to use the Azure Board and Azure Repos.  
But was wondering if there are ways to implement more features of Azure.  
For example:  
• Are there ways to test Ignition automatically?  
• Are there ways to automatically Deploy Ignition on a server?  
• Are there ways to integrate CI/CD with Ignition?

In addition to the automatically testing, are there ways to test the code you write?  
I mean that I can get something working doesn’t mean that my code is made in a professional and good way.

---

<div class="post-metadata">

**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\
**Post date:** [April 29, 2021, 1:50am UTC](https://forum.inductiveautomation.com/t/ignition-with-azure-devops/46095/2 "2021-04-29T01:50:18Z")

</div>

I just made a reply on this thread.... [Source control in Ignition 8 - #11 by ryanjmclaughlin](http://forum.inductiveautomation.com/t/source-control-in-ignition-8/26886/11)

> [@indenkleefj](#):
>
> • Are there ways to automatically Deploy Ignition on a server?

Yes, we just setup Devops release pipelines to perform project deployments. Ignition projects are simply file resources, so all that is needed is a copy files task to move the project files to the target gateway.

> [@indenkleefj](#):
>
> In addition to the automatically testing, are there ways to test the code you write?

Others might chime in more, but I work with developers from both an IT background and an Operational/Engineering background. I always feel that Ignition is an operational tool, not an IT tool. When you focus too strong on testing "code" then you try to write everything in Ignition is scripts which is just the wrong approach. Most users I work with that avoid coding everything in Ignition are more successful. A lot of parts of Ignition are configuration over code so standard unit testing and such is not really possible, I'm sure it could happen, but not sure if its worth the effort.