[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15135: --------------------------------------------- {quote} knownReferences allow to know from which tag or branch the build was triggered. I feel this might be useful one day{quote} About the name I was just not sure what "knownReferences" means and why there are multiple of them. But now I grok it - the knownReferences are what symbolic names matches the HEAD sha1. {code} "revision": { "knownReferences": [ { "ref": "HEAD", "name": "origin", "url": "git@github.com:jbosstools/jbosstools-openshift.git" }, { "ref": "JBIDE-19076", "name": "origin", "url": "git@github.com:jbosstools/jbosstools-openshift.git" }, { "ref": "master", "name": "origin", "url": "git@github.com:jbosstools/jbosstools-openshift.git" } ], "HEAD": "789667220e157a2dc0e0c325ca4845ad87f1a88d" }, {code} It just threw me off that the actual used SHA was coming *After* known references. Is there a way to actually have it state what the active branch was instead of just HEAD ? i.e. I would have expected something like this when building from jbosstools-4.2.x: "revision": { "knownReferences": [ { "ref": "HEAD", "name": "origin", "url": "git@github.com:jbosstools/jbosstools-openshift.git" }, { "ref": "JBIDE-19076", "name": "origin", "url": "git@github.com:jbosstools/jbosstools-openshift.git" }, { "ref": "jbosstools-4.2.x", "name": "origin", "url": "git@github.com:jbosstools/jbosstools-openshift.git" } ], name: "jbosstools-4.2.x" sha1: "789667220e157a2dc0e0c325ca4845ad87f1a88d" } i.e. where it can be seen not only the sha1 used, but lists the symbolic name used for the checkout. {quote}but I didn't figure out any real use-case yet. We can get rid of it if you want.{quote} Knowing what the build actually used for symbolic name + the used sha1 is the important one. the knownReferences does not hurt, but it could be informative. -- This message was sent by Atlassian JIRA (v6.3.11#6341)