[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15135: --------------------------------------------- I like the format/idea of using json and embedding the upstream info for verifcation purposes. 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 ? 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. 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 -- This message was sent by Atlassian JIRA (v6.3.11#6341)