Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Advice needed: Switching to AL-GO Github?
joostheger
Member Posts: 9
Hello all,
A year ago, we started working with BC using Azure Devops and VS Code. Last week i've viewed some interesing dev blogs of the AL-Go team. At first sight, it looks promising. Should we consider switching to AL-Go?
The mayor drawback of using Azure Devops, is that we would like to do automatic unit testing, but we're using an cloud environment. We did't succees yet making it work properly.
We have currently only one extension we're working on, but planning on doing more.
Any advise?
A year ago, we started working with BC using Azure Devops and VS Code. Last week i've viewed some interesing dev blogs of the AL-Go team. At first sight, it looks promising. Should we consider switching to AL-Go?
The mayor drawback of using Azure Devops, is that we would like to do automatic unit testing, but we're using an cloud environment. We did't succees yet making it work properly.
We have currently only one extension we're working on, but planning on doing more.
Any advise?
0
Answers
We were using a homemade devops pipeline, and we need to not handled that internally, but if you want to say with Azure devops, then you can have a look a ALOps or Cosmo alpaca.
If you're using some of the project management features in Azure DevOps, it's worth comparing them to what GitHub offers (e.g., Azure Boards vs. GitHub Projects or Azure Testplan ). Azure DevOps is generally more comprehensive in those areas.
If you are "just" hosting a repo, then I would still test both AL-Go for Github, ALOps (https://www.alops.be/) and COSMO Alpaca (https://www.cosmoconsult.com/en/solutions/products/cosmo-alpaca).
Depending on your license (as a Microsoft partner, you may be eligible for free or discounted use of Azure DevOps, depending on your company size), pricing can vary. GitHub has a different pricing model.
Currently, our company is using GitHub Team as a minimum, and we're considering upgrading to GitHub Enterprise for security reasons.
For our needs, AL-Go turned out to be a great fit!