Continuous Delivery and Testing » History » Version 2
Version 1 (Luke Murphey, 02/24/2017 08:53 AM) → Version 2/11 (Luke Murphey, 02/25/2017 07:29 AM)
h1. Continuous Delivery and Testing
You can use a continuous integration tool to automate testing and deploying your Splunk apps. This will allow you to:
# Test your app on several platforms and versions of Splunk automatically (or with a click of a button)
# Easily build clean and consistent copies of your app (avoids the possible corrupt builds made on Developer hosts)
# 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)
You can use a continuous integration tool to automate testing and deploying your Splunk apps. This will allow you to:
# Test your app on several platforms and versions of Splunk automatically (or with a click of a button)
# Easily build clean and consistent copies of your app (avoids the possible corrupt builds made on Developer hosts)
# 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)