[
https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi...
]
Jiri Peterka commented on JBIDE-19190:
--------------------------------------
True, I referred my old repo before. PR for the removal from jbdevstudio-qa repo created
https://github.com/jbdevstudio/jbdevstudio-qa/pull/55. Once Nick confirms his jobs are set
to a new location and working it can be applied.
migrate VersionWatch to jbosstools-* repo
-----------------------------------------
Key: JBIDE-19190
URL:
https://issues.jboss.org/browse/JBIDE-19190
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: qa
Affects Versions: 4.3.0.Alpha1
Reporter: Nick Boldt
Assignee: Jiri Peterka
Priority: Minor
Fix For: 4.3.0.Beta1
0. decide where to put this... under jbosstools-ci or some new repo? Create a new
component in JIRA accordingly.
1. remove all refs to QA Jenkins file paths to make this more generic
2. migrate those internal file paths into jenkins config.xml files
3. 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/
4. test #3 to ensure it works, and that a mix of "studio" and
"eclipse" folders can be used in a vwatch report
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)