Continuous Delivery and Testing » History » Version 3
Luke Murphey, 02/25/2017 09:16 AM
1 | 1 | Luke Murphey | h1. Continuous Delivery and Testing |
---|---|---|---|
2 | 1 | Luke Murphey | |
3 | 1 | Luke Murphey | You can use a continuous integration tool to automate testing and deploying your Splunk apps. This will allow you to: |
4 | 1 | Luke Murphey | |
5 | 1 | Luke Murphey | # Test your app on several platforms and versions of Splunk automatically (or with a click of a button) |
6 | 1 | Luke Murphey | # Easily build clean and consistent copies of your app (avoids the possible corrupt builds made on Developer hosts) |
7 | 1 | Luke Murphey | # Deploy the app to your test and production hosts with a single click |
8 | 2 | Luke Murphey | |
9 | 2 | Luke Murphey | Some notes: |
10 | 2 | Luke Murphey | To use a created package (spl or tar.gz), make sure to: |
11 | 2 | Luke Murphey | |
12 | 2 | Luke Murphey | * Make a fetch artifact step |
13 | 2 | Luke Murphey | * 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) |
14 | 3 | Luke Murphey | |
15 | 3 | Luke Murphey | Should this be done using: |
16 | 3 | Luke Murphey | # The build script? |
17 | 3 | Luke Murphey | # Direct commands? |