[jbosstools-issues] [JBoss JIRA] (JBIDE-15339) Create version/change auditor/reporting tool

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt closed JBIDE-15339.
------------------------------
    Resolution: Done


Spoke with Alexey, Len, Denis, Mickael, and Fred on the build.next call today and the consensus is that we're doing enough here. 

* Capturing the version of TP used at build time COULD be useful but if the TP is a SNAPSHOT there's no guarantee of content.
* Using the SHA value of the TP repo's last commit could also be useful but no one felt this was a big enough concern to warrant spending time on it.
* Links back to JIRA can be achieved by looking at the commit's SHA in the MANIFEST.MF files (or buildinfo.json) and then reviewing git commits for JIRA #s, or Jenkins job build changelogs.

So, for now I'm closing this issue. If one of the above ideas sounds like something we'd like to add to buildinfo.json, please move it into a new JIRA.

> Create version/change auditor/reporting tool
> --------------------------------------------
>
>                 Key: JBIDE-15339
>                 URL: https://issues.jboss.org/browse/JBIDE-15339
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build, updatesite
>    Affects Versions: 4.1.0.Final
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>              Labels: versioning
>             Fix For: 4.3.x
>
>
> Plugin/Feature Version Auditor
> Goal: be able to more easily see if a feature or plugin needs to be upversioned
> Goal: be able to more easily see if a commit in github has been built into the jars in an update site
> Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs)
> Output: generate a report of: 
> plugins, features in JBT or JBDS by version, md5 #, JIRA #s related to latest commits, jenkins build IDs
> Include URL links to content/metadata: Github, Jenkins, JIRA, dl.jb.org (upstream sites which feed the aggregates, target platforms, composites, etc.)
> May also include some parallel work to provide improvements to QA's versionwatch tool (https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch )



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)