Author Topic: Implement Central DB Repository With Version Control Using Azure DevOps?  (Read 2561 times)

jVizzon

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
We only recently started using EA for system modeling in the past year, and have been using file replicas of a master QEA file for collaboration.  We have evolved to enough users that a central DBMS and version control is likely warranted.  I have read the existing documentation and successfully implemented a setup using MariaDB as the DBMS and a Subversion server for version control. 

However, I am now looking to implement a setup on our local network and the IT team wants to host everything in Azure DevOps for both the SQL database and version control.  As best I can tell, Azure DevOps version control is the evolution of Team Foundation Version Control which is supported by EA but I have never used before.

Is using Azure DevOps for both the DBMS and version control supported?
Would the instructions for implementing be any different than described in the documentation?
Or is my IT department trying to force a square peg into a round hole?

Thanks.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13282
  • Karma: +556/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Implement Central DB Repository With Version Control Using Azure DevOps?
« Reply #1 on: October 25, 2024, 01:25:09 am »
You can use Azure Devops (TFS repository) to do version control, also in combination with SQL Server as repository type.

I'm not sure what you mean by "use Azure Devops for SQL database" though.
In general that is used when developing a database to version control the changes to the schema, but in this case you are simply using a database with a fixed schema.

Geert

jVizzon

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Implement Central DB Repository With Version Control Using Azure DevOps?
« Reply #2 on: October 25, 2024, 03:46:42 am »
Thanks for the input, Geert.
I assumed that Azure DevOps functionality would mirror the setup I tested on my homelab:
- one instance of a stand-alone database server (containing one database per EA project)
- one instance of a stand-alone version control server (containing one remote repo per EA project)

My assumption (which is probably incorrect) was that there would be one instance of Azure DevOps that would act as the database server and another that would act as the version control server.  From your response, it sounds like both capabilities could be handled in the same instance of Azure DevOps.

I am new to Azure DevOps and its capability so I apologize if this is overly simplistic.
In any case, I am reaching out to my IT team to see if they can sandbox a setup that we can do some testing with.

Thanks again.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13282
  • Karma: +556/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Implement Central DB Repository With Version Control Using Azure DevOps?
« Reply #3 on: October 25, 2024, 05:05:47 am »
Azure Devops is only the version control server. Database server is something else entirely.
We host our repositories on Azure SQL, but you could also host them on an on-prem server, or even on your local machine.

Geert

DeBAAT

  • EA User
  • **
  • Posts: 63
  • Karma: +2/-0
    • View Profile
Re: Implement Central DB Repository With Version Control Using Azure DevOps?
« Reply #4 on: October 25, 2024, 07:16:24 pm »
If the main requirement is to go cloud, you could try to ask for a quote to use EA SaaS.
Than you get Sparx to handle all the installation hassle and you only need to connect to Azure for the SSO and handle the rest as Admin within EA like you would in the EA fat client solution.