[ https://issues.jboss.org/browse/JBIDE-15339?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15339: ------------------------------------ * Goal: be able to more easily see if a feature or plugin needs to be upversioned ** JBIDE-19056 A Mojo to validate a version (compared to baseline) ** also have https://github.com/jbosstools/jbosstools-versionwatch/ running for all JBDS builds to audit all org.jboss / com.jboss + all upstream IU versions ** *DONE* * Goal: be able to more easily see if a commit in github has been built into the jars in an update site ** buildinfo.json is produced for each and every update site now; includes upstream URLs, github SHAs, github project URLs *** https://devstudio.redhat.com/10.0/snapshots/updates/core/master/buildinfo... *** http://download.jboss.org/jbosstools/neon/snapshots/updates/core/master/b... *** http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bas... ** https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/u... for auditing when we're in code freeze / some jobs are disabled ** *DONE* * Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs) ** Jenkins job name is already captured in buildinfo.json, as WORKSPACE for each job contains the JOB_NAME. Do we need anything else? ** Github & upstream URLs are already captured in buildinfo.json; see examples above ** sounds like we need some add to buildinfo.json to capture TP URLs ** not sure what we need to do for a link back to JIRA... just a generic link to JBIDE or JBDS? Or multiple links for each JIRA changed/closed between builds? [~maxandersen] [~mickael_istria] [~mmalina] can you help explain this requirement and how we might use such a report? Is this something you see value in creating, or are we good enough w/ all the above tools, mojos & metadata in buildinfo.json to close this issue? -- This message was sent by Atlassian JIRA (v6.4.11#64026)