[
https://issues.jboss.org/browse/JBIDE-4731?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-4731 at 8/13/13 9:18 AM:
------------------------------------------------------------
To answer [~maxandersen]'s questions:
Version Watch (vwatch) Sources:
https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch
Steps to use locally or in Jenkins [1], [2]:
{quote}
1. Install JBDS several times in order to perform a comparison of the plugin/feature
versions installed, and generate an HTML report.
(If on linux can use
https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/vwatch/install.... to
automate the process)
Put them all under some folder $\{INSTALL_FOLDER}.
2. Run maven to produce the report.
{code} mvn clean test -DinstallationsDir="$\{INSTALL_FOLDER}"
-Dvwatch.filter=".*(hibernate\|jboss\|xulrunner).*" -Dvwatch.md5check {code}
3. Open report in output.html in a browser to view resulting comparison table.
Jenkins jobs:
[1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat...
[2]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat...
was (Author: nickboldt):
To answer [~maxandersen]'s questions:
Version Watch (vwatch) Sources:
https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch
Steps to use locally or in Jenkins [1], [2]:
{quote}
1. Install JBDS several times in order to perform a comparison of the plugin/feature
versions installed, and generate an HTML report.
(If on linux can use
https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/vwatch/install.... to
automate the process)
Put them all under some folder ${INSTALL_FOLDER}.
2. Run maven to produce the report.
{code} mvn clean test -DinstallationsDir="$\{INSTALL_FOLDER}"
-Dvwatch.filter=".*(hibernate\|jboss\|xulrunner).*" -Dvwatch.md5check {code}
3. Open report in output.html in a browser to view resulting comparison table.
Jenkins jobs:
[1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat...
[2]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat...
use p2.mirror w/ comparator to verify plugin/feature versions are
correctly incremented between builds/baselines
----------------------------------------------------------------------------------------------------------------
Key: JBIDE-4731
URL:
https://issues.jboss.org/browse/JBIDE-4731
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Jiri Peterka
Priority: Blocker
Fix For: 4.1.x, 4.2.x
This depends on having per-component builds and a buckminster/p2 aggregator to merge them
into a single update site.
See
http://aniefer.blogspot.com/2009/08/versioning-p2-slides-from-eclipsecon.... for
details on using p2.mirror w/ a comparator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira