I am investigating how to have a continuous build process for our Splunk addon and I saw that there are 3 options: slim -a cli tool that is a part of Package apps with the Packaging Toolkit | Documentation | Splunk Developer Program AppInspect - a part of Validate quality of Splunk apps | Documentation | Splunk Developer Program Add-on Builder - Install the Add-on Builder - Splunk Documentation slim gave me very little output and it wasn't clear what sort of validations it was running. app-inspect is very configurable and provides rich output so I'm pretty happy with it. However, I got a recommendation to trust the Add-on Builder's validations. Unfortunately, apart from using some Selenium manipulations to touch the Splunk UI, I wasn't able to identify a way to automatically call it validation logic from an HTTP API or a cli. Finally, the output of AppInspect & the Add-on Builder differs - I'm currently checking why this is so. Perhaps the validations are completely different ... So my questions to the community are: 1. What is the best approach to validate a Splunk add-on? 2. How would you recommend automating at least the validation part of the process? Thank you so much in advance!
... View more