CI/CD Process or Remote Repository UI on XSOAR

[Josep]

Hello,  

We are doubting whether to build a CI/CD Process or a Remote Repository UI on XSOAR. Looking to the table, CI/CD has more features. However, it doesn't allow you to work with Cortex XSOAR UI. This may mean that we will not be able to work with boxes, we will work directly with yaml and python. So is it possible to work this way? Or will it slow down the development considerably?

[amore]

Hi @Josep I will let the community weigh in, but to me it is a matter of preference. If your team is capable and proficient in development practices like content management through tools like github, and develop content outside XSOAR's UI, the CI/CD process might be better suited for you. The remote repositories feature, or dev-prod as we like to call it, allows all of the development to remain in XSOAR and also the management through the XSOAR UI. Hope that helps. 

[EnesOzdemir · Accepted solution]

As @amore mentioned it's a matter of preference. We use CI/CD to deploy content it also allows us to test our code. Currently we are only running validate and lint to see if the content is fine and passes the unit tests. With time you can implement much better development process but for starters it has quite a learning curve .

Content deployment is automated in our environment. Once a PR gets approved the contents get uploaded and synced to all tenants.