-
Enhancement
-
Resolution: Done
-
Major
-
4.1.0.Final
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 )
- is related to
-
JBIDE-14642 How to automate process of bumping version for changed modules/submodules for every release
- Closed
-
JBIDE-19056 A Mojo to validate a version (compared to baseline)
- Closed
- relates to
-
JBIDE-4731 use p2.mirror w/ comparator to verify plugin/feature versions are correctly incremented between builds/baselines
- Closed