Answers for "version vs. build settings in app.conf"https://answers.splunk.com/answers/4034/version-vs-build-settings-in-app-conf.html
The latest answers for the question "version vs. build settings in app.conf"Answer by southeringtonphttps://answers.splunk.com/answering/6321/view.html
<p>And since you're going to want to update these every time you repackage your app, it ends up being easier just wrap the whole thing in a shell script that does the work for you, e.g.:</p>
<pre><code>#!/bin/sh
#################################################
# Skeleton of app release script
#################################################
APPDIR=/opt/splunk/etc/apps/myapp
# Bump version number
cd $APPDIR
let VER=`cat .dist_version`
let VER=VER+1
echo $VER &gt; .dist_version
perl -i -pe "s/^build\s*=.*/build=$VER/g" default/app.conf
perl -i -pe "s/^version\s*=.*/version=1.1.$VER/g" default/app.conf
# More stuff here (scrub private data, etc.)
# Build the archive
cd $APPDIR/..
tar cvzf myapp-$VER.tgz $APPDIR --exclude $APPDIR/local --exclude $APPDIR/metadata/local.meta
</code></pre>Thu, 02 Sep 2010 04:49:37 GMTsoutheringtonpAnswer by Justin Granthttps://answers.splunk.com/answering/4483/view.html
<p>I dug through the Splunk Web and Splunk Manager code, and here's what I found: </p>
<p>Apparently <code>build</code> and <code>version</code> are totally unrelated to each other, but (arrrgh!) both must be incremented every time you rev your app. Here's more details:</p>
<p>"version" is displayed to the user in Manager, and on Splunkbase. Upcoming changes to Splunkbase will require that the version specfied in the UI when uploading into Splunkbase match the version specified in app.conf. Furthermore, when uploading a new Splunkbase version, the version string must be different from previous versions. These requirements together mean that you need to rev version in app.conf every time you upload a new version to Splunkbase. But, as far as I can tell, version isn't used anywhere else inside the Splunk product-- it's purely for display purposes inside the product. </p>
<p>"build", however, is used inside the product when generating URLs for static resources (images, CSS, etc.) Since your app's static resources are cached, updating the build number ensures that your new app's static files are reloaded at least once by the browser before being cached (until the next increment of the build setting).</p>
<p>So you'll definitely want to increment the build number every time you rev any of your app's static files. </p>
<p>And you'll want to increment version every time you upload a new version of your app to Splunkbase. </p>
<p>The safest thing would be to get in the habit of incrementing both every time you rev your app.</p>Fri, 09 Jul 2010 02:17:29 GMTJustin GrantAnswer by Simeonhttps://answers.splunk.com/answering/4407/view.html
<p>I recall using these values simply to track what version of an app I have built. I have not seen it used otherwise.</p>Wed, 07 Jul 2010 05:28:58 GMTSimeon