[
https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi...
]
Jiri Peterka commented on JBIDE-19190:
--------------------------------------
Thanks Max. [~maxandersen], It would probably be suitable to add me and Nick (but he's
already there I assume) as a contributors so we can push our PR each other if needed.
Except me no one else from QE needs permissions right now. Also the old location repo was
already deleted and my jobs updated. From my POV this task can be closed. Not sure about
Nick's jobs. [~nickboldt], are your jobs updated for a new repo location?
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.Alpha2
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)