[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- {quote} what does "knownReferences" refer to exactly ? are the unknown referenes too and why is both HEAD and master listed ? will there ever be multiple different ones ? is it a name used by jenkins ? I do see it lists multiple of my branches when building locally..which one is relevant ?{quote} knownReferences allow to know from which tag or branch the build was triggered. I feel this might be useful one day, but I didn't figure out any real use-case yet. We can get rid of it if you want. {quote} Also I saw today this error: [ERROR] Could not read build info at http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas... when running a single openshift build but the resulting buildInfo.json did not have any trace of that error. In case it fails to get those upstream references I think that should be visible somehow in the file and we should even for a CR/GA build fail the build. {quote} Yes, that makes sense. The "upstream" should be there with a field such as "error": "No upstream build description file found". I'll change that. {quote} Last point: I know you guys hate (or forgot about) it but could we please continue to use lowercase filenames, not mixed case names for artifacts so that would be buildinfo.json, not buildInfo.json {quote} ok... -- This message was sent by Atlassian JIRA (v6.3.11#6341)