[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15135 at 2/17/15 12:57 PM: -------------------------------------------------------------- 0. Build.properties (generated by publish.sh) contains: {code}REV_LOG_DETAIL="origin/jbosstools-4.3.0.Alpha1x@79b3dcd80d3c6f96b3671f5eae6f25d94d5c3801"{code} buildinfo.json contains: {code} "revision" : { "HEAD" : "79b3dcd80d3c6f96b3671f5eae6f25d94d5c3801", "currentBranch" : "HEAD", "knownReferences" : [{ "name" : "origin", "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", "ref" : "jbosstools-4.3.0.Alpha1x" }]{code} So, that's awesome. All other metadata is also present in the json file, including: {code}BUILD_ALIAS, JOB_NAME, BUILD_NUMBER, BUILD_ID TARGET_PLATFORM_VERSION, TARGET_PLATFORM_VERSION_MAXIMUM{code} --- However... a couple problems still exist here: 1. index.html generated for update sites does not provide a link to buildinfo.json. Without a link (next to site.properties, perhaps) how will anyone ever find this file? 2. http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... contains *HUDSON_SLAVE = null*. But there's a value for os.version and os.arch. Did something go wrong with the computation of `uname -a` ? Would still like to know the slave used to run the build. 3. Also missing is *WORKSPACE = /path/to/workspace/*, so if we have to ssh to the slave to debug we know where the workspace is located (it's not the same on all slaves). was (Author: nickboldt): 0. Build.properties (generated by publish.sh) contains: {code}REV_LOG_DETAIL="origin/jbosstools-4.3.0.Alpha1x@79b3dcd80d3c6f96b3671f5eae6f25d94d5c3801"{code} buildinfo.json contains: {code} "revision" : { "HEAD" : "79b3dcd80d3c6f96b3671f5eae6f25d94d5c3801", "currentBranch" : "HEAD", "knownReferences" : [{ "name" : "origin", "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", "ref" : "jbosstools-4.3.0.Alpha1x" }]{code} So, that's awesome. All other metadata is also present in the json file, including: {code}BUILD_ALIAS, JOB_NAME, BUILD_NUMBER, BUILD_ID TARGET_PLATFORM_VERSION, TARGET_PLATFORM_VERSION_MAXIMUM{code} --- However... a couple problems still exist here: 1. index.html generated for update sites does not provide a link to buildinfo.json. Without a link (next to site.properties, perhaps) how will anyone ever find this file? 2. http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... contains *HUDSON_SLAVE = null*. But there's a value for os.version and os.arch. Did something go wrong with the computation of `uname -a` ? Would still like to know the slave used to run the build. 3. Also missing is WORKSPACE = /path/to/workspace/, so if we have to ssh to the slave to debug we know where the workspace is located (it's not the same on all slaves). -- This message was sent by Atlassian JIRA (v6.3.11#6341)