[
https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15481:
------------------------------------
Or, we could set this up as a downstream job from
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p...
or
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...,
which do the install needed... but we would need to copy the workspace somewhere so it can
be reused by the downstream job.
Might save a bunch of time (and disk) if we were only running vwatch on cached folders
instead of doing a fresh install each time.
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
Fix For: 4.2.x
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
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)