Continuous Delivery and Testing¶

You can use a continuous integration tool to automate testing and deploying your Splunk apps. This will allow you to:

1. Test your app on several platforms and versions of Splunk automatically (or with a click of a button)
2. Easily build clean and consistent copies of your app (avoids the possible corrupt builds made on Developer hosts)
3. Deploy the app to your test and production hosts with a single click

Some notes:
To use a created package (spl or tar.gz), make sure to:

• Make a fetch artifact step
• Set the fetch as a file, not a directory (https://groups.google.com/forum/#!searchin/go-cd/gocd$20fetch$20zip$20artifact$20%7Csort:relevance/go-cd/Ja5lBT6bpRA/A0ojaSRqBwAJ)

Need to create a minimal account for installing apps with the following capabilities per (https://answers.splunk.com/answers/67843/capability-to-install-app.html):

• rest_apps_management
• admin_all_objects

You might need to add the user "go" to the "splunk" group:

sudo usermod -G splunk go

Should this be done using:

1. The build script?
   1. Pros: Could hide password using secure variable; can be done in a single line; password can be globally in environment variables
   2. Cons: requires the build script as a material; requires ant on all agents
2. Direct commands?
3. Straight copying?

Using the build script:
Pros:

1. Could hide password using secure variable
2. Can be done in a single line
3. Password can be globally in environment variables
4. Could bump Splunk too

Cons:

1. Requires downloading the build script as a material
2. Requires ant on the agents