[jbosstools-issues] [JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations
Nick Boldt (JIRA)
issues at jboss.org
Fri Aug 21 14:54:28 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-15481:
-------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.CR1)
> setup of vwatch for jboss tools installations
> ---------------------------------------------
>
> Key: JBIDE-15481
> URL: https://issues.jboss.org/browse/JBIDE-15481
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.x
>
> Attachments: jbide15481.png
>
>
> 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed.
> usecases:
> * find missing/weird versions
> * duplicate components
> * get list of potential unnecessary plugins in TP
> 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
> 4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes?
> Additionally, now that jbdevstudio-qa/vwatch has moved to jbosstools-versionwatch, we should also do these two things:
> 5. remove all refs to QA Jenkins file paths to make *.sh scripts more generic
> 6. migrate those internal file paths into jenkins config.xml files so they're not stored in public repos
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list