Azure Pipelines vs. Flagsmith

It is good tool if you are doing continuous improvements in your code and you wish it goes live whenever you push code to GitHub. So integrating Azure Pipeline, it automatically does CI/CD in the background once you push code/merge code and it is live in few minutes. It also does some automated tests if you have wrote scripts

Incentivized

Flagsmith is the best tool I worked with for feature flags, in terms of how easy and intuitive it is to use. On the other hand, it has all the features we need to effectively manage features.

Incentivized

• Integration with SonarQube
• Integration with Azure DevOps
• Integration with GitHub

Incentivized

• Controle features feasability
• Create user segements
• Mange multiple environments

Incentivized

• The errors which we got sometimes are not clearly enough.
• There are some let's say hidden options, they could be more visible
• When the process is running we have to remember about manually refreshing to see the current status because it doesn't work automatically

Incentivized

• Search users based on traits

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 have had outages from Azure in the past

Incentivized

• We can be very flexible to client needs by quickly deploying new features behind flags.
• We can support the sales dept by deploying demo features without risk to stability.

Incentivized