Azure Pipelines vs. TeamCode Tin

With a fully Microsoft Azure based workflow - Azure Pipelines makes absolute sense. Azure Pipelines are robust and work very well with SonarQube for test coverage and are shared with our developers. This prevents the developers for pushing code without unit tests across our backend and frontend platforms. We have reduced our instances of manual regression tests especially when there are multiple teams working across the same repositories.

Incentivized

• Code Integration/Code Deployment
• Azure Engine Auto Scaling Up with help of Pipeline
• Managing Version Control and deploy in rollback with just one click

Incentivized

• Error messaging when team members don't have permissions

Incentivized

We have used the GitHub CI/CD. Earlier we were using the Azure Pipelines but after GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live. GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient

Incentivized

• We don't have to deploy changes manually
• But because of this that we automated some tasks, we need to be still aware of some edge cases we can meet and which can cause a pipelines failures
• We can deploy changes pretty fast

Incentivized